Date: Mon, 10 Feb 1997 18:06:05 -0800 From: Amancio Hasty <hasty@rah.star-gate.com> To: hackers@freebsd.org Subject: mrouted bug? Message-ID: <199702110206.SAA14541@rah.star-gate.com>
next in thread | raw e-mail | index | archive | help
mrouted -D 3 usage: mrouted [-p] [-c configfile] [-d [debug_level]] mrouted -d 3 debug level 3 18:04:01.871 mrouted version 3.8a 18:04:01.901 Getting vifs from kernel interfaces 18:04:01.903 installing ed0 (204.188.121.18 on subnet 204.188.121.16/29) as vif #0 - rate=0 18:04:01.903 Getting vifs from /etc/mrouted.conf 18:04:01.905 installing tunnel from 204.188.121.18 to 140.174.2.1 as vif #1 - rate=500 18:04:01.905 Installing vifs in mrouted... 18:04:01.905 vif #0, phyint 204.188.121.18 18:04:01.906 SENT membership query from 204.188.121.18 to 224.0.0.1 18:04:01.906 SENT neighbor probe from 204.188.121.18 to 224.0.0.4 18:04:01.906 vif #1, tunnel 204.188.121.18 -> 140.174.2.1 18:04:01.906 SENT neighbor probe from 204.188.121.18 to 140.174.2.1 pruning on 18:04:01.934 Installing vifs in kernel... 18:04:01.936 vif #0, phyint 204.188.121.18 18:04:01.936 setsockopt MRT_ADD_VIF: File too large My mrouted was working fine last week till I upgraded to FreeBSD-current late last week. Does anyone have a clue as to what is going on here?? Tnks, Amancio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702110206.SAA14541>