Carlos E. R. wrote:
The Saturday 2004-07-24 at 22:28 -0500, Joe Morris (NTM) wrote:
|FW_IPv6="" | Here I needed to say no.
This no disables ipv6 in the firewall rules, thus the need to change the next one to 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.
But then you are allowing ipv6 packets to get out, and the system will expect to be answered in that protocol as well, but it will get no response.
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.
Anyway, I have dissabled ipv6 completely, but no speed difference.
In module loading or in the firewall rule loading?
|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?
No, I activate it manually running wvdial on a console when needed.
So this means when the ip-up script runs to configure your ppp0 interface, it also reloads the firewall rules to include the new interface. I am wondering if the ISP you dial into is like my router, which appeared to specifically not like the ipv6 rules. The firewall rules even stated to expect timeouts when it loaded with the ipv6 enabled. I could be all wrong though, hope you get it all figured out. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871