Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    SG-1100 IPv6 WAN

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    2 Posts 2 Posters 563 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Timmy
      last edited by

      Hi all,

      This is a bit of a long shot. I am trying to get IPv6 working on my SG-1100. My ISP has a beta for IPv6 running, and there are details on how to set it up on their end, and on pfSense. I have friends who have it all working (same ISP), but they are running pfSense on Intel-based PCs, where as I am running it on an SG-1100.

      Instruction on setting it up:

      WAN Settings
      Menu: Interfaces – WAN
      IP Configuration Type: DHCP6

      DHCPv6 Prefix Delegation size: 56
      The following options only should be checked:

      Send IPv6 prefix hint
      Do not wait for a RA

      There are other settings across the LAN interfaces and route configuration.

      I think the issue I am having is something to do with how the SG-1100 manages the external ports and the internal virtual switch - only real difference I can see between my router and friends who run pfSense on Intel boxes. I have had a couple of gotchas with the switch config before (got it all working, just missed some steps).

      DHCP6 log

      Sep 5 18:57:36	dhcp6c	95857	Sending Solicit
      Sep 5 18:57:36	dhcp6c	95857	set client ID (len 14)
      Sep 5 18:57:36	dhcp6c	95857	set elapsed time (len 2)
      Sep 5 18:57:36	dhcp6c	95857	send solicit to ff02::1:2%mvneta0.4090
      Sep 5 18:57:36	dhcp6c	95857	reset a timer on mvneta0.4090, state=SOLICIT, timeo=206, retrans=125424
      

      Interface config - (note: I have other VLANs configured for IoT and Guest access, which are all working fine):

      VLAN group	VLAN tag	Members	    Description
      0	        1	        0	    Default System VLAN	
      1	        4090	        0t,3	    WAN	
      2	        4091	        0t,2	    LAN	
      3	        4092	        0t,1	    OPT
      

      I only get a link local address on the WAN interface (A,B,C, and D replacing actual) %mvneta0.4090 is how it is shown in the interface and on ssh:

      IPv6 Link Local
      fe80::AAAA:BBBB:CCCC:DDDD%mvneta0.4090
      From ifconfig:

      mvneta0.4090: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
      	description: WAN
      	options=3<RXCSUM,TXCSUM>
      	ether <MAC>
      	inet6 fe80::AAAA:BBBB:CCCC:DDDD%mvneta0.4090 prefixlen 64 scopeid 0xe
      	inet <Public IPv4> netmask 0xfffffe00 broadcast <IPv4.255>
      	groups: vlan
      	vlan: 4090 vlanpcp: 0 parent interface: mvneta0
      	media: Ethernet 1000baseT <full-duplex>
      	status: active
      	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
      

      Thanks for any advice.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        They may be sending a prefix only in which case the WAN would not get an IPv6 address directly and would using link-local for routing the prefix. My ISP does that.
        If you have LAN or OPT set to track WAN with prefix ID set they should get a v6 IP.

        Enable Debug in the dhcpv6 settings on WAN and you will get a lot more logged info when it connects.

        Steve

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.