mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: changing ethernet devices, new one stops cold at iptables
Date: Sun, 25 Jul 2004 19:45:15 -0400	[thread overview]
Message-ID: <200407251945.15747.gene.heskett@verizon.net> (raw)
In-Reply-To: <410424D5.505@blue-labs.org>

On Sunday 25 July 2004 17:23, David Ford wrote:
>No need to reboot it.  Simply flush the neighbor cache.
>
>Scott root # ip neigh flush help
>Usage: ip neigh { add | del | change | replace } { ADDR [ lladdr
> LLADDR ] [ nud { permanent | noarp | stale | reachable } ]
>
>          | proxy ADDR } [ dev DEV ]
>
>       ip neigh {show|flush} [ to PREFIX ] [ dev DEV ] [ nud STATE ]
>
>David

Is my manpages too old?  I studied it for arp at least half an hour 
without seeing any way out of the dilemma short of a reboot, so I 
did.  And I just checked, theres no linkage from arp to anything 
called 'ip'.  Wrecked a 78 day uptime :(

Yes, I learned something from your message, thank you very much, but 
why is it so deeply buried?

Humm, is there not an option that will a: flush, and then b: refresh 
itself just as if its been rebooted?  The 'replace' appears to 
require intimate knowledge of a 48 bit MAC address etc I'd assume.

 
>Gene Heskett wrote:
>>On Sunday 25 July 2004 05:50, Henrik Nordstrom wrote:
>>>On Thu, 22 Jul 2004, Gene Heskett wrote:
>>>>I can ping the firewall, and I can ssh into it, so that part of
>>>>the network is fine, I just cannot get past iptables in the
>>>>firewall when eth0 is the nforce hardware, which has a different
>>>>MAC address.
>>>
>>>Have you verified that the routing got correctly set up on the new
>>>box?
>>>
>>>  ip ro ls
>>>
>>>The usual cause to the symptoms you describe is that the default
>>>route has gone missing or is invalid.
>>
>>The routing was good, showing the fireall as the default gateway
>>address.
>>
>>In this case, the fix was to reboot the firewall so that its arp
>>tables got refreshed to match the new MAC address of the onboard
>>nforce (forcedeth) nic.  Once that was done, everything was peachy.
>>
>>Thanks, I appreciate the reply, Henrik.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

  reply	other threads:[~2004-07-25 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0407251149290.25333-100000@filer.marasystems.com>
2004-07-25 20:28 ` Gene Heskett
2004-07-25 21:23   ` David Ford
2004-07-25 23:45     ` Gene Heskett [this message]
     [not found] <200407222114.20301.gene.heskett@verizon.net>
     [not found] ` <4100F2F0.3080300@redhat.com>
2004-07-23 12:46   ` Gene Heskett
2004-07-23 13:25   ` Gene Heskett

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=200407251945.15747.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --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®