I cannot reach the computers on the wireless segment of the lan

Felix Rubio felix at kngnt.org
Sun Oct 18 04:10:27 EDT 2020


Another update: I have observed that when doing a ping to a wireless printer from a lan client, the response is "Destination Host Unreachable", whereas I can successfully ping the printer from the host hostap is running on. This has made me thing that maybe is not a hostap issue but a routing issue.

What I have, in this experiment is:

----------------                    --------------                        ---------------
| client     |   -- LAN--> | hostap |   -- WLAN--> | printer |
----------------                    --------------                        ---------------

in client, my routing table was:
    default via 192.168.178.1 dev bond0 proto dhcp src 192.168.178.6 metric 1024 
    192.168.178.0/24 dev bond0 proto kernel scope link src 192.168.178.6 
    192.168.178.1 dev bond0 proto dhcp scope link src 192.168.178.6 metric 1024

With this, if I was running telnet to the printer (IP 192.168.178.18) from client and "tcpdump -i eth0 port 515" on hostap, I was getting no packets received in the latter.

If I add the route to the host 192.168.178.18 via the hostap, on the client, running the same telnet and tcpdump experiment results in packets getting to hostap... but those packets are still not forwarded to the printer. I have checked again that I have no firewall running on the host, during the experiment, and that net.ipv4.ip_forward is set to 1.

So... even though seems I have a routing problem on the network, when this problem is addressed by adding the routes the host running hostap is still not forwarding the packets to the printer :-/ any ideas?

Thank you!


On Sunday, 18 October 2020 08:50:46 CEST Felix Rubio wrote:
> I have similar outputs. Interfaces enp1s0, enp3s0 and wlan0 are part of br0:
> 
> # ip add
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
> 2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master br0 state DOWN group default qlen 1000
>     link/ether c0:4a:00:02:69:ba brd ff:ff:ff:ff:ff:ff
> 3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
>     link/ether 1c:6f:65:c6:bf:cc brd ff:ff:ff:ff:ff:ff
> 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000
>     link/ether d0:37:45:9f:57:64 brd ff:ff:ff:ff:ff:ff
> 8: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
>     link/ether 96:52:73:dd:9b:00 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.178.4/24 brd 192.168.178.255 scope global br0
>        valid_lft forever preferred_lft forever
>     inet 192.168.178.5/24 brd 192.168.178.255 scope global secondary br0
>        valid_lft forever preferred_lft forever
> 
> # ip route
> default via 192.168.178.1 dev br0 proto static
> 192.168.178.0/24 dev br0 proto kernel scope link src 192.168.178.4
> 
> > On 17/10/2020 17:46, Felix Rubio wrote:
> > > Thank you for your suggestion, Jan... but still does not work. This is what I get, related to the bridge:
> > > 
> > > nl80211: Interface wlxd037459f5764 is in bridge br0
> > > nl80211: Add own interface ifindex 8 (ifidx_reason 5)
> > > nl80211: if_indices[16]: 8(5)
> > > nl80211: Add own interface ifindex 5 (ifidx_reason -1)
> > > nl80211: if_indices[16]: 8(5) 5(-1)
> > 
> > Okay, another suggestion. The IP address is attached to the bridge, and
> > not to any of the other interfaces, right? This is what ifconfig looks
> > like on my AP:
> > 
> > # ifconfig
> > br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> >         inet 192.168.1.2  netmask 255.255.255.0  broadcast 192.168.1.255
> >         ether 00:08:a2:0a:89:96  txqueuelen 1000  (Ethernet)
> >         RX packets 45669683  bytes 14474015653 (13.4 GiB)
> >         RX errors 0  dropped 0  overruns 0  frame 0
> >         TX packets 63672667  bytes 58122458205 (54.1 GiB)
> >         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > 
> > (...)
> > 
> > eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> >         ether 00:08:a2:0a:89:96  txqueuelen 2  (Ethernet)
> >         RX packets 58609440  bytes 41063687889 (38.2 GiB)
> >         RX errors 0  dropped 280  overruns 0  frame 0
> >         TX packets 60659751  bytes 56371849168 (52.5 GiB)
> >         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> >         device memory 0xdfdc0000-dfddffff
> > 
> > (...)
> > 
> > wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> >         ether 04:f0:21:22:ec:54  txqueuelen 12  (Ethernet)
> >         RX packets 1164267  bytes 463783891 (442.2 MiB)
> >         RX errors 0  dropped 0  overruns 0  frame 0
> >         TX packets 4829459  bytes 2785669223 (2.5 GiB)
> >         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > 
> > wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> >         ether 04:f0:21:3b:f8:a7  txqueuelen 12  (Ethernet)
> >         RX packets 622058  bytes 632089123 (602.8 MiB)
> >         RX errors 0  dropped 0  overruns 0  frame 0
> >         TX packets 483780  bytes 371002757 (353.8 MiB)
> >         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > 
> > # brctl show
> > bridge name	bridge id		STP enabled	interfaces
> > br0		8000.0008a20a8996	no		eth1
> > 							wlan0
> > 							wlan1
> > 
> > 
> > 
> 
> 
> 
> 
> 
> _______________________________________________
> Hostap mailing list
> Hostap at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/hostap
> 







More information about the Hostap mailing list