-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote: |I don't see any ipv6 packet on ethereal capture, but anyway, the firewall |seems correct related to that: | |# Disallowing IPv6 packets may lead to long timeouts when connecting to IPv6 |# Adresses. See FW_IPv6_REJECT_OUTGOING to avoid this. |# |FW_IPv6="" | Here I needed to say no. |# Set to yes to avoid timeouts because of dropped IPv6 Packets. This Option |# does only make sense with FW_IPv6 != no |# |FW_IPv6_REJECT_OUTGOING="yes" | This I set to no as well. This stopped the errors at boot, and it seemed my system speed was back to normal. I am connected to a Netgear router now, and maybe it is not ipv6 ready. If you need the ipv6 functionality, don't do what I did. I know the firewall is reset when the ppp0 interface goes up, that is why I suspected it might be that. You could always try and if it doesn't change things change it back. |And the log shows "SFW2-OUT-IPv6_PROHIB" messages related to eth0 when |booting up only, nothing related to /dev/ppp0 Is ppp0 active at boot? |Perhaps I should dissable ipv6 completely on the kernel. How, I wonder :-? No need, this can be done in /etc/modprobe.conf. - -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBAyjiSllW3IopKeMRAgg/AKCt2Qwcnjc5It3U0jVSSQmP1oxLhwCgvYIN fJsX4Ukmbz0rgHj8rm278Us= =gF66 -----END PGP SIGNATURE-----