Route related panic.
Pawel Jakub Dawidek
nick at garage.freebsd.pl
Tue Jan 27 10:03:01 PST 2004
On Tue, Jan 27, 2004 at 06:44:54PM +0100, Pawel Jakub Dawidek wrote:
+> How to repeat:
+> I can reproduce this panic by removing all routes and adding for example:
+> # route add -net 10.1.0.0/16 10.1.253.253
+> I got little patch for this, but I'm not sure if my fix is correct
+> (it works for me, but maybe it's just a workaround):
+> As you can see I added one more additional check for simlar situation,
+> but maybe it's just useless.
No, sorry, this fix was wrong, I removed it.
But panic stays very real.
Pawel Jakub Dawidek pawel at dawidek.net
UNIX Systems Programmer/Administrator http://garage.freebsd.pl
Am I Evil? Yes, I Am! http://cerber.sourceforge.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 305 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040127/48ca16a1/attachment-0001.bin
More information about the freebsd-current