public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Valdis.Kletnieks@vt.edu
Cc: Jarne Cook <jcook@siliconriver.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Complicated networking problem
Date: Mon, 28 Feb 2005 21:35:35 -0500	[thread overview]
Message-ID: <200502282135.35405.dtor_core@ameritech.net> (raw)
In-Reply-To: <200503010202.j2122b80025303@turing-police.cc.vt.edu>

On Monday 28 February 2005 21:02, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 28 Feb 2005 14:59:31 +1000, Jarne Cook said:
> 
> > They are both using dhcp to the same simple network.  That's right.  Same 
> > network.  They both end up with gateway=192.168.0.1, netmask=255.255.255.0.  
> > But ofcourse they do not have the same IP addresses.
> 
> I don't suppose your network people would be willing to change it thusly:
> 
> wired ports:  gateway 192.168.0.1, netmask 255.255.255.128.0
> wireless:     gateway 192.168.128.1, netmask 255.255.255.128.0
> 
> Or move the wireless up to 192.168.1.1 if they think that would confuse things
> too much.
> 
> There's a limit to how far we should bend over backwards to support stupid
> networking decisions. 192.168 *is* a /16, might as well use it. ;)
> 
> If they won't, you're pretty much stuck with binding applications to one
> interface or another.
> 

If the goal is to primarily use wired link and seamlessly swith to wireless
then look into bonding driver in failover mode with wired interface as 
primary. This way you have only one address and userspace does not notice
anything.
 
-- 
Dmitry

  reply	other threads:[~2005-03-01  2:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28  4:59 Complicated networking problem Jarne Cook
2005-03-01  2:02 ` Valdis.Kletnieks
2005-03-01  2:35   ` Dmitry Torokhov [this message]
2005-03-02  3:24     ` Jarne Cook
2005-03-02  3:27     ` Jarne Cook
2005-03-02  3:44       ` Kyle Moffett
2005-03-02  4:56       ` Daniel Gryniewicz
     [not found] <3CLkr-2LJ-7@gated-at.bofh.it>
2005-03-01  1:21 ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200502282135.35405.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jcook@siliconriver.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox