Hi all.

I am trying to use a third NIC (Apple USB ethernet adaptor) as a second uplink (for failover).  I had this working with a previous but old version of Endian (not the Community Edition).  However, the appropriate module (asix I believe) isn't available in the Community edition (v3.3.19).  

Any advice on how to get this Apple USB NIC (a1277) working with Endian CE?

lsusb shows:

Bus 001 Device 002: ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x05ac Apple, Inc.
  idProduct          0x1402 Ethernet Adapter [A1277]
  bcdDevice            0.01
  iManufacturer           1 Apple Inc.
  iProduct                2 Apple USB Ethernet Adapter
  iSerial                 3 0E429C
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              250mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol      0
      iInterface              7 0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              11
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol         0
  bMaxPacketSize0         8
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)


Thanks.
HL

I could only manage to block requests from an IP pool by making a rule in Port Forwarding / Destination NAT.

Like:

Incoming IP: Uplink ANY
Translate to: A Local IP which takes most of the malicious requests. (Some docs say you can leave this empty but actually it wouldn't allow to be set empty.)
NAT: NAT
Filter Policy: DROP
Access From: Network/IP/Range

Is that really the way it should be set? Then I think I didn't understand the use case of Incoming routed traffic.

Hi,

I am creating a new rule to block some IP pools like this;

Source Type: Network/IP
Insert Network/IP: ..0.0/16
Destination: ANY. I also tried Zones -> Green
Service: ANY Protocol: ANY
Policy: DENY

But requests from this IP pool keep coming to the servers behind Endian. How does this really work?

Ok...I edited /etc/ssh/sshd_conf.tmpl and changed the settings there.  That did the trick.

HL

Hi all,

Recently installed Endian Community edition (upgraded to 3.3.19).  I noticed that the ssh configuration reverts to the default after a reboot.  For example, I usually edit /etc/ssh/sshd.conf to make certain changes (e.g. AllowUsers <myuser only>. Port 2222, PasswordAuthentication no).  Whenever the server reboots, it reverts to the default values (Port 22, AllowUsers root support and PasswordAuthentication yes).  How can I preserve my changes across reboots?

Thanks in advance.
Hilkiah

hello,

is there a way to install development tools on endian firwall?
i'm tryinbg to make igmp proxy to work and i think compiling its the only way.

thanks

Hello everyone,

I had a problem for a while that I can't solve, the configuration of my Endian router/firewall is as follows: 4 network cards, 1 X Eolo antenna input line, 1 x Gbit wired network green line, 1 x WiFi Gbit blue line , 1 x Wired Red Line x DMZ (which I don't use).

Now the problem is as follows on the wired green line I have a Synology server that I would like to reach from clients that are on the blue WiFi line, I routed the firewall from the server's IP address to the clients creating an interzone connection.

But the file folders that are on the server I can not reach them, the files are multimedia, mostly  that are published in broadcast.

If instead the clients are on the same wired network I can see the folders and files contained within.

Tengo un Endian Firewall, versión 3.3.2

Necesito hacer una configuración muy concreta y no se como hacerla.

Tengo un nombre de con No-IP y redireccionado en el Endian un puerto a mi servidor interno, este nombre No-ip, es la dirección externa WAN del Endian.

Si desde fuera de la red del Endian pongo en un navegador el nombre No-IP : el puerto puedo acceder correctamente a mi servidor, ejemplo https:\\"nombre no-ip":8283 funciona ok.

Pero si dentro de la red, donde está trabajando el Endian, escribo ese mimo ejemplo de antes, los navegadores no me abren la web del servidor.

Si por el contrario escribo https:\\" dirección IP de la red interna":8283 si puedo acceder correctamente, ejemplo https:\\192.168.0.174:8283 esto si me funciona, pero no es lo que necesito.

Lo que necesito es configurar el Endian y no se como hacerlo, para que desde la red interna(192.168.0.0) poniendo el nombre No-IP:8283 me consiga abrir el servidor.

Gracias, espero me ayuden.

Hi,

I have the following setup in a Hyper-V:

EFW 3.3.15 = Public IP
EFW 3.3.15 LAN = 192.168.110.1 (DHCP 192.168.110.0/24)
RRAS LAN = 192.168.110.15
RRAS VPN Server = 192.168.120.1 (Static Pool 192.168.120.0/24)
VPN Client = 192.168.120.2

I cannot reach the 192.168.110.0/24 network once i connect via VPN (i can get to the RRAS & Internet and that's it). I searched in many places, enabled Promiscuous mode on the Internal vSwitch, Disabled BADTCP drop in EFW, added a static route in EFW so it will know to send comms for 192.168.120.0/24 to 192.168.110.15 (via web interface and also ssh). Maybe I'm not putting it where it should be via SSH, my Linux knowledge is severely lacking, so trial & error was the way so far, but I'm about to give up on this. I've got to the point where I'm putting routes in VPNClient/RRAS/EFW that don't make sense even to me, just to see if anything changes.

If anyone has the knowledge and patience to explain in an idiot-proof way how such a setup should be configured i would be in his/her .

Thanks.

Hi, does it also happen to you that the firewall restarts several times even in one day for no reason? It's not an electrical problem. Could it be because of a link that is often offline?

Endian version 3.3.16, 3.3.17, 3.3.19.