Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

multiple interfaces on same subnet

Somewhere in my past I ran into a problem where the outgoing packets 
went out one interface, but the incoming packets came in the other 
interface.  Some process or service did not like this, it required the 
same interface be used for both directions.  I don't remember any more 
details.  I think it was Solaris rather than Linux, but I'm not certain.

You might get around the problem by advertising route costs to coax the 
next hop to use the desired IP address for the box.

	Jerry Natowitz
	j.natowitz (at)
	Owner of Unix port 1572 (chip-lm), as found by Google

Jerry Feldman wrote:
> Recently I noticed that both Linux (specifically Ubuntu 9.10) on
> netmanager as well as Windows like to connect to both the wired and
> wireless networks at the same time. Fortunately, the Linux routing table
> assigns the default route to the wired connection. Windows actually
> creates 2 default routes, but with different metrics.
> From my networking experience, this really should not pose a problem.
> Sometimes I like to disable wireless which is easy in Linux, but a minor
> pain on Windows.
> I'm looking for some reasons why this might be a bad thing, but I don't
> know any technical reason not to allow this, at least when there is a
> single default route.
> ------------------------------------------------------------------------
> _______________________________________________
> Discuss mailing list
> Discuss-mNDKBlG2WHs at

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /