Hey and thanks to anyone taking the time to read this. I have flashed my omada er605 with openwrt no issue very good guides.
My issue is however I have the LAN as normal and I created another sub-net called access point this is connected to port 4.
all is OK the dhcp works they can connect to the access point fine but only my laptops will get to the internet. My mobile phones the access point itself even my iot devices cant talk to the internet.
They can all talk to the access point and get IP address by dhcp but not to the internet, but my laptops can.
As my laptops can talk to the internet I assumed it was not dns but I added 6,8.8.8.8 to the access point to give my devices a direct dns but still only the laptops work.
So I reset that back to normal but still no internet access bar my laptops.
Anyone have any ideas. Have I missed something?
I have 5 ports on my omada router port 0 is wan – port 1234 was on a default br-lan I removed port 4 so as to avoid dhcp conflicts.
I created a new interface called accesspoint and attached port 4.
I added the firewall rules same as the lan accept accept accept and forward to wan.
As stated above it all works fine but I cant get internet on my access point bar my laptops.
I currently have a working pf-sense box but its old and big a n3050 ,so I would like very much to switch to openwrt as this omada device sips power.
ps i tried changing device mac address for port 4 but still not working. phones say connected to device cant provide internet strange.
i will read through that guide and check if all matches. as to the question no i did not read that guide i just used the gui on luci to make the changes.
i have not ssh into the device to check the files directly used to pfsense only ever used gui on that.
it is strange that it is working but not for mobiles would this link explain that and i have two sub-nets not one,thanks.
I figured it out you got me to look at my gateway settings with that link i had set ipv4 address to 192.168.50.0 changed it to 192.168.50.1 and devices area all working now.
thank you for the help sorry about that.
still don't understand why laptops worked but mobiles did not given that fixed it but cheers.
the .0 address in a /24 is technically invalid (as it is the 'network/subnet' address, not intended to be used by a host). Most operating systems will know that and refuse to send traffic to that address even though that is the address provided by DHCP for the gateway. Other operating systems will send the traffic there anyway, despite the fact that there shouldn't be a host at that address. That's why it works for some devices and not for others.
When you fixed the address of the router, the address because valid and therefore all devices/operating systems will send the traffic accordingly.
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!
Beyond what was already stated, I am worried about
an AP should not provide DHCP services to your network, there can only be one DHCPd[0] within your (physical-) network (-segment), and it's usually best placed on your central router[1] (not an AP).
--
[0] unless you go deep enterprise, with cooperating failover DHCPds, possible, but not common at home - and you need to be really up your game, if you take this route. In other words, not common, strongly recommended against, unless you really-really-really know what you're doing.
[1] exceptions exists, e.g. if you are running a Windows Active Directory, which really wants to run its own DHCPd/ DNSd on the domain server - or for things like pihole, AGH or similar, still this is not ideal.
