Re: Source MAC addresses when bridge(4) used
On Sun, Jan 07, 2007 at 08:02:11AM +1100, Peter Jeremy wrote: I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: +-+ +-+ | | | | | laptop1 |-| desktop |-- Rest of network | |dc0 tl0| |rl0 via dumb switch +-+ +-+ Chiming in late here after a nice holiday. Both hosts are running 6.1-STABLE: laptop1: FreeBSD laptop1.vk2pj.dyndns.org 6.1-STABLE FreeBSD 6.1-STABLE #0: Wed Nov 15 18:40:00 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/laptop i386 desktop: FreeBSD jashank.vk2pj.dyndns.org 6.1-STABLE FreeBSD 6.1-STABLE #15: Wed Aug 2 18:35:57 EST 2006 ^^ This is actually fixed now in r1.84 and MFC'd early nov. The laptop would have been fine but the bridging was done on the desktop which was an older stable. The reason is that the arp reply when bridging sends the mac address of the nic where the request came in, so laptop1 will get the mac of tl0. The other problem that was fixed in r1.84 was that locally destined packets to the bridge were always broadcast when they shouldn't. Anything on the rest of the network arping for the rl0 address would cause the arp reply to also be sent to laptop1 (with rl0's address), hence the logged 'address moved' warnings. Some people pointed out that the address should be assigned to the bridge interface which is correct, but they way you had it still works and now that warning is now fixed. cheers, Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Source MAC addresses when bridge(4) used
On Sun, 2007-Jan-07 18:58:18 -0500, Sten Daniel Srsdal wrote: Peter Jeremy wrote: I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: ... Does moving 192.168.123.36 to the bridge interface help? That gets rid of the IP moved from MAC to MAC on NIC messages. It doesn't really address the questions I raised about why I'm getting them but I think getting rid of them will do for now. Thanks. -- Peter Jeremy pgpd8kSwMWo2N.pgp Description: PGP signature
Re: Source MAC addresses when bridge(4) used
On Friday 12 January 2007 17:12, Peter Jeremy wrote: On Sun, 2007-Jan-07 18:58:18 -0500, Sten Daniel Srsdal wrote: Peter Jeremy wrote: I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: ... Does moving 192.168.123.36 to the bridge interface help? That gets rid of the IP moved from MAC to MAC on NIC messages. It doesn't really address the questions I raised about why I'm getting them but I think getting rid of them will do for now. net.link.ether.inet.log_arp_movement=0 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Source MAC addresses when bridge(4) used
Peter Jeremy wrote: On Sun, 2007-Jan-07 18:58:18 -0500, Sten Daniel Srsdal wrote: Peter Jeremy wrote: I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: ... Does moving 192.168.123.36 to the bridge interface help? That gets rid of the IP moved from MAC to MAC on NIC messages. It doesn't really address the questions I raised about why I'm getting them but I think getting rid of them will do for now. The exact logic why this happens eludes me. Putting the IP address on the bridge interface has been considered the correct way on the bridge implementations that has an actual logical bridge interface I've come across. It is, as far as i understand, to address the problems you described. -- Sten Daniel Sørsdal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Source MAC addresses when bridge(4) used
On Sun, Jan 07, 2007 at 08:02:11AM +1100, Peter Jeremy wrote: The desktop network configuration is: tl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 ether 00:00:24:28:98:9a media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.123.36 netmask 0xff00 broadcast 192.168.123.255 ether 00:20:ed:78:9c:a3 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8043UP,BROADCAST,RUNNING,MULTICAST mtu 1500 ether ca:a9:aa:1e:71:32 priority 32768 hellotime 2 fwddelay 15 maxage 20 member: tl0 flags=3LEARNING,DISCOVER member: rl0 flags=3LEARNING,DISCOVER Does tinkering with net.link.ether.bridge.config help at all? See bridge(4) manpage. (I haven't used this, I'm just brainstorming...) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Source MAC addresses when bridge(4) used
If memory serves me right, Jeremy Chadwick wrote: On Sun, Jan 07, 2007 at 08:02:11AM +1100, Peter Jeremy wrote: The desktop network configuration is: tl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 ether 00:00:24:28:98:9a media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.123.36 netmask 0xff00 broadcast 192.168.123.255 ether 00:20:ed:78:9c:a3 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8043UP,BROADCAST,RUNNING,MULTICAST mtu 1500 ether ca:a9:aa:1e:71:32 priority 32768 hellotime 2 fwddelay 15 maxage 20 member: tl0 flags=3LEARNING,DISCOVER member: rl0 flags=3LEARNING,DISCOVER Does tinkering with net.link.ether.bridge.config help at all? See bridge(4) manpage. (I haven't used this, I'm just brainstorming...) Actually the applicable manpage for this configuration is if_bridge(4), but I think the OP knew that. As someone else in this thread pointed out, the usual practice is to assign an IP address to the bridge0 interface and leave the member interfaces unnumbered. As for *why* the IP address keeps moving around, I'm not sure either. Bruce. signature.asc Description: OpenPGP digital signature
Re: Source MAC addresses when bridge(4) used
On Saturday 13 January 2007 09:33, Bruce A. Mah wrote: As for *why* the IP address keeps moving around, I'm not sure either. The bridge interfaces MAC address changes every time you create one, ie [inchoate 18:11] /usr/src/sys/modules/bridgestp sudo ifconfig bridge0 create [inchoate 18:11] /usr/src/sys/modules/bridgestp sudo ifconfig bridge0 bridge0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether e6:91:28:34:39:79 priority 32768 hellotime 2 fwddelay 15 maxage 20 [inchoate 18:11] /usr/src/sys/modules/bridgestp sudo ifconfig bridge0 destroy [inchoate 18:11] /usr/src/sys/modules/bridgestp sudo ifconfig bridge0 create [inchoate 18:11] /usr/src/sys/modules/bridgestp sudo ifconfig bridge0 bridge0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether d2:da:21:33:32:df priority 32768 hellotime 2 fwddelay 15 maxage 20 so if you reboot then the MAC address will change at each reboot. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp37IWlaqH02.pgp Description: PGP signature
Re: Source MAC addresses when bridge(4) used
Peter Jeremy wrote: I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: +-+ +-+ | | | | | laptop1 |-| desktop |-- Rest of network | |dc0 tl0| |rl0 via dumb switch +-+ +-+ The desktop network configuration is: tl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 ether 00:00:24:28:98:9a media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.123.36 netmask 0xff00 broadcast 192.168.123.255 ether 00:20:ed:78:9c:a3 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8043UP,BROADCAST,RUNNING,MULTICAST mtu 1500 ether ca:a9:aa:1e:71:32 priority 32768 hellotime 2 fwddelay 15 maxage 20 member: tl0 flags=3LEARNING,DISCOVER member: rl0 flags=3LEARNING,DISCOVER laptop1 is regularly reporting that 192.168.123.36 (the IP address of the desktop) is switching between the two adapters in it: Jan 6 07:27:09 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 08:09:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 08:46:11 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 09:29:00 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 12:12:12 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 12:15:31 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 13:06:42 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 16:48:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 17:32:22 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 17:33:33 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 17:53:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 17:57:05 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 18:17:20 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 18:24:48 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 18:45:08 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 18:48:19 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 19:08:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 19:11:50 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 19:32:15 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 19:33:07 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 19:56:34 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 22:44:24 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 23:04:26 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Even more unexpectedly, laptop1 is repeating the same moved message: Jan 7 00:46:55 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 01:38:09 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 02:29:26 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 03:20:39 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 04:28:59 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 05:18:50 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 06:28:31 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 07:16:05 laptop1 kernel: arp: 192.168.123.36 moved
Source MAC addresses when bridge(4) used
I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: +-+ +-+ | | | | | laptop1 |-| desktop |-- Rest of network | |dc0 tl0| |rl0 via dumb switch +-+ +-+ The desktop network configuration is: tl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 ether 00:00:24:28:98:9a media: Ethernet autoselect (100baseTX full-duplex) status: active rl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.123.36 netmask 0xff00 broadcast 192.168.123.255 ether 00:20:ed:78:9c:a3 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8043UP,BROADCAST,RUNNING,MULTICAST mtu 1500 ether ca:a9:aa:1e:71:32 priority 32768 hellotime 2 fwddelay 15 maxage 20 member: tl0 flags=3LEARNING,DISCOVER member: rl0 flags=3LEARNING,DISCOVER laptop1 is regularly reporting that 192.168.123.36 (the IP address of the desktop) is switching between the two adapters in it: Jan 6 07:27:09 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 08:09:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 08:46:11 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 09:29:00 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 12:12:12 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 12:15:31 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 13:06:42 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 16:48:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 17:32:22 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 17:33:33 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 17:53:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 17:57:05 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 18:17:20 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 18:24:48 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 18:45:08 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 18:48:19 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 19:08:45 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 19:11:50 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 19:32:15 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 19:33:07 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 19:56:34 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 6 22:44:24 laptop1 kernel: arp: 192.168.123.36 moved from 00:20:ed:78:9c:a3 to 00:00:24:28:98:9a on dc0 Jan 6 23:04:26 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Even more unexpectedly, laptop1 is repeating the same moved message: Jan 7 00:46:55 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 01:38:09 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 02:29:26 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 03:20:39 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 04:28:59 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 05:18:50 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 06:28:31 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Jan 7 07:16:05 laptop1 kernel: arp: 192.168.123.36 moved from 00:00:24:28:98:9a to 00:20:ed:78:9c:a3 on dc0 Both hosts are running 6.1-STABLE: laptop1: FreeBSD
