Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 5797 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

What information is needed from ISP for SLAAC on XG?

WörnhardIT Administrator

Hi all

I am running SFOS 16.05.7 MR-7 on my SG115. My link with the ISP is VDSL using PPPoE.

My provider supports IPv6 and my WAN side has the subnet 2001:8e0:9ff:abcd::/64, and a provider assigned PA: 2001:8e0:abcd::/64. He tells me all I need to do to have a working IPv6 connection is to enable SLAAC on my firewall in order to get IPv6 working.


I have turned on IPv6 on eth1 with IPv6 Assignment = DHCP, Mode = Auto (which makes the "Stateless" option selected). I need to fill inn a Gateway Name, but my provider has not provided anything like this and the documentation does not mention it either.

Is the "Gateway Name" just a label?
How can I verify what the SLAAC process does on my XG?

Thanks for reading
- Maurice



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    your assumption is correct, it is a label only.

    I am surprised you were only assigned a /64 for your internal use usually a /56 or occasionally a /60 for home users and maybe even a /48.

    The only IPv6 function that works is the DHCP on the external interface. You will need to configure your internal address space because the current version of XG and the v17b version do not provide any real useful functions similar to the UTM 9.5.

    To use IPv6 on the XG you would need to setup a modem/router with firewall disabled but IPv6 enabled and you would need another /64 because you are not supposed to subnet a /64 except for link usage. My opinion some of the more network specialists might add more details.

    Very frustrating.

    Ian

  • 0 in reply to rfcat_vk

    Hi Ian

    Thanks for your explanation. Do I understand correctly that DHCP over PPPoE is not supported on XG, that's why you recommend a modem/router before the XG? (If this is the case: WatchGuard used to have the same problem ...) If DHCPv6 over PPPoE is supported, any ideas why the public-facing /64 address does not show up in my XG on Port1?

    I dblchecked with the ISP and they actually assign an /48 for internal use, and they use prefix delegation (PD). My understanding of your post is that PD is not yet supported in XG, but when assigning it manually I should be able to get it to work?

    - Maurice

  • 0 in reply to WörnhardIT Administrator

    Hi,

    you are assigned anew external address when your network restarts using PPPoE (DHCP). I have IPv6 addresses asigned to my external interface but cannot workout how to get the internal assigned range. The UTM 9.5 picks up all the information and I was hoping XG v17b would be updated.

    If you have a DHCP (not PPPoE) based then you will see the addresses assigned and I believe PD works, but no practical experience.

    Ian

Reply
  • 0 in reply to WörnhardIT Administrator

    Hi,

    you are assigned anew external address when your network restarts using PPPoE (DHCP). I have IPv6 addresses asigned to my external interface but cannot workout how to get the internal assigned range. The UTM 9.5 picks up all the information and I was hoping XG v17b would be updated.

    If you have a DHCP (not PPPoE) based then you will see the addresses assigned and I believe PD works, but no practical experience.

    Ian

Children
No Data