I just moved. I have a GWIFI with Openwrt I've been running for ages. The move involved a new modem, everything was plug and play (Xfinity to Xfinity).
Yesterday, however, everything went South. Router seems fine, everything ok with intranet, so I decide it must be the refurbished modem giving up the ghost. I got a brand new Arris S33 today and still no internet.
When I look at the wan interface, I see it gets an address from the modem via DHCP--but then drops it after a few seconds. I'm using my laptop straight into the modem right now with no issues. I've been trying everything I could read as far as config changes, but I don;t think the solution is down that path--it's the same config I've been using for days (and years before that).
I'm about the get on the horn with Xfinity, but I'm not holding my breath they'll be able to help. Anybody have any pointers? Thanks in advance.
First, try rebooting the modem -- maybe a few times -- with nothing connected to the ethernet port. Then reboot your router and plug it into the modem.
If that doesn't fix the problem, let's review your config to see if there is anything wrong there:
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
Thanks for the speedy reply! I'll do all that but here's the result of a little experiment I just ran: using my phone and ethernet tethering, I can get internet through the router. WAN IP is stable. So I now know neither the modem nor router are expressly an issue, just the interplay between them.
I wouldn't say it is a no-no, but I'd try the 1G port which may be more stable in this situation. Unless you have >1G service and a router capable of that bandwidth, it shouldn't matter (assuming both ports are physically active).
Also, you might check your cable -- it is possible that you have a faulty cable (even if it is new, it's not unheard of to have a bad cable from time to time).
I only see local IPs, but please flag any security leaks and I'll come back and edit:
Tue Dec 26 20:10:37 2023 daemon.notice netifd: wan (5532): udhcpc: received SIGTERM
Tue Dec 26 20:10:37 2023 daemon.notice netifd: wan (5532): udhcpc: unicasting a release of 192.168.165.186 to 192.168.165.59
Tue Dec 26 20:10:37 2023 daemon.notice netifd: wan (5532): udhcpc: sending release
Tue Dec 26 20:10:37 2023 daemon.notice netifd: wan (5532): udhcpc: entering released state
Tue Dec 26 20:10:41 2023 daemon.notice netifd: wan (6010): udhcpc: started, v1.36.1
Tue Dec 26 20:10:41 2023 daemon.notice netifd: wan (6010): udhcpc: broadcasting discover
Tue Dec 26 20:10:44 2023 daemon.notice netifd: wan (6010): udhcpc: broadcasting discover
Tue Dec 26 20:10:47 2023 daemon.notice netifd: wan (6010): udhcpc: broadcasting discover
Tue Dec 26 20:10:53 2023 daemon.notice netifd: wan (6010): udhcpc: received SIGTERM
Tue Dec 26 20:10:53 2023 daemon.notice netifd: wan (6010): udhcpc: entering released state
Tue Dec 26 20:11:09 2023 daemon.notice netifd: wan (6142): udhcpc: started, v1.36.1
Tue Dec 26 20:11:09 2023 daemon.notice netifd: wan (6142): udhcpc: broadcasting discover
Tue Dec 26 20:11:12 2023 daemon.notice netifd: wan (6142): udhcpc: broadcasting discover
Tue Dec 26 20:11:15 2023 daemon.notice netifd: wan (6142): udhcpc: broadcasting discover
Tue Dec 26 20:11:23 2023 daemon.notice netifd: wan (6142): udhcpc: received SIGTERM
Tue Dec 26 20:11:23 2023 daemon.notice netifd: wan (6142): udhcpc: entering released state
Tue Dec 26 20:11:26 2023 daemon.notice netifd: wan (6272): udhcpc: started, v1.36.1
Tue Dec 26 20:11:26 2023 daemon.notice netifd: wan (6272): udhcpc: broadcasting discover
Tue Dec 26 20:11:27 2023 daemon.notice netifd: wan (6272): udhcpc: received SIGTERM
Tue Dec 26 20:11:27 2023 daemon.notice netifd: wan (6272): udhcpc: entering released state
Tue Dec 26 20:11:40 2023 daemon.notice netifd: wan (6401): udhcpc: started, v1.36.1
Tue Dec 26 20:11:40 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting discover
Tue Dec 26 20:11:43 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting discover
Tue Dec 26 20:11:43 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting select for 192.168.100.10, server 192.168.100.1
Tue Dec 26 20:11:44 2023 daemon.notice netifd: wan (6401): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:11:59 2023 daemon.notice netifd: wan (6401): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:12:00 2023 daemon.notice netifd: wan (6401): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:12:16 2023 daemon.notice netifd: wan (6401): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:12:17 2023 daemon.notice netifd: wan (6401): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:12:32 2023 daemon.notice netifd: wan (6401): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:12:35 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting renew
Tue Dec 26 20:12:38 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting renew
Tue Dec 26 20:12:41 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting renew
Tue Dec 26 20:12:44 2023 daemon.notice netifd: wan (6401): udhcpc: lease lost, entering init state
Tue Dec 26 20:12:44 2023 daemon.notice netifd: wan (6401): udhcpc: broadcasting discover
Tue Dec 26 20:14:45 2023 daemon.notice netifd: wan (6401): udhcpc: received SIGTERM
Tue Dec 26 20:14:45 2023 daemon.notice netifd: wan (6401): udhcpc: entering released state
Tue Dec 26 20:15:08 2023 daemon.notice netifd: wan (6811): udhcpc: started, v1.36.1
Tue Dec 26 20:15:08 2023 daemon.notice netifd: wan (6811): udhcpc: broadcasting discover
Tue Dec 26 20:15:11 2023 daemon.notice netifd: wan (6811): udhcpc: broadcasting discover
Tue Dec 26 20:15:14 2023 daemon.notice netifd: wan (6811): udhcpc: broadcasting discover
Tue Dec 26 20:15:22 2023 daemon.notice netifd: wan (6811): udhcpc: received SIGTERM
Tue Dec 26 20:15:23 2023 daemon.notice netifd: wan (6811): udhcpc: entering released state
Tue Dec 26 20:15:26 2023 daemon.notice netifd: wan (6940): udhcpc: started, v1.36.1
Tue Dec 26 20:15:26 2023 daemon.notice netifd: wan (6940): udhcpc: broadcasting discover
Tue Dec 26 20:15:27 2023 daemon.notice netifd: wan (6940): udhcpc: received SIGTERM
Tue Dec 26 20:15:27 2023 daemon.notice netifd: wan (6940): udhcpc: entering released state
Tue Dec 26 20:15:40 2023 daemon.notice netifd: wan (7069): udhcpc: started, v1.36.1
Tue Dec 26 20:15:40 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting discover
Tue Dec 26 20:15:43 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting discover
Tue Dec 26 20:15:43 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting select for 192.168.100.10, server 192.168.100.1
Tue Dec 26 20:15:45 2023 daemon.notice netifd: wan (7069): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:16:00 2023 daemon.notice netifd: wan (7069): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:16:01 2023 daemon.notice netifd: wan (7069): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:16:16 2023 daemon.notice netifd: wan (7069): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:16:17 2023 daemon.notice netifd: wan (7069): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:16:32 2023 daemon.notice netifd: wan (7069): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:16:35 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting renew
Tue Dec 26 20:16:38 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting renew
Tue Dec 26 20:16:41 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting renew
Tue Dec 26 20:16:44 2023 daemon.notice netifd: wan (7069): udhcpc: lease lost, entering init state
Tue Dec 26 20:16:44 2023 daemon.notice netifd: wan (7069): udhcpc: broadcasting discover
Tue Dec 26 20:19:04 2023 daemon.notice netifd: wan (7069): udhcpc: received SIGTERM
Tue Dec 26 20:19:04 2023 daemon.notice netifd: wan (7069): udhcpc: entering released state
Tue Dec 26 20:19:04 2023 daemon.notice netifd: wan (7458): udhcpc: started, v1.36.1
Tue Dec 26 20:19:04 2023 daemon.notice netifd: wan (7458): udhcpc: broadcasting discover
Tue Dec 26 20:19:08 2023 daemon.notice netifd: wan (7458): udhcpc: broadcasting discover
Tue Dec 26 20:19:11 2023 daemon.notice netifd: wan (7458): udhcpc: broadcasting discover
Tue Dec 26 20:21:30 2023 daemon.notice netifd: wan (7458): udhcpc: received SIGTERM
Tue Dec 26 20:21:30 2023 daemon.notice netifd: wan (7458): udhcpc: entering released state
Tue Dec 26 20:21:30 2023 daemon.notice netifd: wan (7824): udhcpc: started, v1.36.1
Tue Dec 26 20:21:30 2023 daemon.notice netifd: wan (7824): udhcpc: broadcasting discover
Tue Dec 26 20:21:33 2023 daemon.notice netifd: wan (7824): udhcpc: broadcasting discover
Tue Dec 26 20:21:36 2023 daemon.notice netifd: wan (7824): udhcpc: broadcasting discover
Tue Dec 26 20:23:44 2023 daemon.notice netifd: wan (7824): udhcpc: received SIGTERM
Tue Dec 26 20:23:44 2023 daemon.notice netifd: wan (7824): udhcpc: entering released state
Tue Dec 26 20:23:53 2023 daemon.notice netifd: wan (8073): udhcpc: started, v1.36.1
Tue Dec 26 20:23:53 2023 daemon.notice netifd: wan (8073): udhcpc: broadcasting discover
Tue Dec 26 20:23:56 2023 daemon.notice netifd: wan (8073): udhcpc: broadcasting discover
Tue Dec 26 20:24:00 2023 daemon.notice netifd: wan (8073): udhcpc: broadcasting discover
Tue Dec 26 20:24:56 2023 daemon.notice netifd: wan (8073): udhcpc: received SIGTERM
Tue Dec 26 20:24:56 2023 daemon.notice netifd: wan (8073): udhcpc: entering released state
Tue Dec 26 20:24:56 2023 daemon.notice netifd: wan (8160): udhcpc: started, v1.36.1
Tue Dec 26 20:24:56 2023 daemon.notice netifd: wan (8160): udhcpc: broadcasting discover
Tue Dec 26 20:24:59 2023 daemon.notice netifd: wan (8160): udhcpc: broadcasting discover
Tue Dec 26 20:25:02 2023 daemon.notice netifd: wan (8160): udhcpc: broadcasting discover
Tue Dec 26 20:25:12 2023 daemon.notice netifd: wan (8160): udhcpc: received SIGTERM
Tue Dec 26 20:25:12 2023 daemon.notice netifd: wan (8160): udhcpc: entering released state
Tue Dec 26 20:25:15 2023 daemon.notice netifd: wan (8480): udhcpc: started, v1.36.1
Tue Dec 26 20:25:15 2023 daemon.notice netifd: wan (8480): udhcpc: broadcasting discover
Tue Dec 26 20:25:18 2023 daemon.notice netifd: wan (8480): udhcpc: broadcasting discover
Tue Dec 26 20:25:21 2023 daemon.notice netifd: wan (8480): udhcpc: broadcasting discover
Tue Dec 26 20:26:23 2023 daemon.notice netifd: wan (8480): udhcpc: received SIGTERM
Tue Dec 26 20:26:23 2023 daemon.notice netifd: wan (8480): udhcpc: entering released state
Tue Dec 26 20:26:29 2023 daemon.notice netifd: wan (8628): udhcpc: started, v1.36.1
Tue Dec 26 20:26:29 2023 daemon.notice netifd: wan (8628): udhcpc: broadcasting discover
Tue Dec 26 20:26:32 2023 daemon.notice netifd: wan (8628): udhcpc: broadcasting discover
Tue Dec 26 20:26:35 2023 daemon.notice netifd: wan (8628): udhcpc: broadcasting discover
Tue Dec 26 20:26:41 2023 daemon.notice netifd: wan (8628): udhcpc: received SIGTERM
Tue Dec 26 20:26:41 2023 daemon.notice netifd: wan (8628): udhcpc: entering released state
Tue Dec 26 20:26:52 2023 daemon.notice netifd: wan (8764): udhcpc: started, v1.36.1
Tue Dec 26 20:26:52 2023 daemon.notice netifd: wan (8764): udhcpc: broadcasting discover
Tue Dec 26 20:26:55 2023 daemon.notice netifd: wan (8764): udhcpc: broadcasting discover
Tue Dec 26 20:26:58 2023 daemon.notice netifd: wan (8764): udhcpc: broadcasting discover
Tue Dec 26 20:27:07 2023 daemon.notice netifd: wan (8764): udhcpc: received SIGTERM
Tue Dec 26 20:27:07 2023 daemon.notice netifd: wan (8764): udhcpc: entering released state
Tue Dec 26 20:27:24 2023 daemon.notice netifd: wan (8903): udhcpc: started, v1.36.1
Tue Dec 26 20:27:24 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting discover
Tue Dec 26 20:27:27 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting discover
Tue Dec 26 20:27:28 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting select for 192.168.100.10, server 192.168.100.1
Tue Dec 26 20:27:29 2023 daemon.notice netifd: wan (8903): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:27:44 2023 daemon.notice netifd: wan (8903): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:27:45 2023 daemon.notice netifd: wan (8903): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:28:00 2023 daemon.notice netifd: wan (8903): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:28:01 2023 daemon.notice netifd: wan (8903): udhcpc: lease of 192.168.100.10 obtained from 192.168.100.1, lease time 20
Tue Dec 26 20:28:16 2023 daemon.notice netifd: wan (8903): udhcpc: sending renew to server 192.168.100.1
Tue Dec 26 20:28:19 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting renew
Tue Dec 26 20:28:22 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting renew
Tue Dec 26 20:28:25 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting renew
Tue Dec 26 20:28:28 2023 daemon.notice netifd: wan (8903): udhcpc: lease lost, entering init state
Tue Dec 26 20:28:29 2023 daemon.notice netifd: wan (8903): udhcpc: broadcasting discover
You're not actually getting an IP from Comcast... instead, what is happening is a lease is being issued from the cable modem's status interface. This strongly suggests that the cable modem has another MAC address that it has 'learned' and therefore it will not issue an IP to another device.
You must clear the learned MAC via the reboot process that I described earlier. Did you do that? I used to have to do it several times (say 3-5 times) with nothing connected.
P.S. That lease is only 20 seconds, so yeah, it stands to reason that it's being dropped quickly!
Only make this change if the reboots don't work...
Network > Interfaces > Devices (tab) > wan > configure (button) > MAC address
If you plug a different router or a computer into the cable modem and it successfully gets an IP, you will then look for that device's MAC and enter that in the field for your wan.
But as I type this, it looks like you're in businesss! (leaving the above for reference for you later or for any future readers).
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks!