Date: Sat, 25 May 2002 12:23:40 -0700 (PDT) From: Guido Laubner <Guido.Laubner@gmx.de> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/38554: changing interface ipaddress doesn't seem to work Message-ID: <200205251923.g4PJNeOM054302@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 38554
>Category: kern
>Synopsis: changing interface ipaddress doesn't seem to work
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat May 25 12:30:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Guido Laubner
>Release: 4.0-RELEASE
>Organization:
>Environment:
FreeBSD gatekeeper.die-insel.germany.net 4.0-RELEASE #2: Sun Mar 11 23:42:23 MET 2001 guido@gatekeeper.die-insel.germany.net:/usr/src/sys/compile/GATEKEEPER i386
>Description:
When I change the IP address of an interface the system continues
to use the old address. Ifconfig does display the new address though.
I've changed the IP address multiple times and the systems seem to love
the very first address for that interface, which was set on boot
time. I do have another system (same version, different HW aparat from
networking interface) which shows the same problem.
>How-To-Repeat:
In a window do this:
prompt# more /tmp/bla
*.* @192.168.0.88
prompt# ifconfig -a
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:30:84:3a:26:16
media: autoselect (100baseTX <full-duplex>) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>
ep0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1492
inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:a0:24:56:f7:e0
media: 10baseT/UTP
supported media: 10base2/BNC 10baseT/UTP 10base5/AUI
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
prompt# < kill syslogd now >
prompt# syslogd -f /tmp/bla
prompt# tcpdump -n -i ep0
tcpdump: listening on ep0
20:45:49.015965 arp who-has 192.168.0.88 tell 192.168.0.1
20:45:56.968093 arp who-has 192.168.0.44 tell 192.168.0.44
20:48:33.186548 arp who-has 192.168.0.88 tell 192.168.0.1
In other window (on same machine!)
20:45:49# logger test
20:45:56# ifconfig ep0 192.168.0.44
20.48:33# logger test
Watch when the machine arps for it's new ip. The next "logger" doesn't cause a new arp request for the syslog server with the _NEW_ ip, but with the old ip ! It doesn't change when it stop the syslogd and start a new one after changing the ip.
>Fix:
Sorry...
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205251923.g4PJNeOM054302>