kern/72263: gifconfig output corruption

[Jonas Nagel]

>Number:         72263
>Category:       kern
>Synopsis:       gifconfig output corruption
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 02 17:20:23 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Jonas Nagel
>Release:        FreeBSD 4.10-RELEASE i386
>Organization:
>Environment:
System: FreeBSD got.zerouptime.ch 4.10-RELEASE FreeBSD 4.10-RELEASE #3: Sun Jun 13 15:47:26 CEST 2004     root at www.zerouptime.ch:/usr/obj/usr/src/sys/FW  i386


>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Õ  --> 

	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.

>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.
	
>Fix:

	It's hard to tell, if you do not understand, how this could happen at all.


>Release-Note:
>Audit-Trail:
>Unformatted: