Craig Sanders <[email protected]> writes:
> On Fri, Feb 20, 2015 at 12:10:40PM +1100, Trent W. Buck wrote:
>> Dan062 <[email protected]> writes:
>>
>> > The box boots it connects to the network and both nics (eth0 and
>> > eth1) gets same ip a.b.c.149.
>>
>> This is not supported. Don't do it.
>
> i might be wrong, but as i read it that's the problem he's complaining
> about - it's happening but he doesn't want it to.
I solve this by brute force:
just don't plug in / bring up both NICs at once.
Maybe NetworkManager has magic to automate that for GUI people,
but I can't help there.
--------------------
In case it's not obvious to the OP, the issue is that you'll end up with
two default routes, like
default via 192.168.1.1 dev eth0
default via 192.168.1.1 dev eth1
192.168.1.1/24 dev eth0 proto kernel scope link src 192.168.1.2
192.168.1.1/24 dev eth1 proto kernel scope link src 192.168.1.3
New packets will end up going via eth0, because (this time) it's first.
The other end will say "WTF, I sent stuff to 192.168.1.3 but I got an
answer back from 192.168.1.2" and chuck a wobbly.
If you want both links up at once to double your throughput, or for
failover (to avoid a SPOF in the NIC), you want what's called "trunking"
or "bonding". It's slightly tedious and flaky; mostly I wouldn't bother.
_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main
