Not sure I created it correctly. Clicked on Multiple DHCP Server +
IP Address None, Interface br0, Enable On, Start 100, Max 50, Lease time 1440.
Rebooted with no success. Seems like there needs to be an IP address/range instead of none.
I wasn't sure if this would work or not being that br0 is already assigned the LAN IP of the router. I guess it doesn't. Thanks for trying anyway. I hoped it would work, but I think I understand why it doesn't.
We may need an expert for dhcp servers to chime in, and I am not one.
Just delete it and turn on the main dhcp server again and make sure logging is enabled, both syslogd and klogd enabled in Services, ssh into the router and run this command:
Code:
tail -f /var/log/messages
and watch the log as a device tries to get a dhcp assignment. Hopefully it will show us the error. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Not sure I created it correctly. Clicked on Multiple DHCP Server +
IP Address None, Interface br0, Enable On, Start 100, Max 50, Lease time 1440.
Rebooted with no success. Seems like there needs to be an IP address/range instead of none.
I wasn't sure if this would work or not being that br0 is already assigned the LAN IP of the router. I guess it doesn't. Thanks for trying anyway. I hoped it would work, but I think I understand why it doesn't.
We may need an expert for dhcp servers to chime in, and I am not one.
Just delete it and turn on the main dhcp server again and make sure logging is enabled, both syslogd and klogd enabled in Services, ssh into the router and run this command:
Code:
tail -f /var/log/messages
and watch the log as a device tries to get a dhcp assignment. Hopefully it will show us the error.
Dec 31 17:02:09 IdahoMesh kern.warn kernel: [ 129.251435] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: authenticated
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: associated (aid 1)
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 RADIUS: starting accounting session ADAE3165E4A4307B
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 WPA: pairwise key handshake completed (RSN)
Dec 31 17:06:30 IdahoMesh kern.warn kernel: [ 390.209611] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
Dec 31 17:06:31 IdahoMesh kern.warn kernel: [ 391.204753] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
Dec 31 17:06:33 IdahoMesh kern.warn kernel: [ 393.195342] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
Dec 31 17:06:45 IdahoMesh kern.warn kernel: [ 405.134103] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
Dec 31 17:07:09 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: disassociated
Dec 31 17:07:09 IdahoMesh kern.info kernel: [ 429.113389] ath11k c000000.wifi: nss mac 1 peer 9 mem freed
Dec 31 17:07:10 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) _________________ Linksys MX4300: Primary & Node
Netgear XR500, R7800
Asus AC87U A1, RT-AC68R A1, RT-AC66U A1 retired
Repeater Bridge
Netgear R6400v2otp
I'm a bit confused are you using the EA8500 5g radio in a mesh or wds? If mesh are you using it for both backhaul and client traffic?
I'd like to do something similar with an R9000 as primary and mx4300 to service a remote area.
No the EA8500 is not involved at all in the mesh. It's the main Gateway/DHCP server/VLAN trunk.
Simply put:
Internet<>EA8500<>House Managed Switch<>Garage Managed Switch<>MX4300(((mesh)))MR7350
There's much more here, but this is my layout, in a nutshell. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Dec 31 17:02:09 IdahoMesh kern.warn kernel: [ 129.251435] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: authenticated
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: associated (aid 1)
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 RADIUS: starting accounting session ADAE3165E4A4307B
Dec 31 17:04:04 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 WPA: pairwise key handshake completed (RSN)
Dec 31 17:06:30 IdahoMesh kern.warn kernel: [ 390.209611] ath11k c000000.wifi: unknown packet type received in mesh link vdev 1057137716
...
Dec 31 17:07:10 IdahoMesh daemon.info hostapd: wlan1: STA e2:7f:bd:40:36:03 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
So the DHCP server works normally for everything else, but not through the mesh. Would this be a correct assessment?
There is a setting in the Wireless Advanced Settings/802.11 Mesh Settings called Layer 2 Forwarding. Try disabling it. Warning, it may break the Mesh. I have no idea but be prepared for that. Then you will likely need to add a wire back to access it to turn it back on. This would also likely break any vlans if using them over the mesh (I am). _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Disabled in Node, no difference
Disabled in Node and disabled in Primary no difference
Disabled in Primary no difference
No effect either way trying to access the DHCP Server on the Primary _________________ Linksys MX4300: Primary & Node
Netgear XR500, R7800
Asus AC87U A1, RT-AC68R A1, RT-AC66U A1 retired
Repeater Bridge
Netgear R6400v2otp
Okay, bummer. Unless somebody else knows what those errors means, it may have to be pushed up the food chain to the developer. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Posted: Sat Sep 21, 2024 22:18 Post subject: eoip tunnels
@lexridge, so the main stream beta does not appear to have the fix for the eoip tunnels bootlop. I tried it to today. i am back to DD-WRT v3.0-r58376 std (09/11/24.
Good news though is I got the dd-wrt WG Server and DD-WRT Client to work. _________________ 5 Linksys MX4300 LN1301 DD-WRT v3.0-r58376 std (09/11/24)
As, instructed I reflashed to stock and have the blue Linksys screen. I flashed first factory2ddwrt and then flashed webupgrade. After more testing, the behaviour only happens the 2.4 radio. If I create 2+ VAP on the 5Ghz, it works as expected, but on the 2.4Ghz radio, it doesn't work with more than 1 VAP and the also bridge disappears for all the 2.4 VAP's. I just tested on the lastest version r38389 (9/20/24) with the same results.
When you say the bridge disappears, which bridge precisely? All VAPs would default to br0 and if br0 is disappearing you would completely loose access to the router. This would also be the same for the 5ghz radio. It too defaults to br0. Are you creating additional bridges? If so, you are leaving out a lot of pertinent information here.
After a lot of trial and error, it turns out that the using WEP for wireless security on a VAP was causing the radio issues I was having and NOT the number of VAP's. The work-around was to disable wireless security and all my issues disappeared! Hope this info helps someone.
After a lot of trial and error, it turns out that the using WEP for wireless security on a VAP was causing the radio issues I was having and NOT the number of VAP's. The work-around was to disable wireless security and all my issues disappeared! Hope this info helps someone.
You were using WEP? Seriously? So you went from WEP to no security. Sounds like a great idea. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
After a lot of trial and error, it turns out that the using WEP for wireless security on a VAP was causing the radio issues I was having and NOT the number of VAP's. The work-around was to disable wireless security and all my issues disappeared! Hope this info helps someone.
You were using WEP? Seriously? So you went from WEP to no security. Sounds like a great idea.
I couldn't believe what I had just read.... even if I lived on the moon alone, I wouldn't use WEP, let alone NO SECURITY! lmao
Posted: Sun Sep 22, 2024 17:00 Post subject: Band Steering Options cause disconnect "AP temporarily
Turn on band-steering options and my phone gets disconnected from the network "access point temporarily full", I increase more users for DHCP but still got the same issue. Has anyone experienced the same issue?
I have 2 MX4300 connecting LAN-LAN.
Okay, bummer. Unless somebody else knows what those errors means, it may have to be pushed up the food chain to the developer.
I tried to search the error message in the source code and can not find any match.
How do we know if the developers are aware of this? Do we need to create a ticket or bug report for this?
