I’m sure this is my cursory setup or just my knowledge limits.
I run DHCP on IPFire.
I have wireless setup to be access points.
So, whether I connect via hard wire or wifi, my various PC’s, phones, etc. get the same subnet, for example: 192.168.33.xx.
All my hard wires resolve the names on the network fine.
But wifi connected PC’s don’t resolve.
From wired nodes I can ping a wifi node by name and the ip is resolved, but is unreachable.
From wired nodes I can ping a wifi node by ip, no problem.
From wifi nodes I can ping by IP, but not name.
Having setup the wap points in a distant past, did I just leave something set/unset that I should have been more cognizant of?
It is one way to do it. Nothing wrong with it but if you have 300 pc’s on your network it is a lot of work and needs to be repeated if the name server is changed.
The simpler way is to have the IPFire DNS server defined in the DHCP WUI page for green and for blue as shown here.
Then the DNS name server is provided to your clients with their dhcp IP address.
This works very well with Linux but I have heard that sometimes windows clients will ignore this information. In that case you have to manually define the DNS name server in your Windows network configuration.
As you are using blue with a WAP then if you are using phones such as Android or iOS, then they definitely tend to ignore what they are told in terms of DNS servers.
When you have the problem is it with all your clients on the blue network or only a subset of them? If a subset, is there any commonality in the set of clients having the problem?
Okay, clear. You have a WAP(s) attached to your green network.
Same things still apply.
If your Ubuntu system is not picking up the DNS server from the dhcp info then your manual setting of the DNS server in your Ubuntu’s configuration is also a valid approach.
