No Internet - WiFi - DHCP\DNS?
I wonder if somebody could have a look at this config as I'm having issues with a certain WiFi VLAN that is accessed on EAP225 & 245 and controlled by OC200 (SDN).
Issue: Connecting to VLAN30, my client devices connect and get a DHCP IP address (all statically configured for this particular VLAN via DHCP) and shows DNS as connected. However, 'No Internet' is shown. Sometimes after several minutes, it will connect to the internet. The issue appears to be temperamental.
I did change my DNS from an Edgerouter to a Pi-hole (both on VLAN1), however, since the upgrade to SDN I had, had already experienced some issues with the WiFi, showing 'No internet' and then connecting to correct SSID. Another issues since SDN is roaming between the EAP225 & 245. Extremely slow to pick up the stronger signal but this worked perfectly before the upgrade (no fast roaming etc set, I just use Max RSSI to achieve the desired result).
Hardware
Edgerouter ERX
DHCP on, statically assigned IPs for devices (generally)
DHCP server = 'use-dnsmasq'
VLANS = each have their own subnet & DHCP
VLAN1 (IPs range changed on this thread, as public) 10.10.1.1
VLAN30 10.10.30.1
OC200 10.10.1.3 statically assigned from DHCP 10.20.1.1 range (static IP table)
EAPS
225 10.10.1.4 statically assigned from DHCP 10.20.1.1 range (static IP table)
245 10.10.1.5 statically assigned from DHCP 10.20.1.1 range (static IP table)
Settings in Omada software = all DHCP assigned from 10.10.1.1 (as above)
DNS FORWARDING Settings
Name-server = 10.10.1.253 (Pi-Hole)
Listin On = All switch0 interfaces (including VLAN30)
System name-server = 127.0.0.1
Pi-hole
DNS 1.1.1.2, 1.0.0.2
All VLANS in the individaul DHCP setup are configured to use their own DNS i.e. 10.10.1.1 = VLAN1, 10.10.30.1 = VLAN30
Now, as I understand it, DNS requests will be forwarded from each DHCP VLAN service back to the router DHCPs (10.10.1.1, 10.10.30.1), which will forward on to the Pi-hole 10.10.1.253 (DNS forwarding) and can use DNSmasq.Is this correct or should the 'name-server' be the routers IP of 10.10.1.1 and not 127.0.0.1? This is the onlt thing I can think off thats possibly throwing the errors but what is strange its only what is conencted on the EAPs, all other hard wired VLANs are fine and have the same DNS\DHCP setups.
All VLAN local In firewalls have rules for DHCP and DNS to be allowed to the Pi-hole address.
Ethernet ports on the router are in a swtich config and those connected to the OC200 have a PVID=1(U) the EAPS=PVID=1(U),30 (T), VLAN1 trunk to switch (U), all other VLANS tagged.
Finally, as stated its only the EAP connected devices that have this issue, no ethernet based connections do. I remember prior to SDN that both the OC200 & EAPs were a bit finicky with their DHCP.