Hello,
Have been running pfsense on a VM under Hyper-v for a month or more. Had a Comcast business account and my own modem (SB6121). Decided to switch to xfinity residential cause I didn’t need the features of Comcast business any longer. Bought a SB8200 and swapped it in place on the business account which was working. Last week, switched over to the xfinity gig account and cannot get pfsense to get a WAN IP address. Switched to the Xfinity modem and it worked until I tried to go back to the SB8200 today. Now I cannot get the pfsense box to connect to either the Xfinity modem or the SB8200. Any ideas on how to resolve this?
How did you activate the SB8200?
I called xfinity support.
I have a Netgear Router on dd-wrt that can connect. When I connect my pfsense to the modem I get this in the logs when I renew the DHCP on the WAN
Jul 18 12:39:59 | dhclient | FAIL | |
---|---|---|---|
Jul 18 12:39:59 | dhclient | 41817 | No working leases in persistent database - sleeping. |
Jul 18 12:39:59 | dhclient | Deleting old routes | |
Jul 18 12:39:58 | dhclient | New Routers (hn0): 67.160.96.1 | |
Jul 18 12:39:56 | dhclient | New Routers (hn0): 67.160.96.1 | |
Jul 18 12:39:56 | dhclient | New Broadcast Address (hn0): 255.255.255.255 | |
Jul 18 12:39:56 | dhclient | New Subnet Mask (hn0): 255.255.252.0 | |
Jul 18 12:39:56 | dhclient | New IP Address (hn0): 67.160.99.151 | |
Jul 18 12:39:56 | dhclient | ifconfig hn0 inet 67.160.99.151 netmask 255.255.252.0 broadcast 255.255.255.255 | |
Jul 18 12:39:56 | dhclient | Starting add_new_address() | |
Jul 18 12:39:56 | dhclient | TIMEOUT | |
Jul 18 12:39:56 | dhclient | 41817 | Trying recorded lease 67.160.99.151 |
Jul 18 12:39:56 | dhclient | 41817 | No DHCPOFFERS received. |
Jul 18 12:39:44 | dhclient | 41817 | DHCPDISCOVER on hn0 to 255.255.255.255 port 67 interval 12 |
Jul 18 12:39:19 | dhclient | 41817 | DHCPDISCOVER on hn0 to 255.255.255.255 port 67 interval 25 |
Jul 18 12:38:55 | dhclient | 41817 | DHCPDISCOVER on hn0 to 255.255.255.255 port 67 interval 24 |
and this
Jul 18 12:38:26 | dhclient | exiting. | |
---|---|---|---|
Jul 18 12:38:26 | dhclient | process and the information we find helpful for debugging. | |
Jul 18 12:38:26 | dhclient | before submitting a bug. These pages explain the proper | |
Jul 18 12:38:26 | dhclient | bugs on either our web page at www.isc.org or in the README file | |
Jul 18 12:38:26 | dhclient | than a configuration issue please read the section on submitting | |
Jul 18 12:38:26 | dhclient | If you think you have received this message due to a bug rather | |
Jul 18 12:38:26 | dhclient | Can’t attach interface {} to bpf device /dev/bpf0: Device not configured | |
Jul 18 12:38:26 | dhclient | Sending on BPF/hn0/00:15:5d:00:91:03 | |
Jul 18 12:38:26 | dhclient | Listening on BPF/hn0/00:15:5d:00:91:03 | |
Jul 18 12:38:26 | dhclient | For info, please visit https://www.isc.org/software/dhcp/ | |
Jul 18 12:38:26 | dhclient | All rights reserved. | |
Jul 18 12:38:26 | dhclient | Copyright 2004-2018 Internet Systems Consortium. | |
Jul 18 12:38:26 | dhclient | Internet Systems Consortium DHCP Client 4.4.1 |
Did you reboot the cable modem between the switch to pfsense? It usually needs a reboot to pickup new MAC address unless you clone the Mac of the dd wrt router
What happens if you connect your computer directly to the modem can you go online?
Yes to both questions. Currently have my old netgear in place of pfsense and it is working fine.
Hi, OP.
Have you tried copying the WAN (Internet port) MAC address of your netgear and apply it on pfsense. After saving shutdown pfsense and then connect to your modem and then turn it on. Check if that address the issue.
I have spoofed the mac of the Netgear router several times
Did you ever get this fixed? I am having the same issue. New SB8200 connected to an SG3100 and it won’t pull an IP. Wan port shows none in of sense.
I anded up getting a connectli device and deploying opnsense. That resolved it.