what are the correct setting for IPV6 with ATT Fiber when not using the gateway (gateway bypass)
-
Anyone know the correct settings for getting IPV6 working on multipal LAN interfaces (multipal Prefixes) when using ATT Fiber bypassing the gateway? the instructions are not working or not complete. IPV4 works. I can see the DHCP6 request on the WAN interface and response with a prefix, but it is not getting applies or not working on PFSense.
-
logs are:
Jun 7 19:45:12 dhcp6c 91536 Sending Solicit
Jun 7 19:45:12 dhcp6c 91536 set client ID (len 27)
Jun 7 19:45:12 dhcp6c 91536 set elapsed time (len 2)
Jun 7 19:45:12 dhcp6c 91536 send solicit to ff02::1:2%mvneta2
Jun 7 19:45:12 dhcp6c 91536 reset a timer on mvneta2, state=SOLICIT, timeo=5, retrans=31928
Jun 7 19:45:12 dhcp6c 91536 receive advertise from fe80::ea4:2ff:fe2e:1c01%mvneta2 on mvneta2
Jun 7 19:45:12 dhcp6c 91536 get DHCP option server ID, len 10
Jun 7 19:45:12 dhcp6c 91536 DUID: 00:03:00:01:0c:a4:02:2e:1c:01
Jun 7 19:45:12 dhcp6c 91536 get DHCP option client ID, len 27
Jun 7 19:45:12 dhcp6c 91536 DUID: 00:02:00:00:0d:e9:30:30:31:45:34:36:2d:52:39:31:56:4a:30:46:46:31:30:34:39:31:37
Jun 7 19:45:12 dhcp6c 91536 get DHCP option status code, len 2
Jun 7 19:45:12 dhcp6c 91536 status code: unspec failure
Jun 7 19:45:12 dhcp6c 91536 server ID: 00:03:00:01:0c:a4:02:2e:1c:01, pref=-1
Jun 7 19:45:12 dhcp6c 91536 reset timer for mvneta2 to 0.999010
Jun 7 19:45:13 dhcp6c 91536 picked a server (ID: 00:03:00:01:0c:a4:02:2e:1c:01)
Jun 7 19:45:13 dhcp6c 91536 Sending Request
Jun 7 19:45:13 dhcp6c 91536 a new XID (2e2154) is generated
Jun 7 19:45:13 dhcp6c 91536 set client ID (len 27)
Jun 7 19:45:13 dhcp6c 91536 set server ID (len 10)
Jun 7 19:45:13 dhcp6c 91536 set elapsed time (len 2)
Jun 7 19:45:13 dhcp6c 91536 send request to ff02::1:2%mvneta2
Jun 7 19:45:13 dhcp6c 91536 reset a timer on mvneta2, state=REQUEST, timeo=0, retrans=1019
Jun 7 19:45:13 dhcp6c 91536 receive reply from fe80::ea4:2ff:fe2e:1c01%mvneta2 on mvneta2
Jun 7 19:45:13 dhcp6c 91536 get DHCP option server ID, len 10
Jun 7 19:45:13 dhcp6c 91536 DUID: 00:03:00:01:0c:a4:02:2e:1c:01
Jun 7 19:45:13 dhcp6c 91536 get DHCP option client ID, len 27
Jun 7 19:45:13 dhcp6c 91536 DUID: 00:02:00:00:0d:e9:30:30:31:45:34:36:2d:52:39:31:56:4a:30:46:46:31:30:34:39:31:37
Jun 7 19:45:13 dhcp6c 91536 get DHCP option status code, len 2
Jun 7 19:45:13 dhcp6c 91536 status code: unspec failure
Jun 7 19:45:13 dhcp6c 91536 dhcp6c Received REQUEST
Jun 7 19:45:13 dhcp6c 91536 status code: unspec failure
Jun 7 19:45:13 dhcp6c 91536 executes /var/etc/dhcp6c_wan_dhcp6withoutra_script.sh
Jun 7 19:45:13 dhcp6c 20086 dhcp6c REQUEST on mvneta2 - running rtsold
Jun 7 19:45:13 dhcp6c 91536 script "/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh" terminated
Jun 7 19:45:13 dhcp6c 91536 removing an event on mvneta2, state=REQUEST
Jun 7 19:45:13 dhcp6c 91536 removing server (ID: 00:03:00:01:0c:a4:02:2e:1c:01)
Jun 7 19:45:13 dhcp6c 91536 got an expected reply, sleeping.
Jun 7 19:45:15 dhcp6c 91536 receive reply from fe80::ea4:2ff:fe2e:1c01%mvneta2 on mvneta2
Jun 7 19:45:15 dhcp6c 91536 get DHCP option server ID, len 10
Jun 7 19:45:15 dhcp6c 91536 DUID: 00:03:00:01:0c:a4:02:2e:1c:01
Jun 7 19:45:15 dhcp6c 91536 get DHCP option client ID, len 27
Jun 7 19:45:15 dhcp6c 91536 DUID: 00:02:00:00:0d:e9:30:30:31:45:34:36:2d:52:39:31:56:4a:30:46:46:31:30:34:39:31:37
Jun 7 19:45:15 dhcp6c 91536 get DHCP option IA_PD, len 41
Jun 7 19:45:15 dhcp6c 91536 IA_PD: ID=1, T1=1800, T2=2880
Jun 7 19:45:15 dhcp6c 91536 get DHCP option IA_PD prefix, len 25
Jun 7 19:45:15 dhcp6c 91536 IA_PD prefix: 2600:1700:4ed1::/60 pltime=0 vltime=0
Jun 7 19:45:15 dhcp6c 91536 XID mismatch -
While I don't know the settings, and AT&T seems to pride themselves on not sharing such basic information to their customers, I can tell you that I've never seen pfsense pick up the IPv6 properly without the 'send IPv6 prefix hint' box checked.
After that it shouldn't take too long to just brute force it from 64, 56, or 48. -