Thanks Johnny, I think you've hit the nail on the head. I just your post after recently discovering something very similar.
I made a few changes to the virtual network settings that should not have mattered and then reapplied the IPs -- I removed all aliases and then began adding them back on one by one and now all is well. I am guessing this is the unanswered question of why some have experienced this issue and some have not. I am guessing due to the elusive nature of this issue it has remained unresolved for an unknown length of time in the Endian codebase. This should be added as a bug in the Endian bugtracker - anyone have a login to bugs.endian.com and would like to take this on? Johnny-M wrote: > > 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. > > From: compdoc [mailto:comp...@hotrodpc.com] > Sent: Saturday, October 22, 2011 4:20 AM > To: efw-user@lists.sourceforge.net > Subject: Re: [Efw-user] Port forwarding on RED multi-IP > >>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. > > > > ------------------------------------------------------------------------------ > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > Efw-user mailing list > Efw-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/efw-user > > -- View this message in context: http://old.nabble.com/Port-forwarding-on-RED-multi-IP-tp32694429p32708260.html Sent from the efw-user mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
