Looking at a packet capture, a response to the DHCP6 solicit is never received from Xfinity.Īfter many iterations of testing, my conclusion is that Xfinity seems to respond to a DHCPv6 Solicit message only when the IPv6 source address is consistent with what they expect.
#Spoofing network mac address plus#
When switching to the new device (pfSense Plus 21.05.2), IPv6 doesn’t work. An address for the WAN and the prefix for LAN are obtained via DHCP6. On the old device (running pfSense 2.4.5), IPv6 is working properly.
During troubleshooting, the new device has also been configured by hand with essentially no changes other than to the WAN/LAN interface configuration and DUID. The new device has been configured from a backup/restore of the old device. LAN interface is set to track WAN, IPv6 Prefix ID=0.īoth the old and new devices are Netgate 5100s. MAC address is overridden (spoofed) on the WAN interface of the new device to match the MAC address of the old device.ĭHCP6 DUID is set in System/Advanced/Networking (DUID-LLT, with Link-layer address matching the spoofed WAN Mac). The network connection is residential Comcast/Xfinity with an Arris S33 cable modem. IPv6 is configured on the WAN via DHCP6, with prefix delegation size of /60 and prefix hint. One thing difficult to test is the WAN behavior with IPv6 and Comcast, so the issue described below was tested from the same site with two devices. Limits downtime and allows bench testing of some aspects of the new device prior to installation. Visit a site, swap out the existing unit (“old device”) with a pre-configured device (“new device”) instead of performing in-place upgrades. My general goal was to have multiple pfSense hardware devices to be used for upgrades.
0 kommentar(er)
