Tom Eastep wrote:
> Tom Eastep wrote:
>> Laurent CARON wrote:
>>> Hi,
>>>
>>> I'm currently facing a rather strange problem.
>>>
>>> I did order a dedicated server at a hosting company.
>>>
>>> This server is provided with ipv4 and ipv6 connectivity.
>>>
>>> The default ipv6 gateway is given through radvd (from what i've seen in
>>> tcpdump logs):
>>>
>>> 21:17:25.260848 IP6 fe80::215:2cff:fe6e:b000 > ip6-allnodes: ICMP6,
>>> router advertisement, length 64
>>>
>>> default via fe80::215:2cff:fe6e:b000 dev eth0  proto kernel  metric 1024
>>>  expires 1797sec mtu 1500 advmss 1440 hoplimit 64
>>>
>>> If I start shorewall, this default route immediately disappears thus
>>> preventing any ipv6 communication.
>>>
>>> I think my setup might block ipv6 router advertisment messages.
>> Unless you explicitly block these messages, Shorewall allows them.
> 
> You can look at /usr/share/shorewall6/action.AllowICMPs to see the icmp6
>  types that Shorewall allows.
> 
> If the default route is immediately disappearing as Shorewall6 starts,
> it would be useful if you could forward a trace of Shorewall6 startup:
> 
>       shorewall6 trace start 2> trace.txt
> 

After shorewall6 has started, also please execute this command:

        ls -a /var/lib/shorewall6/

and include the output in your response.

Thanks,
-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 \________________________________________________

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to