There are 142 packages installed after a "fresh" flash?
Can I remove all but the ones listed here in installed packages. Easier way?
https://firmware-selector.openwrt.org/?version=23.05.3&target=ath79%2Fnand&id=glinet_gl-ar300m-nor
Also should I be using this NOR version or the Generic AR300M16 ?
The NOR version is the only one that doesn't give an error at the firmware check after upload.
Does it say AR300M-16 on the label?
Then you need the generic version.
The "nor" flash is under the nand section and is a dual flash, bootstrapping from nor and running from nand.
If you try to flash the "nor" image from luci it will quietly fail as it merrilly writes to empty space where the nand chip would have been....
Flashed with the Generic AM300M16 firmware.
Still not getting an IP on WAN.
I don't have a gigabit unmanaged switch handy but below is when I connect to my EdgeRouter X which is gigabit.
AR300M16 negotiates 100Mb so this could be the issue that my ISP NTD and Starlink doesn't want to accept a 100Mb connection and drops it.
Wed Apr 17 09:38:24 2024 daemon.notice netifd: Network device 'eth1' link is up
Wed Apr 17 09:38:24 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Apr 17 09:38:24 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Apr 17 09:38:24 2024 kern.info kernel: [34609.224794] eth1: link up (100Mbps/Full duplex)
Wed Apr 17 09:38:24 2024 daemon.notice netifd: wan (7006): udhcpc: started, v1.36.1
Wed Apr 17 09:38:25 2024 daemon.notice netifd: wan (7006): udhcpc: broadcasting discover
Wed Apr 17 09:38:26 2024 daemon.notice netifd: wan (7006): udhcpc: broadcasting select for 192.168.15.98, server 192.168.15.1
Wed Apr 17 09:38:26 2024 daemon.notice netifd: wan (7006): udhcpc: lease of 192.168.15.98 obtained from 192.168.15.1, lease time 86400
Wed Apr 17 09:38:26 2024 daemon.notice netifd: Interface 'wan' is now up
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Apr 17 09:38:26 2024 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Apr 17 09:38:26 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Wed Apr 17 09:38:27 2024 daemon.warn odhcpd[1535]: No default route present, overriding ra_lifetime!
It could be that, or it could be that Starlink is doing strange things with DHCP per the reddit thread I provided earlier. But now we can conclude that it is not an OpenWrt issue.
An intermediate gigabit switch will be a good test, though.
I have another AR300M16 that I've been having the same problem with but now it is failing to get an IP from local networks. I also tried a cellular modem with no success.
It was working.
Default settings.
Fri Mar 22 22:20:55 2024 daemon.notice netifd: Network device 'eth1' link is down
Fri Mar 22 22:20:55 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Fri Mar 22 22:20:55 2024 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Fri Mar 22 22:20:55 2024 kern.info kernel: [ 148.185172] eth1: link down
Fri Mar 22 22:20:55 2024 daemon.notice netifd: wan (2021): udhcpc: received SIGTERM
Fri Mar 22 22:20:55 2024 daemon.notice netifd: wan (2021): udhcpc: entering released state
Fri Mar 22 22:20:55 2024 daemon.notice netifd: Interface 'wan6' is now down
Fri Mar 22 22:20:56 2024 daemon.notice netifd: wan (2021): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Fri Mar 22 22:20:56 2024 daemon.notice netifd: Interface 'wan' is now down
Fri Mar 22 22:20:57 2024 daemon.warn odhcpd[1360]: No default route present, overriding ra_lifetime!
Fri Mar 22 22:20:57 2024 kern.info kernel: [ 150.273898] eth1: link up (100Mbps/Full duplex)
Fri Mar 22 22:20:57 2024 daemon.notice netifd: Network device 'eth1' link is up
Fri Mar 22 22:20:57 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Mar 22 22:20:57 2024 daemon.notice netifd: Interface 'wan' is setting up now
Fri Mar 22 22:20:57 2024 daemon.notice netifd: Interface 'wan6' has link connectivity
Fri Mar 22 22:20:57 2024 daemon.notice netifd: Interface 'wan6' is setting up now
Fri Mar 22 22:20:58 2024 daemon.notice netifd: wan (2417): udhcpc: started, v1.36.1
Fri Mar 22 22:20:58 2024 daemon.notice netifd: wan (2417): udhcpc: broadcasting discover
Fri Mar 22 22:21:01 2024 daemon.notice netifd: wan (2417): udhcpc: broadcasting discover
Fri Mar 22 22:21:04 2024 daemon.notice netifd: wan (2417): udhcpc: broadcasting discover
Fri Mar 22 22:21:13 2024 daemon.warn odhcpd[1360]: No default route present, overriding ra_lifetime!
Fri Mar 22 22:21:29 2024 daemon.warn odhcpd[1360]: No default route present, overriding ra_lifetime!
We see this, but we don't see any responses from an upstream DHCP server. What is immediately upstream of the wan connection on this device?
Edgerouter X via a TP Link Unmanaged Switch.
Is the ER-X running OpenWrt or EdgeOS? Do other devices get DHCP leases when connected to the same port (and cable) of the TP-Link unmanaged switch?
If you bypass the switch and connect directly to the ER-X, does that change anything?
EdgeOS. Other devices get a leases when connected to same cable/port.
Nope.
Let's look at the config on the problematic AR300M16:
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:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
Connecting to Netgear Nighthawk 4G MR100.
Very different responses from "identical" devices.
First Router, no IP.
Wed Apr 17 11:41:56 2024 daemon.notice netifd: wan (2024): udhcpc: received SIGTERM
Wed Apr 17 11:41:56 2024 daemon.notice netifd: wan (2024): udhcpc: entering released state
Wed Apr 17 11:41:56 2024 daemon.notice netifd: wan (2024): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Wed Apr 17 11:41:56 2024 daemon.notice netifd: Interface 'wan' is now down
Wed Apr 17 11:41:56 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Apr 17 11:41:56 2024 daemon.notice netifd: wan (2334): udhcpc: started, v1.36.1
Wed Apr 17 11:41:56 2024 daemon.notice netifd: wan (2334): udhcpc: broadcasting discover
Wed Apr 17 11:41:57 2024 daemon.warn odhcpd[1361]: No default route present, overriding ra_lifetime!
Wed Apr 17 11:41:59 2024 daemon.notice netifd: wan (2334): udhcpc: broadcasting discover
Wed Apr 17 11:42:02 2024 daemon.notice netifd: wan (2334): udhcpc: broadcasting discover
Second Router, IP obtained.
Wed Apr 17 09:43:59 2024 daemon.notice netifd: Network device 'eth1' link is up
Wed Apr 17 09:43:59 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Apr 17 09:43:59 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Apr 17 09:43:59 2024 kern.info kernel: [ 376.986915] eth1: link up (100Mbps/Full duplex)
Wed Apr 17 09:43:59 2024 daemon.notice netifd: wan (2604): udhcpc: started, v1.36.1
Wed Apr 17 09:43:59 2024 daemon.notice netifd: wan (2604): udhcpc: broadcasting discover
Wed Apr 17 09:44:02 2024 daemon.notice netifd: wan (2604): udhcpc: broadcasting discover
Wed Apr 17 09:44:02 2024 daemon.notice netifd: wan (2604): udhcpc: broadcasting select for 192.168.1.45, server 192.168.1.1
Wed Apr 17 09:44:02 2024 daemon.notice netifd: wan (2604): udhcpc: lease of 192.168.1.45 obtained from 192.168.1.1, lease time 43200
Wed Apr 17 09:44:02 2024 daemon.notice netifd: Interface 'wan' is now up
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Apr 17 09:44:02 2024 daemon.warn dnsmasq[1]: ignoring nameserver 192.168.1.1 - local interface
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Apr 17 09:44:02 2024 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Apr 17 09:44:03 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Wed Apr 17 09:44:03 2024 daemon.warn odhcpd[1361]: No default route present, overriding ra_lifetime!
Sorry, this is the working one with EdgeRouter.
I'll do the non working one now.
ubus call system board
{
"kernel": "5.15.150",
"hostname": "OpenWrt",
"system": "Qualcomm Atheros QCA9533 ver 2 rev 0",
"model": "GL.iNet GL-AR300M16",
"board_name": "glinet,gl-ar300m16",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.3",
"revision": "r23809-234f1a2efa",
"target": "ath79/generic",
"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
}
}
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 'fd36:a02c:f6a9::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'eth1'
option proto 'dhcp'
config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'
option disabled '1'
option reqaddress 'try'
option reqprefix 'auto'
config device
option name 'eth1'
cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option path 'platform/ahb/18100000.wmac'
option channel '1'
option band '2g'
option htmode 'HT20'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
cat /etc/config/dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
option ra_slaac '1'
list ra_flags 'managed-config'
list ra_flags 'other-config'
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'
cat /etc/config/firewall
config defaults
option syn_flood 1
option input REJECT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
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
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
# Allow IPv4 ping
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
# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
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
# Allow essential incoming IPv6 ICMP traffic
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
# Allow essential forwarded IPv6 ICMP traffic
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
### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
# option src lan
# option src_ip 192.168.45.2
# option dest wan
# option proto tcp
# option target REJECT
# block a specific mac on wan
#config rule
# option dest wan
# option src_mac MAC#
# option target REJECT
# block incoming ICMP traffic on a zone
#config rule
# option src lan
# option proto ICMP
# option target DROP
# port redirect port coming in on wan to lan
#config redirect
# option src wan
# option src_dport 80
# option dest lan
# option dest_ip 192.168.16.235
# option dest_port 80
# option proto tcp
# port redirect of remapped ssh port (22001) on wan
#config redirect
# option src wan
# option src_dport 22001
# option dest lan
# option dest_port 22
# option proto tcp
### FULL CONFIG SECTIONS
#config rule
# option src lan
# option src_ip 192.168.45.2
# option src_mac MAC#
# option src_port 80
# option dest wan
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
# option target REJECT
#config redirect
# option src lan
# option src_ip 192.168.45.2
# option src_mac MAC#
# option src_port 1024
# option src_dport 80
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
root@OpenWrt:~#
looks like the default config, so no issues that I see.
I cannot explain why you're having these issues, but I'm quite certain that it is not a universal thing....
In fact, I'll run a test in a moment. I have an ER-X with EdgeOS handy. I'll connect it to a device with a 100Mbps ethernet port (TP-Link TL-WR902AC) and a device with a gigabit port (Linksys E3000)... both of those devices running 23.05.3.
Sorry, that was the working one.
Non working here.
root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.150",
"hostname": "OpenWrt",
"system": "Qualcomm Atheros QCA9533 ver 2 rev 0",
"model": "GL.iNet GL-AR300M16",
"board_name": "glinet,gl-ar300m16",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.3",
"revision": "r23809-234f1a2efa",
"target": "ath79/generic",
"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
}
}
root@OpenWrt:~# 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 'fd52:dbc0:f71f::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'eth1'
option proto 'dhcp'
config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'
root@OpenWrt:~# cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option path 'platform/ahb/18100000.wmac'
option channel '1'
option band '2g'
option htmode 'HT20'
option disabled '1'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
root@OpenWrt:~# cat /etc/config/dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
option ra_slaac '1'
list ra_flags 'managed-config'
list ra_flags 'other-config'
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'
root@OpenWrt:~# cat /etc/config/firewall
config defaults
option syn_flood 1
option input REJECT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
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
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
# Allow IPv4 ping
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
# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
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
# Allow essential incoming IPv6 ICMP traffic
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
# Allow essential forwarded IPv6 ICMP traffic
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
### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
# option src lan
# option src_ip 192.168.45.2
# option dest wan
# option proto tcp
# option target REJECT
# block a specific mac on wan
#config rule
# option dest wan
# option src_mac MAC#
# option target REJECT
# block incoming ICMP traffic on a zone
#config rule
# option src lan
# option proto ICMP
# option target DROP
# port redirect port coming in on wan to lan
#config redirect
# option src wan
# option src_dport 80
# option dest lan
# option dest_ip 192.168.16.235
# option dest_port 80
# option proto tcp
# port redirect of remapped ssh port (22001) on wan
#config redirect
# option src wan
# option src_dport 22001
# option dest lan
# option dest_port 22
# option proto tcp
### FULL CONFIG SECTIONS
#config rule
# option src lan
# option src_ip 192.168.45.2
# option src_mac MAC#
# option src_port 80
# option dest wan
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
# option target REJECT
#config redirect
# option src lan
# option src_ip 192.168.45.2
# option src_mac MAC#
# option src_port 1024
# option src_dport 80
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
root@OpenWrt:~#
From the E3000:
Fri Mar 22 22:12:44 2024 daemon.notice netifd: wan (1822): udhcpc: started, v1.36.1
Fri Mar 22 22:12:45 2024 daemon.notice netifd: wan (1822): udhcpc: broadcasting discover
Fri Mar 22 22:12:48 2024 daemon.notice netifd: wan (1822): udhcpc: broadcasting discover
Fri Mar 22 22:12:51 2024 daemon.notice netifd: wan (1822): udhcpc: broadcasting discover
Fri Mar 22 22:13:32 2024 daemon.notice netifd: wan (1822): udhcpc: broadcasting select for 192.168.1.42, server 192.168.1.1
Fri Mar 22 22:13:32 2024 daemon.notice netifd: wan (1822): udhcpc: lease of 192.168.1.42 obtained from 192.168.1.1, lease time 86400
And from the WR902AC
Mon Mar 25 11:57:42 2024 daemon.notice netifd: wan (4151): udhcpc: started, v1.36.1
Mon Mar 25 11:57:42 2024 daemon.notice netifd: wan (4151): udhcpc: broadcasting discover
Mon Mar 25 11:57:43 2024 daemon.notice netifd: wan (4151): udhcpc: broadcasting select for 192.168.1.43, server 192.168.1.1
Mon Mar 25 11:57:43 2024 daemon.notice netifd: wan (4151): udhcpc: lease of 192.168.1.43 obtained from 192.168.1.1, lease time 86400
Both connect with no issues with an ER-X as the DHCP server (v2.0.9-hotfix.7).
I also know that these connect without issue to my Unifi Dream Machine Pro (DHCP server) via 2 Unifi switches.
@wstan6 did you follow the wiki instructions for flashing the ar300m lite?
https://openwrt.org/toh/gl.inet/gl-ar300m_lite
Looks like if you don't make the wan port the Lan port in stock firmware before flashing that it doesn't come up correctly, only allowing ipv6.
I have a boxed Mango here that I can flash if required
The OP has a different device..
https://openwrt.org/toh/gl.inet/gl-ar300m
The AR300m lite has only one ethernet port, whereas the AR300M has 2 ethernet ports. So the problem with the lite does not impact the regular, at least based on the device info page.
@hecatae
He has confirmed he has the ar300m-16-ext. It has 16MB flash, 128MB ram, wan port, lan port (both 100Mb/s) and external antennas.
There is something wrong with the config/how_he_is_connecting combination.
HINT: Ethernet patch cable
From the network config he has the default ip:
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
But in his working example's logs he has:
The same subnet as in the config.
This may not be the core issue though.
I have used many ar300m-xx in the past and never had a problem - except just one time.
That was very similar (reading my notes from 5 years ago). It turned out to be a slightly damaged rj45 connector on one end of the wan patch cable.
It worked with some ethernet ports, failed on others, but always showed the port coming up on plugging in.
So @wstan6 - Try another ethernet cable......