My two openSUSE machines can't ping each other

English Network/Internet
1

I have three Linux machines at home. Two of them run openSUSE Leap 42.2. The other is running Debian “Stretch” i386.

Machine 1 runs openSUSE Leap 42.2. It has a firewall and is my main desktop machine. It can ping my Debian machine, which can also ping it. It cannot ping machine 3 (info below) which also cannot ping it. It’s local IP address is 192.168.1.7, and it is wirelessly connected to my only access point (IP address 192.168.1.1).

Machine 2 is a tablet running Debian “Stretch” i386. It can ping both of the other machines, which can both also ping it. It’s local address is 192.168.1.14. It has no firewall and is also wirelessly connected to my access point.

Machine 3 is an Oracle VirtualBox (version 5.1.10) machine running openSUSE Leap 42.2. It has exclusive use of its host’s built-in ethernet adapter and is cabled to my access point. It’s IP address is 192.168.1.9. It has no firewall. It cannot ping machine 1 which also cannot ping it. It can ping machine 2 (Debian tablet) which can also ping it.

The lone DNS server for all three machines is 192.168.1.1 (my router) and the gateway for each machine is also 192.168.1.1. The subnet mask for all three machines is set to 255.255.255.0. I am pinging by numerical addresses to avoid any potential DNS issues, and as all three machines are on the same subnet, I don’t think that the gateway information should even matter.

Why can’t machines 1 and 3 see each other? Neither of them have any other apparent networking issues. I intend to make #3 a Samba server, so it is important to me that I get this working.

Thank you!

Will in Missouri, USA

2

Show from your 3 Machine inside Virtualbox:

ifconfig -a
3

“ifconfig -a” produces:

eth0 Link encap:Ethernet HWaddr 5C:F9:DD:6F:68:B3
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::5ef9:ddff:fe6f:68b3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:126154 errors:0 dropped:47 overruns:0 frame:0
TX packets:49987 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:150712050 (143.7 Mb) TX bytes:4309889 (4.1 Mb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:3610 (3.5 Kb) TX bytes:3610 (3.5 Kb)

NOTE: The above smiley in the HW address should be a colon and then an upper-case D.

4

Please use code tags (the # in the form edit window tool bar) This prevents reformatting of text for computer output and also stops the smilies :wink:

5

Will,

Do I understand correctly that machine 3 is a virtual machine running on machine 1?

If that is the case, it might have to do with the way you set up the network in the guest (machine 3). To test that assumption, I installed virtualbox and tried to create a guest with “exclusive use of its host’s built-in ethernet adapter”. That is where I got stuck. On my new guest, in Settings > Network > Attached to, the options are:

  • Not attached
  • NAT
  • NAT Network
  • Bridged Adapter
  • Internal Network
  • Host-only Adapter
  • Generic Driver

Which of those did you choose? Did you set any other settings for the guest’s network?

Kind regards,

Leen

6

Machine 3 runs on a Windows 7 host. The Windows host has a wireless adapter which I am using for it’s Internet connectivity. In Windows networking I unchecked all protocols for the onboard NIC except for “VirtualBox NDIS 6 Bridged Networking Driver.” In VirtualBox, I set the virtual machine to “bridged adapter,” selected the NIC, and went under advanced and set the MAC address to the correct value for the adapter. Machines 1 and 3 can both access the Internet and machine 2… just not each other.

Machine 1 doesn’t have any virtual machines involved in this setup. Once I have Samba installed on machine 3, I will connect to it from a Windows virtual PC on machine 1, but I haven’t gotten that far yet.

7

One piece of information that I realized I haven’t posted…
I connected via ssh to “machine 3” using my Debian tablet. I ran journalctl on machine 3 and saw all of the information about that ssh connection. I also attempted to connect via ssh to machine 3 from my other Leap 42.2 machine. Machine 3’s journal shows nothing about those failed attempts.

8

Will,

thanks for your answer.

I was on the wrong track and I could have known it (I reread your initial post).:shame:Your next remark just comfirms that:

Does the problem persist when the firewall on machine 1 is (temporarily) turned off?

Also, please try

# on machine 1:
ping -c1 192.168.1.9; /sbin/arp 192.168.1.9

and

# on machine 3:
ping -c1 192.168.1.7; /sbin/arp 192.168.1.7

(you do not have to be root). Do both arp’s return anything?

9

Hi Leen,

Does the problem persist when the firewall on machine 1 is (temporarily) turned off?

Yes, I turned off the firewall and got the same results.
On machine 1:

ping -c1 192.168.1.9; /sbin/arp 192.168.1.9

produces

PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data.

--- 192.168.1.9 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.1.9              ether   5c:f9:dd:6f:68:b3   C                     wlan0

On machine 3:

ping -c1 192.168.1.7; /sbin/arp 192.168.1.7

produces

PING 192.168.1.7 (192.168.1.7) 56(84) bytes of data.

--- 192.168.1.7 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.1.7              ether   80:9b:20:d9:de:00   C                     eth0

Thank you,

Will

10

I was curious, so I just went on my Windows host and made a new “Machine 3.” I used the exact same network setup, only I installed Debian Stretch instead of openSUSE. I have the same problem with Debian… Machine 2 can still see machines 1 and 3, but they can’t see each other.

I am now thinking that my three machines are setup fine, and the problem has to do with the router/access point provided to me by my ISP. I am going to look at this from that angle and see what I come up with.

11

There is a lot of missing and confused information here.
And, contrary to your initial post your openSUSE Guest on machine does not have “exclusive use of its host’s built-in ethernet adapter” unless you did something unusual like doing a hardware pass-through of the ethernet adapter. From your description, your Guest is <sharing> a physical adapter on Machine 3.

Re-summarizing
Machine 1
Connection: WiFi
LEAP 42.2
192.168.1.7/24

Machine 2
Connection: WiFi
Debian on a tablet
192.168.14/24

Machine 3
Connection: Wired(802.3) and Wireless
HostOS: Windows 7
Unknown address
GuestOS: LEAP 42.2
Bridged Networking
192.168.1.9

Router
Unknown manufacturer
Wireless and a Wired connection to Machine 3

The following using IPv4 and testing IP addresses only:

What works:
Machine 1 and Machine 3 can ping Machine 2
Machine 2 can ping Machine 1 and Machine 3

What does not work:
Machine 1 cannot ping Machine 3
Machine 3 cannot ping Machine 1

So, now after laying out everything as clearly as possible,
One big issue leaps out at me… Your Machine 3 is configured with active wireless and wired adapters, and they’re both configured with the same networkID (192.168.1.0/24). This is a recipe for problems because contrary to your statement, the Guest is <not> exclusively using the wired or wireless on your network.

Without going into a technical description what’s wrong with using two network adapters configured(You can also look up my prior posts on this in this Forum) with the same NetworkID at the same time (without special configuration like bonding), my initial suggestion is to just disable your wireless… or physically disconnect your wired connection, then reboot your machine (the HostOS). There’s a good chance everything will sort itself out automatically.

For anyone else later who is reading this thread with a similar problem, you may also have to consider how your router is configuring the wired and wireless networks for some problems but I don’t see that as an issue here.

If that doesn’t work, then

  • Post the <entire result> from the following run in Machine 3 (the HostOS aka Windows 7)
ipconfig
  • Post your Virtualbox configuration file. It’s in the folder created that holds your Guest machine files and it will have a “.vbox” extension

HTH,
TSU

12

Here is all of the ipconfig information from my Windows host:

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : 
   IPv4 Address. . . . . . . . . . . : 192.168.1.5
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::a0b3:1ec0:9380:4e8a%13
   IPv4 Address. . . . . . . . . . . : 192.168.56.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 

Tunnel adapter isatap.{66F0E2FB-6E1A-482D-8000-69C621391993}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 

Tunnel adapter isatap.{E67D9EE3-4698-4604-BC49-7E5E66A1B1CC}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

and the .vbox file

<?xml version="1.0"?>
<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.16-windows">
  <Machine uuid="{41824d61-8a17-4975-a83e-1276b9e46666}" name="openSUSE" OSType="OpenSUSE_64" snapshotFolder="Snapshots" lastStateChange="2016-11-28T15:05:41Z">
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid="{139e68eb-9a8b-4e9f-8566-0d8ff0d14082}" location="openSUSE.vdi" format="VDI" type="Normal"/>
      </HardDisks>
      <DVDImages>
        <Image uuid="{586d1320-21ac-4145-875a-431b3319109c}" location="C:/Linux ISOs/openSUSE-Leap-42.2-DVD-x86_64.iso"/>
        <Image uuid="{5d5d40e2-800d-4090-a00b-ee0656b32939}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
      </DVDImages>
    </MediaRegistry>
    <ExtraData>
      <ExtraDataItem name="GUI/LastCloseAction" value="PowerOff"/>
      <ExtraDataItem name="GUI/LastGuestSizeHint" value="1280,960"/>
      <ExtraDataItem name="GUI/LastNormalWindowPosition" value="409,27,800,647"/>
      <ExtraDataItem name="GUI/RestrictedRuntimeDevicesMenuActions" value="HardDrives"/>
      <ExtraDataItem name="GUI/RestrictedRuntimeMachineMenuActions" value="SaveState,PowerOff"/>
      <ExtraDataItem name="GUI/ScaleFactor" value="1"/>
      <ExtraDataItem name="GUI/StatusBar/IndicatorOrder" value="HardDisks,OpticalDisks,FloppyDisks,Network,USB,SharedFolders,Display,VideoCapture,Features,Mouse,Keyboard"/>
    </ExtraData>
    <Hardware>
      <CPU count="2">
        <PAE enabled="true"/>
        <LongMode enabled="true"/>
        <X2APIC enabled="true"/>
        <HardwareVirtExLargePages enabled="true"/>
      </CPU>
      <Memory RAMSize="4096"/>
      <HID Pointing="USBTablet"/>
      <Boot>
        <Order position="1" device="HardDisk"/>
        <Order position="2" device="DVD"/>
        <Order position="3" device="None"/>
        <Order position="4" device="None"/>
      </Boot>
      <Display VRAMSize="32"/>
      <RemoteDisplay>
        <VRDEProperties>
          <Property name="TCP/Ports" value="3389"/>
        </VRDEProperties>
      </RemoteDisplay>
      <BIOS>
        <IOAPIC enabled="true"/>
      </BIOS>
      <USB>
        <Controllers>
          <Controller name="OHCI" type="OHCI"/>
          <Controller name="EHCI" type="EHCI"/>
        </Controllers>
      </USB>
      <Network>
        <Adapter slot="0" enabled="true" MACAddress="5CF9DD6F68B3" type="82540EM">
          <DisabledModes>
            <InternalNetwork name="intnet"/>
            <NATNetwork name="NatNetwork"/>
          </DisabledModes>
          <BridgedInterface name="Intel(R) 82579LM Gigabit Network Connection"/>
        </Adapter>
        <Adapter slot="1" type="82540EM"/>
        <Adapter slot="2" type="82540EM"/>
        <Adapter slot="3" type="82540EM"/>
        <Adapter slot="4" type="82540EM"/>
        <Adapter slot="5" type="82540EM"/>
        <Adapter slot="6" type="82540EM"/>
        <Adapter slot="7" type="82540EM"/>
      </Network>
      <LPT>
        <Port slot="1" enabled="false" IOBase="0x378" IRQ="7"/>
      </LPT>
      <AudioAdapter codec="AD1980" driver="DirectSound" enabled="true"/>
      <Clipboard mode="Bidirectional"/>
      <GuestProperties>
        <GuestProperty name="/VirtualBox/GuestAdd/HostVerLastChecked" value="5.1.10" timestamp="1480301962323274000" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Revision" value="112026" timestamp="1480302577518393902" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/Version" value="5.1.10" timestamp="1480302577518393900" flags=""/>
        <GuestProperty name="/VirtualBox/GuestAdd/VersionExt" value="5.1.10" timestamp="1480302577518393901" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/Net/Count" value="0" timestamp="1480302577519394002" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/OS/Product" value="Linux" timestamp="1480302577517893800" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/OS/Release" value="4.4.27-2-default" timestamp="1480302577517893801" flags=""/>
        <GuestProperty name="/VirtualBox/GuestInfo/OS/Version" value="#1 SMP Thu Nov 3 14:59:54 UTC 2016 (5c21e7c)" timestamp="1480302577517893802" flags=""/>
        <GuestProperty name="/VirtualBox/HostInfo/GUI/LanguageID" value="en_US" timestamp="1480302580901323400" flags=""/>
      </GuestProperties>
    </Hardware>
    <StorageControllers>
      <StorageController name="IDE" type="PIIX4" PortCount="2" useHostIOCache="true" Bootable="true">
        <AttachedDevice passthrough="false" type="DVD" hotpluggable="false" port="1" device="0"/>
      </StorageController>
      <StorageController name="SATA" type="AHCI" PortCount="1" useHostIOCache="true" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
        <AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
          <Image uuid="{139e68eb-9a8b-4e9f-8566-0d8ff0d14082}"/>
        </AttachedDevice>
      </StorageController>
    </StorageControllers>
  </Machine>
</VirtualBox>

The router is a NETGEAR genie. I haven’t been able to find more specific information on the model and am looking for a flashlight to help me.

At my former job (from 2010 to 2013), I ran all of our production servers with VirtualBox using this same network setup. They were all on the same subnet and could all see each other, as well as the Internet. The only difference was that all of them had ethernet connections.

The Windows host can ping .7 and .14 but not .9. I will disconnect the wireless in Windows and reboot once I have posted this and see what happens.

13

I have disabled the wireless adapter in Windows and rebooted. I have confirmed that I have no Internet access in Windows.

I started my virtual openSUSE machine and still have the same issue…
It can ping 192.168.1.14 but not 192.168.1.7

EDIT: I can no longer edit my previous post, but I thought of one more difference between my home setup and what I had done at work. I worked for a university and our all of our computers had fixed IP addresses (i.e. our building didn’t have DHCP). The local IPs that I have at home were all assigned by my router via DHCP.

14

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a0b3:1ec0:9380:4e8a%13
IPv4 Address. . . . . . . . . . . : 192.168.56.1

This is not the IP you are saying…
It is from another Subnet…

15

Try disabling your ethernet and use your wireless instead…
Scratch that… It looks like your wireless is still getting an IP address, it should be empty if you rebooted your machine with a disabled wireless. Something is wrong in what you did…

TSU

16

A “Host Only” network is the virtual network that is accessible only by Guests and the Host on the same machine, and not one that can communicate with other physical machines on the network… That might be configured but is not usable for the desired scenario…

TSU

17

As I posted before,
The last ipconfig you posted says you have a wireless IP address and there is no mention of your wired adapter.

That is totally inconsistent with disabling wireless while still leaving your wired connected.

Are you really posting your <entire> ipconfig?
It should include information on both your wired and wireless adapters, and it’s important to know what your Virtualbox adapter is bound to (ordinarily it should bind to any that’s available) so not seeing info about both adapters is incomplete and insufficient.

  1. Disable one of your network adapters
  2. Then, reboot
  3. Then do an ipconfig and post if you need help

If you do the above in a different order (like boot, and then disable an adapter) then things will be screwed up. The whole point of the reboot is to clear and re-build the network configuration.

TSU

18

As I posted before,
The last ipconfig you posted says you have a wireless IP address and there is no mention of your wired adapter.

That is totally inconsistent with disabling wireless while still leaving your wired connected.

I ran ipconfig before I disabled my wireless. I thought that’s what you wanted. Here are the results with wireless disabled:

Windows IP Configuration


Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::a0b3:1ec0:9380:4e8a%13
   IPv4 Address. . . . . . . . . . . : 192.168.56.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 

Tunnel adapter isatap.{E67D9EE3-4698-4604-BC49-7E5E66A1B1CC}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Are you really posting your <entire> ipconfig?
It should include information on both your wired and wireless adapters, and it’s important to know what your Virtualbox adapter is bound to (ordinarily it should bind to any that’s available) so not seeing info about both adapters is incomplete and insufficient.

Yes, my built-in ethernet doesn’t show up under ipconfig because I have unbound my network protocols from it. Here is an image http://tamusquash.com/WinNetworkSetup.jpg

This was necessary for the adapter to work correctly with my openSUSE virtual machine.

19

No need to remove protocols, just disable the network connection by one of the following
Wired - Just remove the physical cable from your machine
Wireless - Turn off the nardware network adapter. If on a laptop, there is generally a hardware switch or button. An alternative I haven’t used recently is to disable the adapter with a software switch like rfkill on openSUSE, or in Windows rt-click on the adapter and click “disable”

Your “ipconfig” should display your HostOS network configuration, which it doesn’t.
Something is not right…

So, for instance since you say you disabled your wireless your ipconfig should display something like the following for your wired connection

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : 
   Link-local IPv6 Address . . . . . : fe80::915d:117f:b173:6003%20
   IPv4 Address. . . . . . . . . . . : 192.168.1.8
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

And not the following (And if you don’t even see the following then something is wrong!)

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : workgroupname.net