Date: Sat, 2 Oct 2004 17:50:11 GMT From: Brooks Davis <brooks@one-eyed-alien.net> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/72263: gifconfig output corruption Message-ID: <200410021750.i92HoBdp088231@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/72263; it has been noted by GNATS. From: Brooks Davis <brooks@one-eyed-alien.net> To: Jonas Nagel <fireball@zerouptime.ch> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/72263: gifconfig output corruption Date: Sat, 2 Oct 2004 10:47:14 -0700 On Sat, Oct 02, 2004 at 07:10:23PM +0200, Jonas Nagel wrote: > >Description: > When one uses gifconfig -a or ifconfig to display configuration of the gif-tunnel interfaces > it will not be displayed (correctly). gifconfig displays garbage within the output and ifconfig > displays nothing at all. > > Besides that, everything works as designed. > > Also when I use gifconfig gifn delete and then 'sh /etc/rc.network start' again; everything works, > but no info visible, corruption of output stays the same. > > got# gifconfig -a > gif0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1280 > physical address z¸PÕ --> > gif1: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1280 > physical address z¸PÕ --> This sort of error is usually a symptom of your userland and kernel being out of sync. > got# ifconfig |grep gif > gif0: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1280 > gif1: flags=8011<UP,POINTOPOINT,MULTICAST> mtu 1280 > > But the interfaces are configured with valid ip addresses in rc.conf and work correctly. This is the expected output from that command. The configuration lines do not contain the string gif so the grep won't match them... > >How-To-Repeat: > No idea, besides typing gifconfig -a or ifconfig |grep gif > you cannot reproduce this straight away, after a fresh boot, but it seems to happen over the time, > when its already running a while; > --> 6:55PM up 111 days, 32 mins, 1 user, load averages: 0.00, 0.02, 0.19 > > I don't want to boot the firewall, just to see if it works again, because I remember some time ago, > when I configured it first, it displayed all correctly. This sounds like some sort of memory corruption. I don't give us any real chance of being able to fix this problem with so little information. I can't replicate it here. -- Brooks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410021750.i92HoBdp088231>