LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 06-30-2020, 08:17 PM   #1
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Rep: Reputation: Disabled
Some (but not all) network hosts can't talk to each other


I'm having trouble with my local network. All the Linux hosts get DHCP addresses and connectivity. The problem is that they're not always able to communicate (SSH, ping) with each other. I've got two WiFi routers configured on channels far apart from each other. One router (my ISP's device) is at 192.168.1.1 and my TPLink AC1200 router is configured as an access point on the same network at 192.168.1.2.

Right now I've got a Raspberry Pi that was assigned 192.168.1.16 and has internet connectivity, but can't be seen or accessed from my primary workstation - even when it's connected through the same router (that would be the TPLink, at the moment). And I can't SSH from the Pi to my workstation, But my laptop - on the same network and logged in through the same router - can SSH in and pick the Pi up on nmap.

Another issue that I think may be related is that, for some reason, I'm not always able to refer to all the hosts by "hostname.local" - although they'll generally work using the IP address (except when they're "off" the network, of course).

Any ideas?
Thanks,
 
Old 06-30-2020, 08:28 PM   #2
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,703

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Quote:
Right now I've got a Raspberry Pi that was assigned 192.168.1.16 and has internet connectivity, but can't be seen or accessed from my primary workstation
Can you ping the Pi host via the primary workstation successfully?
Code:
ping 192.168.1.16
With respect to Avahi...
Code:
avahi-browse -art
*You may need to discover avahi-utils package first.

Check for active firewalls on the host you're trying to reach.
 
1 members found this post helpful.
Old 06-30-2020, 08:36 PM   #3
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
Can you ping the Pi host via the primary workstation successfully?
Code:
ping 192.168.1.16
Nothing:
Code:
$ ping 192.168.1.16
PING 192.168.1.16 (192.168.1.16) 56(84) bytes of data.
From 192.168.1.13 icmp_seq=1 Destination Host Unreachable
Quote:
With respect to Avahi...
Code:
avahi-browse -art
*You may need to discover avahi-utils package first.
I've attached the avahi output: avahi.txt
As you can see, this is a busy machine - lots of LXD bridges etc.

Quote:

Check for active firewalls on the host you're trying to reach.
[/QUOTE]
Good point. I forgot to mention that there are no firewalls on the local network.
Thanks,
 
Old 06-30-2020, 08:58 PM   #4
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,703

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Can you confirm the ip assignments on the pi at this time?
Code:
ip address
Code:
ip route
 
Old 06-30-2020, 09:05 PM   #5
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
Can you confirm the ip assignments on the pi at this time?
Code:
ip address
Code:
$ ip a
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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b8:27:eb:2e:69:db brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:7b:3c:8e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.16/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 85877sec preferred_lft 75077sec
    inet6 fe80::9181:da2:27d5:37e/64 scope link 
       valid_lft forever preferred_lft forever
Quote:
Code:
ip route
Code:
$ ip route
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.16 metric 303 
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.16 metric 303
 
Old 06-30-2020, 09:13 PM   #6
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,703

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
I know you said there was no firewall on any host....but just to be sure, run this from the Pi...
Code:
sudo iptables -S
 
Old 06-30-2020, 09:17 PM   #7
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,703

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Regarding this comment...
Quote:
I've got two WiFi routers configured on channels far apart from each other. One router (my ISP's device) is at 192.168.1.1 and my TPLink AC1200 router is configured as an access point on the same network at 192.168.1.2.
Can you confirm that both hosts are connected to the same wifi AP?
Code:
iw dev wlan0 link
or via older iwconfig command...
Code:
iwconfig wlan0
 
2 members found this post helpful.
Old 06-30-2020, 09:18 PM   #8
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
I know you said there was no firewall on any host....but just to be sure, run this from the Pi...
Code:
sudo iptables -S
This is a completely fresh install on the Pi:

Code:
$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
The truth is that the Pi is just a current example of the problem. I've been having similar issues with other hosts on this LAN.
 
Old 06-30-2020, 09:25 PM   #9
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,703

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
If you have hosts connected via different wifi AP's this might present an issue (eg multicast traffic being blocked), although pinging should work with no issue. Some APs have features to keep wifi client hosts from being able to talk directly to each other as well.

Just in case this is applicable...
https://www.tp-link.com/us/support/faq/2089/

Last edited by ferrari; 06-30-2020 at 09:31 PM.
 
1 members found this post helpful.
Old 06-30-2020, 10:35 PM   #10
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
If you have hosts connected via different wifi AP's this might present an issue (eg multicast traffic being blocked), although pinging should work with no issue. Some APs have features to keep wifi client hosts from being able to talk directly to each other as well.

Just in case this is applicable...
https://www.tp-link.com/us/support/faq/2089/
That is interesting. My TPLink model doesn't seem to have that function. But in any case, in at least my current setup, all three hosts (my workstation, my laptop, and the Pi) were attached to the same router - but only two were able to talk to each other.
Thanks,
 
Old 06-30-2020, 11:00 PM   #11
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Original Poster
Rep: Reputation: Disabled
Just a quick update: A couple of hours later, the Pi suddenly became available for SSH from my workstation. This is exactly the unpredictable behavior I've been experiencing with other hosts. Is it possible that there's something buggy about the way ARP is caching my host addresses and, for some hosts, it's taking a very long time? Full disclosure: I don't know all that much about ARP, but I'd like to hear what people who do understand it think.
 
Old 06-30-2020, 11:06 PM   #12
tinfoil3d
Member
 
Registered: Apr 2020
Location: Japan/RJCC
Distribution: debian, lfs, whatever else i need in qemu
Posts: 231

Rep: Reputation: Disabled
dlanced, as ferrari mentioned, I also have a strong suspicion if both of your wifi AP have same keys and name then your systems might roam between them sometimes which would cause them to split. Make sure the devices are connected to the same AP.
 
1 members found this post helpful.
Old 06-30-2020, 11:10 PM   #13
dlanced
Member
 
Registered: Apr 2014
Location: Canada
Distribution: Ubuntu, Kali Linux
Posts: 36

Original Poster
Rep: Reputation: Disabled
Thanks. I have indeed seen some flipping between APs over the past months.
But all three of the devices I've been watching through the past six hours have been on the same AP. Besides that, why should they split even if they are one different APs? They're all on the same network.
 
Old 06-30-2020, 11:33 PM   #14
tinfoil3d
Member
 
Registered: Apr 2020
Location: Japan/RJCC
Distribution: debian, lfs, whatever else i need in qemu
Posts: 231

Rep: Reputation: Disabled
If your tp-link isn't configured as a bridge then they'd be on the same network the same way my 192.168.1.2 is on the same network as you.
 
1 members found this post helpful.
Old 07-01-2020, 03:08 AM   #15
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,703

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Yes, I agree... focus your attention on the second AP device. I assume it is connected via ethernet? (Refer below link)
https://www.tp-link.com/en/support/faq/417/

WDS Bridging is described here
https://www.tp-link.com/us/support/faq/440/

Last edited by ferrari; 07-01-2020 at 03:09 AM.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
I want few users which is in aliases can send mail to each other but not other mail users in postfix Chitra Gurung Linux - Server 4 07-07-2016 01:26 PM
I can't really figure out why these two hosts can ping each other Berkut83 Linux - Networking 19 03-17-2006 03:17 PM
how can I get a wired and wireless computer to talk to each other r_squared Linux - Wireless Networking 3 06-26-2005 10:17 AM
Can my computers talk to each other? Amos Ku Linux - Software 3 09-10-2003 08:17 AM
can't see other machines but they can see each other Silly22 Linux - Networking 1 11-20-2002 03:28 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 10:21 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration