[114466] in North American Network Operators' Group
RE: two interfaces one subnet
daemon@ATHENA.MIT.EDU (Skywing)
Mon May 11 21:31:49 2009
From: Skywing <Skywing@valhallalegends.com>
To: Chris Adams <cmadams@hiwaay.net>, "nanog@nanog.org" <nanog@nanog.org>
Date: Mon, 11 May 2009 20:31:37 -0500
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Yes, similar happens to me all the time with both Windows Server 2008 and V=
ista with respect to 802.11 putting two interfaces on the same subnet (and =
LAN segment). I typically am never the wiser until I notice that a SMB con=
nection had gone over to 802.11 first, because that associated before the w=
ire was plugged in, causing data transfers on that connection to be much sl=
ower than on a hardline.
This is something that happens every day to a great many laptop users, I'd =
wager. Certainly not by any means up there in "does not work at all, perio=
d / incompatible with networking" land, as, at the very least, emperical ev=
idence has a quite different story to say.
- S
-----Original Message-----
From: Chris Adams <cmadams@hiwaay.net>
Sent: Monday, May 11, 2009 16:29
To: nanog@nanog.org <nanog@nanog.org>
Subject: Re: two interfaces one subnet
Once upon a time, Kevin Oberman <oberman@es.net> said:
> > From: Chris Meidinger <cmeidinger@sendmail.com>
> > For example, eth0 is 10.0.0.1/24 and eth1 is 10.0.0.2/24, nothing like
> > bonding going on. The customers usually have the idea of running one
> > interface for administration and another for production (which is a
> > _good_ idea) but they want to do it in the same subnet (not such a
> > good idea...)
>
> This will not work right. One interface can be 10.0.0.1/24, but any
> added interfaces would need to be /32 (10.0.0.2/32).
I don't know which OS(es) you are using, but that's not true in Linux.
I see this all the time at home; if I plug my notebook into the wired
LAN and still have the wireless enabled, both will get an IP (in the
same subnet) from DHCP. The wired link is the preferred default route
by default, but you can easily set up routes for some networks via the
wireless link.
You can also set up multipath routing to send packets out both links. I
think you can also use IP policy routing to control the choice of
outbound interface by rule (e.g. based on source address).
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
