The Sunday 2004-07-25 at 22:45 -0500, Joe Morris (NTM) wrote:
No, you missed the point of the first change. The first change turns off all ipv6 rules in the firewall, as per the comment. In my experience, commenting out the ipv6 in modprobe did not completely fix my speed problem, probably because it was still trying to set the rules, just no modules would load.
The second variable says: # 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" So, to avoid timeouts, set it to "yes" - that is what I want. It also says that it only makes sense is FW_IPv6 is set to something different than "no"; that is what I do: # - drop: drop all IPv6 packets. This is the default. # Disallowing IPv6 packets may lead to long timeouts when connecting to # IPv6 Adresses. See FW_IPv6_REJECT_OUTGOING to avoid this. FW_IPv6="" Therefore, as I block ipv6 going out, there will not be any incoming ipv6 in answer. But, as I commented out, while pppd is running and the connection to Internet is on, I see no ipv6 packet been dropped, passed or whatever: the firewall would log it, and it doesn't. There are no ipv6 packets been sent or received - as it should be, as none of my providers are ipv6 capable. Still, that doesn't explain why if I route my traffic to another computer running SuSE 7.3 the connections speed more than doubles. My hypothesis is still that there is some bug on the ppp code in SuSE 9.1 that makes it loose packets. I have looked at the flow with ethereal, and I see nothing strange there - except long pauses.
Anyway, I have dissabled ipv6 completely, but no speed difference.
In module loading or in the firewall rule loading?
in modprobe.conf: install ipv6 /bin/true -- Cheers, Carlos Robinson