On Wed, 29 Sep 2004, JINMEI Tatuya / [ISO-2022-JP] [EMAIL PROTECTED]@C#:H(B wrote: > >> Okay. Now I think I figure out the problem. Those host routes were > >> created not deliberately, so the kernel will eventually need a fix to > >> this. > >> > >> But if you are in a hurry and/or cannot replace the kernel soon, I > >> think setting net.inet6.ip6.rtexpire to 0 can be a workaround (with > >> this you even do not have to reboot the kernel - though rebooting may > >> also help if you can). > > > Warning: this freezed the system immediately [all network connectivity > > broke, and I had to do a quick reset]. Maybe I should have set it up > > at reboot before the system was in a 'bad' shape.. > > Sorry for the trouble, but could you be more specific on "freeze"? > Does it mean the kernel hanged (you could not type anything from the > keyboard, etc)?
Unfortunately, I can't. The when my SSH session froze, and the 6to4 SSH sessions as well, my first instinct was 'oh, crap', and knee-jerk push of reset button (because the box has no keyboard attached). Sorry for being inprecise. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
