From: Kyle Moffett <mrmacman_g4@mac.com>
To: Jarne Cook <jcook@siliconriver.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Complicated networking problem
Date: Tue, 1 Mar 2005 22:44:23 -0500 [thread overview]
Message-ID: <5DFD93E4-8ACD-11D9-858B-000393ACC76E@mac.com> (raw)
In-Reply-To: <200503021327.31429.jcook@siliconriver.com.au>
On Mar 01, 2005, at 22:27, Jarne Cook wrote:
> Damn
>
> Having to configure the interfaces using bonding was not really the
> answer I
> was expecting.
>
> I did not think linux would be that rigid. I figured if poodoze is
> able to do
> it (seamlessly mind you), surely linux (with some tinkering) would be
> able to
> do it also.
>
> The goal was to have the networking on the laptop work as perfectly as
> crapdoze does.
>
> Perhaps I should and this topic to my list of software issues that
> no-one else
> cares about. "man that list is getting big". maybe one day I'll
> develop the
> balls to get deep into the code.
Well, what exactly is the desired behavior for you? If you have two
network
interfaces to the same local network, the default config will pick a
random
one (They're both equal-cost unless you tell it otherwise) and send
ARPs and
everything else through that one interface. If you take it down, it may
require a minute or so to update the rest of the network to the new
hardware
address, but eventually they will figure it out. I suppose if that is
the
expected config, you could tell the box to send out a gratuitous ARP
packet
when you reconfigure interfaces, but that's a userspace issue in any
case.
As far as networking is concerned, a subnet is an atomic networking
unit.
Everything on it is considered directly and equally attached to
everything
else, unless informed otherwise via a switch protocol. Any system that
doesn't follow that rule is broken.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2005-03-02 3:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 4:59 Jarne Cook
2005-03-01 2:02 ` Valdis.Kletnieks
2005-03-01 2:35 ` Dmitry Torokhov
2005-03-02 3:24 ` Jarne Cook
2005-03-02 3:27 ` Jarne Cook
2005-03-02 3:44 ` Kyle Moffett [this message]
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=5DFD93E4-8ACD-11D9-858B-000393ACC76E@mac.com \
--to=mrmacman_g4@mac.com \
--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
all inboxes | Powered by JetHome®