Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 974 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IPv6: Client did not get a "Gateway"

gbl
Hi,

I've setup my UTM with an IPv6 Tunnelbroker.
My UTM is WebProxy enabled and surfing the Web is now well ofer IPv6.
Any Ping Test to Google from the UTM'c CLI is 100% OK.

After this, i trying to setup UTM's DHCPv6 Server for servicing my Clients.
My (Ubuntu) Clients getting a IPv6 from my assigned Subnet (is this the Prefix?). Pinging via IPv6 to another Clients in the same Subnet works.

But I can not ping any public IPv6 Address.

After adding a default route (e.G.: /sbin/route -A inet6 add ::/0 gw 2001:***x:0:f101::1), the public IPv6 Addresses are reachable.

It seems I (my Setup) have a Problem with Router Advertizement.

How can I fix this?
[:S]

sincerly
Guenter


This thread was automatically locked due to age.
  • 0
    Hi,
    do you have advertisement in the IPv6 settings turned on.
    This will obey your DHCP settings.

    Ian
  • 0
    THX.

    I solved this by myself. The issue was the Linux Client. This client is able to get IP Addresses "Automatically" or "Automatically (DHCP)". 
    Switched to "Automatically" solved my Problem.

    This make sense, because DHCP did not provide a Gateway anymore. So we have to find our routes via Link-Local "automatically".


    Guenter
Unfiltered HTML