1
There is home network: 192.168.1.0/24
, default gateway 192.168.1.1
(DHCP)
There is a web server which is running on a host, lets call the host "server".
There are several devices which are connected to the router via wifi (clients).
Problem: clients can't connect to the server when it is connected to the network via wifi. But they are able to connect to it when it is connected via ethernet.
"can't connect" means:
http ://192.168.1.15/myservice
- "Oops! Google Chrome could not connect to 192.168.1.15"telnet/ping
192.168.1.15
- "Destination Host Unreachable"
Server: Ubuntu 12.04 x86_64 (kernel 3.8.0-35-generic)
# ufw status
Status: inactive
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Server ethernet network configuration
# ifconfig eth2
inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0
# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
Server wifi network configuration
# ifconfig eth3
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth3
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3
JIC, I'm able to connect to my wifi interface from(!) the server (but probably it just connects via loopback interface instead).
What the problem?
Wifi access points can be set to not let clients talk to each other. This setting is sometimes called "AP isolation". It could explain the behavior you're experiencing. – Daniel B – 2016-06-04T22:43:40.263