Re: Port forwarding on RED multi-IP

I had a similar issue were only the primary IP would ping and none of the alias IP’s would respond.

Work Around:

I changed the primary IP to one of the alias IPs and cleared out the other alias. Each IP had to be added as the primary by itself first to create the rules.

After adding them using the above method, I was able to add them all to the Red interface so that they all responded to ping and port forwarding rules.

I changed the hardware including Motherboard and network cards and the problem went away so I’m thinking that it’s a driver issue, but I didn’t bother to isolate it further.

>We use EFW on a physical machine. At the moment we have 3x RED interfaces (pppoe to adsl).

> 

>Running 2.4.0, as the latest version does not like the nic (driver issue).

> 

>Hope this helps

With a VM, you can create as many interfaces as you like. Being virtual, you have a certain amount of flexibility.

You could create several red interfaces which could all attach to one (real) physical nic, or they could attach to multiple physical nics, as your networking requires.

In qemu-kvm, this is done by creating a bridge to each physical nic. The virtual nics are then created attached to the bridge. You can share the physical nic with as many virtual nics as makes sense.

There would be no driver issues within EFW, since you decide which type of virtual nic to install in the VM. (Realtek, Intel, virtio, etc)

So the issue becomes how many red interfaces (or any colored zones) EFW can support.