On 1/17/11 11:58 AM, Jim Blake wrote: ugh my IPv6 provider. > > I conclude from the information above that the server is operating two > dual-stack interfaces correctly, stateless autoconfiguration is working > correctly, and while shorewall is forwarding IPv4 across the kernel, > shorewall6 is not forwarding anything.
Neither Shorewall6 nor Netfilter6 is responsible for routing. What Shorewall6 *does* do is set the ipv6 forwarding flags for the interfaces based on your interfaces file. That is working: > /proc/sys/net/ipv6/conf/eth0/forwarding = 1 > /proc/sys/net/ipv6/conf/eth1/forwarding = 1 Did you set those two flags and test forwarding before you installed Shorewall6? That should be the only thing needed to enable IPv6 forwarding through your router. If it works without Shorewall6 (shorewall6 clear), then you have a Shorewall6 problem; otherwise, there is something else going on in your setup. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
