On Thu, Sep 05, 2002 at 03:31:05PM +1000, Ray Phillips wrote:
> Thanks for your replies Manuel and Jaromir.
> 
> OK, I left ne2 as it was and set ne3 to a number in 130.102.20.0/24:
> 
> # ifconfig ne2
> ne2: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         media: Ethernet autoselect (10baseT)
>         inet 130.102.18.111 netmask 0xffffffc0 broadcast 130.102.18.127
>         inet6 fe80::240:5ff:fe6b:f9f3%ne2 prefixlen 64 scopeid 0x1
> # ifconfig ne3
> ne3: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         media: Ethernet autoselect (10baseT)
>         inet 130.102.20.121 netmask 0xffffff00 broadcast 130.102.20.255
>         inet6 fe80::240:5ff:fee1:f6fa%ne3 prefixlen 64 scopeid 0x2
> 
> I thought that would make it possible to access my LAN from the PC 
> when either ne2 or ne3 (or both) were connected to the LAN, but I 
> found that was only possible when ne3 was plugged in.  I tried 
> pinging the IP numbers for ne2 and ne3 from the LAN: they could only 
> be reached when ne3 was plugged in--even if ne2 wasn't connected to 
> the LAN.  So, no packets are travelling into or out of ne2 from the 
> LAN.  Is that to be expected?
> 
> Next I re-enabled ipf and connected both cards to the LAN.  I could 
> only ping machines on the LAN from the PC when ne3 was plugged in, 
> not when only ne2 was connected.  When pinging from the LAN I could 
> reach ne2 only when both ne2 and ne3 were plugged in.  ne3 could be 
> pinged from the LAN when only it was connected.

Yes, of course. The addresse/IP you have say that your LAN can be reached
via ne3.

You can't have 2 routes to the same network via 2 different interfaces.
How should the kernel choose the right one if this was the case ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--