Can no longer hold IP from Surfboard S33

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:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

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.

are you using the 2.5G port or the 1G port?

I totally didn't notice the two ports were different speeds! I'm on the 2.5G, is that a no-no?

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've swapped cables, I can try again. I've been using the same port the whole time, so the 2.5 was definitely working. I'll try swapping ports.

root@GWIFI1:~# ubus call system board
{
	"kernel": "6.1.55",
	"hostname": "GWIFI1",
	"system": "ARMv7 Processor rev 5 (v7l)",
	"model": "Google WiFi (Gale)",
	"board_name": "google,wifi",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "SNAPSHOT",
		"revision": "r24096-9536446965",
		"target": "ipq40xx/chromium",
		"description": "OpenWrt SNAPSHOT r24096-9536446965"
	}
}
root@GWIFI1:~# cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd92:fd33:5094::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan'

config device
	option name 'lan'
	option macaddr '70:3a:cb:79:ad:20'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '10.0.0.1'
	option netmask '255.255.255.0'
	option ip6assign '60'
	list dns '10.0.0.10'

config device
	option name 'wan'
	option macaddr '70:3a:cb:79:ad:1f'

config interface 'wan'
	option device 'wan'
	option proto 'dhcp'
	option peerdns '0'
	list dns '10.0.0.10'
	option hostname '*'
	option broadcast '1'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'
	option reqaddress 'none'
	option reqprefix 'auto'

root@GWIFI1:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc/a000000.wifi'
	option channel 'auto'
	option band '2g'
	option htmode 'HT20'
	option cell_density '0'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'NODE'
	option encryption 'psk2'
	option key 'UMCU103113'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc/a800000.wifi'
	option channel '153'
	option band '5g'
	option htmode 'VHT80'
	option cell_density '0'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'NODE'
	option encryption 'psk2'
	option key 'UMCU103113'

config wifi-iface 'wifinet2'
	option device 'radio1'
	option mode 'mesh'
	option encryption 'sae'
	option mesh_id 'afce473fbeb2'
	option mesh_fwding '1'
	option mesh_rssi_threshold '0'
	option key '92d51dfb19e1'
	option network 'lan'

root@GWIFI1:~# cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option cachesize '1000'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option localservice '1'
	option ednspacket_max '1232'
	option noresolv '1'

config dhcp 'lan'
	option interface 'lan'
	option start '100'
	option limit '150'
	option leasetime '12h'
	option dhcpv4 'server'
	option dhcpv6 'server'
	option ra 'server'
	list ra_flags 'managed-config'
	list ra_flags 'other-config'
	list dhcp_option '6,10.0.0.10'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'

config host
	option mac 'dc:a6:32:d1:bc:94'
	option ip '10.0.0.10'
	option name 'elektor'
	option dns '1'

config host
	option name 'gpu-0'
	option dns '1'
	option mac '70:85:C2:6F:92:D4'
	option ip '10.0.0.12'

config host
	option name 'elektorNAS'
	option dns '1'
	option mac '90:09:D0:2F:A6:6F'
	option ip '10.0.0.11'

config host
	option name 'MK2S'
	option dns '1'
	option mac 'B8:27:EB:E2:D4:62'
	option ip '10.0.0.21'

config host
	option name 'icebear'
	option dns '1'
	option mac 'E4:5F:01:01:FC:CD'
	option ip '10.0.0.20'

root@GWIFI1:~# cat /etc/config/firewall

config defaults
	option syn_flood '1'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'

config zone
	option name 'lan'
	list network 'lan'
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'ACCEPT'

config zone
	option name 'wan'
	list network 'wan'
	list network 'wan6'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'
	option masq '1'
	option mtu_fix '1'

config forwarding
	option src 'lan'
	option dest 'wan'

config rule
	option name 'Allow-DHCP-Renew'
	option src 'wan'
	option proto 'udp'
	option dest_port '68'
	option target 'ACCEPT'
	option family 'ipv4'

config rule
	option name 'Allow-Ping'
	option src 'wan'
	option proto 'icmp'
	option icmp_type 'echo-request'
	option family 'ipv4'
	option target 'ACCEPT'

config rule
	option name 'Allow-IGMP'
	option src 'wan'
	option proto 'igmp'
	option family 'ipv4'
	option target 'ACCEPT'

config rule
	option name 'Allow-DHCPv6'
	option src 'wan'
	option proto 'udp'
	option dest_port '546'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-MLD'
	option src 'wan'
	option proto 'icmp'
	option src_ip 'fe80::/10'
	list icmp_type '130/0'
	list icmp_type '131/0'
	list icmp_type '132/0'
	list icmp_type '143/0'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-ICMPv6-Input'
	option src 'wan'
	option proto 'icmp'
	list icmp_type 'echo-request'
	list icmp_type 'echo-reply'
	list icmp_type 'destination-unreachable'
	list icmp_type 'packet-too-big'
	list icmp_type 'time-exceeded'
	list icmp_type 'bad-header'
	list icmp_type 'unknown-header-type'
	list icmp_type 'router-solicitation'
	list icmp_type 'neighbour-solicitation'
	list icmp_type 'router-advertisement'
	list icmp_type 'neighbour-advertisement'
	option limit '1000/sec'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-ICMPv6-Forward'
	option src 'wan'
	option dest '*'
	option proto 'icmp'
	list icmp_type 'echo-request'
	list icmp_type 'echo-reply'
	list icmp_type 'destination-unreachable'
	list icmp_type 'packet-too-big'
	list icmp_type 'time-exceeded'
	list icmp_type 'bad-header'
	list icmp_type 'unknown-header-type'
	option limit '1000/sec'
	option family 'ipv6'
	option target 'ACCEPT'

config rule
	option name 'Allow-IPSec-ESP'
	option src 'wan'
	option dest 'lan'
	option proto 'esp'
	option target 'ACCEPT'

config rule
	option name 'Allow-ISAKMP'
	option src 'wan'
	option dest 'lan'
	option dest_port '500'
	option proto 'udp'
	option target 'ACCEPT'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'HTTP'
	option src 'wan'
	option src_dport '80'
	option dest_ip '10.0.0.10'
	option dest_port '80'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'HTTPS'
	option src 'wan'
	option src_dport '443'
	option dest_ip '10.0.0.10'
	option dest_port '443'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option src 'wan'
	option src_dport '587'
	option dest_ip '10.0.0.10'
	option dest_port '587'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option src 'wan'
	option src_dport '993'
	option dest_ip '10.0.0.10'
	option dest_port '993'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'SMTP'
	option src 'wan'
	option src_dport '2525'
	option dest_ip '10.0.0.10'
	option dest_port '2525'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option src 'wan'
	option src_dport '5222'
	option dest_ip '10.0.0.10'
	option dest_port '5222'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option src 'wan'
	option src_dport '5269'
	option dest_ip '10.0.0.10'
	option dest_port '5269'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'SSH'
	option src 'wan'
	option src_dport '3333'
	option dest_ip '10.0.0.10'
	option dest_port '3333'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'DNS Force'
	option src 'wan'
	option src_ip '!10.0.0.10'
	option src_dport '53'
	option dest_ip '10.0.0.10'
	option dest_port '53'

config nat
	option name 'DNS Force'
	list proto 'tcp'
	list proto 'udp'
	option src 'lan'
	option dest_ip '10.0.0.10'
	option dest_port '53'
	option target 'MASQUERADE'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'Transmission Torrent'
	option src 'wan'
	option src_dport '51413'
	option dest_ip '10.0.0.10'
	option dest_port '51413'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'Wireguard'
	option src 'wan'
	option src_dport '8102'
	option dest_ip '10.0.0.10'
	option dest_port '8102'

config redirect
	option dest 'lan'
	option target 'DNAT'
	option name 'Matrix-synapse'
	option src 'wan'
	option src_dport '8448'
	option dest_ip '10.0.0.10'
	option dest_port '8448'

I'd recommend that you upgrade to the latest stable release unless there is a specific reason you are using snapshot:
https://firmware-selector.openwrt.org/?version=23.05.2&target=ipq40xx%2Fchromium&id=google_wifi

You shouldn't need the last two lines in your wan interface stanza, so you can delete those:

I'm using snapshot because that's what the wiki told me at the time! If there's a stable I'll try it.

Updated:

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd92:fd33:5094::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan'

config device
	option name 'lan'
	option macaddr '70:3a:cb:79:ad:20'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '10.0.0.1'
	option netmask '255.255.255.0'
	option ip6assign '60'
	list dns '10.0.0.10'

config device
	option name 'wan'
	option macaddr '70:3a:cb:79:ad:1f'

config interface 'wan'
	option device 'wan'
	option proto 'dhcp'
	option peerdns '0'
	list dns '10.0.0.10'


config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'
	option reqaddress 'none'
	option reqprefix 'auto'

Same result though.

let's see the output of:

logread -e udhcpc

(be sure to redact your public IP address)

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!

I've done a trillion reboots, but not with nothing connected. Let me try 5 of those and report back.

ok... and to be clear, it is rebooting the cable modem.

If that doesn't solve the problem, we can try the MAC address clone method which may fix the issue.

I did try MAC copying earlier but I might have fudged it. For that I just set the Client ID in advanced settings to the same MAC as the modem, yes?

no, it is not the client ID, and no it is also not the MAC of the modem.

Instead, it will be an override of this:

and the address you'll use will be from another router or computer that is able to successfully get an IP from Comcast.

Where in Luci can I find the relevant fields?

NEVER MIND WE GOT A PUBLIC IP!

Thank you so much. That was key, rebooting with finger disconnected. Saved my ass man, thank you!

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! :slight_smile:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.