From: Chris Friesen <chris_friesen@sympatico.ca>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: calling all gurus! odd and subtle network problem -- followup, possible answer
Date: Thu, 15 Feb 2001 23:49:01 -0500 [thread overview]
Message-ID: <3A8CB13D.ACE8A1@sympatico.ca> (raw)
In-Reply-To: <3A8CA97F.EB514999@sympatico.ca>
Chris Friesen wrote:
> The kicker is that the NIC with the MAC address in question happened to be in my
> G4 box running linux (yellowdog, 2.2.17 kernel). It was a D-Link 530TX NIC, if
> it matters. The linux box was not configured as a DHCP server or client, and
> both interfaces on the box were configured with static IP addresses. The
> motherboard interface was eth0 and was set to an address on the corporate LAN.
> The other NIC was eth1 and was set to an address in the 192.168 range for
> testing. The machine has been up and running in this configuration since
> september of last year with no known issues. I made no changes at the time the
> problems started.
Okay, so some further digging revealed that someone was testing out the
"ethertap" device, which according to him requires ip_forwarding and proxy_arp
to be turned on. I suspect this is what changed and caused the problems. Since
rebooting cleaned up the /proc filesystem and reset these to zero, the problems
went away.
This feels like the answer to me. It saw the arp requests coming in the one
interface, sent them out the other interface, and the other machines got
confused because they saw that arps coming from a different MAC address.
Guess this goes to show the problems people can get into with stuff they don't
understand....
Chris
prev parent reply other threads:[~2001-02-16 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 4:15 calling all gurus! odd and subtle network problem Chris Friesen
2001-02-16 4:49 ` Chris Friesen [this message]
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=3A8CB13D.ACE8A1@sympatico.ca \
--to=chris_friesen@sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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