Date: Thu, 25 Jul 2002 13:21:00 -0700 From: Kent Stewart <kstewart@owt.com> To: "Roger 'Rocky' Vetterberg" <listsub@rambo.simx.org> Cc: Eric Dedrick <dedrick@dsl-146-127.resnet.purdue.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: another question Message-ID: <3D405DAC.8000306@owt.com> References: <20020725122956.M96437-100000@dsl-146-127.resnet.purdue.edu> <3D405A2C.1020406@rambo.simx.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Roger 'Rocky' Vetterberg wrote: > Eric Dedrick wrote: > >> Natd hasn't exactly been working as it used to either. Any idea what >> this >> means? >> >> Jul 24 23:26:43 dsl-146-127 /kernel: arp: 192.168.0.1 is on lo0 but got >> reply from 00:04:76:b8:94:10 on ep0 >> Jul 24 23:28:17 dsl-146-127 /kernel: arp: 128.211.146.127 is on lo0 but >> got reply from 00:60:08:10:e6:e5 on xl0 >> >> # ifconfig >> xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> options=3<rxcsum,txcsum> >> inet6 fe80::204:76ff:feb8:9410%xl0 prefixlen 64 scopeid 0x1 >> inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 >> ether 00:04:76:b8:94:10 >> media: Ethernet autoselect (10baseT/UTP) >> status: active >> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 >> ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> inet 128.211.146.127 netmask 0xffffff00 broadcast 128.211.146.255 >> inet6 fe80::260:8ff:fe10:e6e5%ep0 prefixlen 64 scopeid 0x3 >> ether 00:60:08:10:e6:e5 >> media: Ethernet 10baseT/UTP >> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 >> inet 127.0.0.1 netmask 0xff000000 >> faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500 >> >> > > I dont know why this happens but if its any comfort I have had similar > errors on my machine for years. > > Jul 4 14:40:43 rambo /kernel: arp: 192.168.0.3 is on lo0 but got reply > from 00:48:54:50:e4:96 on fxp0 > Jul 8 15:13:36 rambo /kernel: arp: 192.168.0.1 is on dc1 but got reply > from 00:02:e3:14:5a:b6 on fxp0 > > 192.168.0.3 is the ip of the machine logging this, 192.168.0.1 is a win > machine connected to dc1. > Since everything works I havent bothered to look into it. This only happens when dc1 and fxp0 are hooked up to the same stretch of wire. When you have it setup properly (a variable definition), it doesn't happen. Kent > > -- > R > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > . > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D405DAC.8000306>