My OMV lose connection to the outside

    • OMV 1.0

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • My OMV lose connection to the outside

      Hi!

      I have a N54L microserver with two network cards (tp-link TG-3468 and integrated).

      Yesterday perform a clean installation OMV 1.0. When you configure DNS cards and I saw that lose connection with the outside occasionally. I try ping google.com and do not answer. Reboot the computer and it works, reboot again and again not working. I install a plugin and not download.
      I try to install backports and not working. Where is the problem? This problem is random...

      All this with the integrated network card

      Sorry, my english is very bad :P
    • I have the exact same problem. N54L, two network cards, one (integrtated) for LAN, and the other (usb) for the IPTV stream connected to my modem. OMV 0.5

      As pikinik says sometimes the connection on towards the internet doesn't work. LAN is fine. And it seems pretty random. I avoid using the web interface for the network config because I need some static routing rules for the iptv. Below is my /etc/network/interfaces

      Source Code

      1. # This file describes the network interfaces available on your system
      2. # and how to activate them. For more information, see interfaces(5).
      3. # The loopback network interface
      4. auto lo
      5. iface lo inet loopback
      6. # The primary network interface
      7. allow-hotplug eth0
      8. iface eth0 inet dhcp
      9. # IPTV interface
      10. allow-hotplug eth1
      11. iface eth1 inet dhcp
      12. pre-up ifconfig eth1 mtu 9000
      13. # Static route table
      14. up route add -net 10.0.0.0/8 gw 10.0.0.253 dev eth1
      15. up route add -net 224.0.0.0/4 dev eth1
      16. up route add -net default gw 192.168.0.1 dev eth0
      17. up route add -net 192.168.150.0/24 gw 10.0.0.253 dev eth1
      Display All


      output of ifconfig

      Source Code

      1. eth0 Link encap:Ethernet HWaddr 38:ea:a7:ff:0b:b8
      2. inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
      3. UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      4. RX packets:79376 errors:0 dropped:0 overruns:0 frame:0
      5. TX packets:315170 errors:0 dropped:0 overruns:0 carrier:0
      6. collisions:0 txqueuelen:1000
      7. RX bytes:20045392 (19.1 MiB) TX bytes:461944687 (440.5 MiB)
      8. Interrupt:18
      9. eth1 Link encap:Ethernet HWaddr 00:14:d1:b0:83:a4
      10. inet addr:10.0.0.219 Bcast:10.0.0.255 Mask:255.255.255.0
      11. UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
      12. RX packets:460792 errors:0 dropped:0 overruns:0 frame:0
      13. TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      14. collisions:0 txqueuelen:1000
      15. RX bytes:503507807 (480.1 MiB) TX bytes:382881 (373.9 KiB)
      16. lo Link encap:Local Loopback
      17. inet addr:127.0.0.1 Mask:255.0.0.0
      18. inet6 addr: ::1/128 Scope:Host
      19. UP LOOPBACK RUNNING MTU:16436 Metric:1
      20. RX packets:4781 errors:0 dropped:0 overruns:0 frame:0
      21. TX packets:4781 errors:0 dropped:0 overruns:0 carrier:0
      22. collisions:0 txqueuelen:0
      23. RX bytes:518424 (506.2 KiB) TX bytes:518424 (506.2 KiB)
      Display All


      Any ideas?

      The post was edited 1 time, last by ak0ska ().

    • ak0ska wrote:

      I have the exact same problem.


      ak0ska wrote:

      Any ideas?


      For starters, you have not the exact same problem. pikinik uses static while you use dhcp.

      Did you check if your DNS servers are configured correctly?

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hi David,

      Well let's just say then that the symptoms are pretty similar. :) Shall I rather open a new topic?

      On the OMV web interface primary and secondary dns server are 192.168.0.1 (router) and 8.8.8.8.

      If I check /etc/resolv.conf I see:

      Source Code

      1. root@openmediavault:~# cat /etc/resolv.conf
      2. # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
      3. # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
      4. nameserver 192.168.0.1


      Cheers,
      Akos
    • And there you got your problem. Because you set your interfaces manually (which you said a post before) you forget to set your nameservers which now are missing in the resolv.conf file.

      So add them to your interfaces section and they should be used in the resolv.conf file.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hi David,

      Thanks for the tip. The only manual configuration I did is the static routing rules in /etc/network/interfaces, otherwise they are configured using dhcp. However I added

      Source Code

      1. interface "eth0" {
      2. prepend domain-name-servers 8.8.8.8;
      3. }

      to /etc/dhcp/dhclient.conf

      After rebooting, the /etc/resolv.conf looks like this:

      Source Code

      1. root@openmediavault:~# cat /etc/resolv.conf
      2. # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
      3. # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
      4. nameserver 8.8.8.8
      5. nameserver 192.168.0.1
      6. nameserver 10.66.255.245


      Don't know where the 10.66.255.245 came from. It still has no internet though.

      Source Code

      1. root@openmediavault:~# ping google.com
      2. PING google.com (173.194.45.35) 56(84) bytes of data.
      3. ^C
      4. --- google.com ping statistics ---
      5. 10 packets transmitted, 0 received, 100% packet loss, time 9071ms


      And alsoI cannot even ping 8.8.8.8 from OMV, but I can from my desktop. If this was a DNS issue, shouldn't I be able to ping based on IP?
    • Check your default gateway, seems like its not the right one.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Source Code

      1. root@openmediavault:~# route -n
      2. Kernel IP routing table
      3. Destination Gateway Genmask Flags Metric Ref Use Iface
      4. 0.0.0.0 10.0.0.253 0.0.0.0 UG 0 0 0 eth1
      5. 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
      6. 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
      7. 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0


      Source Code

      1. root@openmediavault:~# ip route
      2. default via 10.0.0.253 dev eth1
      3. default via 192.168.0.1 dev eth0
      4. 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.20
      5. 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.101


      The strange thing is I brought back the server from hibernate tonight and the "nameserver 10.66.255.245" entry is gone from /etc/resolv.conf.
      Right now I can ping google.com with the above routing rules.
      Could it be that the OS is randomly using either of the gateways?