Debian :: No Internet Access \ Ping Always Respond With Network Is Unreachable?
Jan 29, 2011
I'm using debian lenny.When I boot with kernel 2.6.36, ping always respond with Network is Unreachable. But when I boot with kernel 2.6.26 it works. I can't even ping the dafault router of 2.6.26 kernel when I am at 2.6.36. Also, system/administration/network does not show any connections while it shows something at the other kernel.
I cannot access/ping my Debian server. I know the IP is right (ifconfig, route and ip addr) all gave me 10.0.2.25 (route gave me 10.0.2.0).I cannot ping it from any computer in my netwerk, even when I try to ping it from my Debian itself, it gives me Destination Host Unreachable !(Wierdly, I can ping 10.0.2.2 tho).I am using virtualbox when the netwerk options 'NAT' turned on. When I look at my /etc/network/interfaces/ the last line looks like:iface eth0 inet dhcpShouldn't their be some other stuff listed?
I installed openSUSE on one of my work system. The network port wasn't working when I was installing, but works fine now (checked in Windows). But for some reason, I am not able to configure the network. I used both Dynamic and Static IPs (both work fine in Windows) but still no go. I am using Yast Control Center for this purpose. I can't even ping the default gateway when I am using custom settings. When I use dynamic settings, it says Unreachable Network.
I have two linux servers, I tried to ping from one linux box to another and vice versa but error message is "connect: Network is unreachable" Where as If I tried from windows machine I am getting the reply from both the servers. C:Documents and Settings>ping bnkprod
Pinging bnkprod.softtech.com [172.20.40.141] with 32 bytes of data: Reply from 172.20.40.141: bytes=32 time=16ms TTL=64 Reply from 172.20.40.141: bytes=32 time<1ms TTL=64 Reply from 172.20.40.141: bytes=32 time<1ms TTL=64 Reply from 172.20.40.141: bytes=32 time<1ms TTL=64
Ping statistics for 172.20.40.141: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 16ms, Average = 4ms
I installed Fedora 10 and are using KDE. I struggled to get my network up and running - error for ping was "network is unreachable". I eventually got it right by modifying my ifcfg-eth0 file manually.
Now I'm trying to install with yum, but yum fails to connect, probably because of the proxy. I've set the proxy in <System Settings><Network Settings><Proxy> but it doesn't allow me to also add the authorization - greyed out. I've chosen the manual configuration of proxy.
1. How can I enable or allow the adding of authorization in the proxy dialogs or
2. Where is the proxy file which I can modify from command line (and how)?
I installed centos 5.3 x86 at vrtualbox on windows 7 x64 as host. The ping answers "network is unreachable", ifconfig has an ip "192,168,51,100". At control panel, I seleted intel PRO/1000MT Desktop Host only. Is this centos's problem?
Firewall disabled.Static IP addys given to each laptop, but makes no diff when dhcp derived IP addys.using wlan Cannot ping either laptop from a windows box, bit windows box pings other computers.Can access internet from either laptop and Samba works too.I can ping one laptop if I plug the LAN wire into it. In fact I can ping either the wlan IP addy or the LAN addy this way. WHen I remove the Lan wire I can still ping the wlan on the laptop, but restarting screws it all up again.I see that iptables and other files change when I plug the LAN cvable in and then remove it again.
I have a Compaq Presario R3000 with Ubuntu 9.10 32 bit that I just installed last night. I'm using a Zyxel G-102 Wireless card and Actiontec GT701WG wireless modem.
When I try to connect to the 'net, the network does show up and it connects strong (100%). It also shows multiple neighbors networks. It pings at 99% success (with over 900 sent as I write this) but when I open Firefox it can't connect, it just times out. I've used WEP security and have switched off security as well. I tried hooking up to the modem via USB and get the same result. It acts like a Firewall issue but there isn't one installed - at least that I can find and the Firewall in the modem is off. I ran FF in root with gksu firefox as suggested in another thread. I tried www.ubuntu.com and the header loaded but that was all. Then it timed out.
I'm new to Linux but have used Puppy Linux with this machine and card, etc. so I know it can/does work with Linux. I wanted a more refined distro and chose Ubuntu.
I just downloaded and installed the latest Cent OS 5. I disabled SE linux, turned off the firewall, and selected the Server package options when installing. I plan on using this as a router/firewall between my internal network and the internet, as well as web server, etc. The first thing I did was to configure the two NICs, internal one with 192.168.7.1 address and the other with an address from my ISP (I have a static address, but I also tried to let the DSL router assign an address via DHCP). Everything looked fine, I checked /etc/resolv.conf and my routes. I was able to ping the DSL router from the server, but I was not able to do a ping or lookup on anything outside my network. I tried host, dig, nslookup, etc, no luck. Obviously then, I was not able to browse the net with firefox.
I have a Centos 5 server working as firewall, dns, proxy (squid) and mail server with postfix. sometimes it blocks ping from the net and when it hapen I cant browse my site not even fetch my email through webmail from outside. But inside every thing still go well even browsing the internet, but no ping to the net (e.g pop.gmail.com). when I restart it everything come up and work fine.
I have installed debian to run Squid cache as a caching proxy. Ive been bashing away now for 2 days and i have managed to install squid (i first tried manually, but that did not work so i used synaptic software packager to install it (from Administration menu) That went well, thereafter i installed webamin to work with squid in a GUI
I have managed to start squid and added my range of IP addresses to the ACL list I have added the proxy restriction too.
Now, i tried to test it. I opened Iceweasel Web browser (on the same machine) and setit to use the Proxy server: localhost and port:3128 That works fine.
But when i try to change the proxy setting to my machines ip (where squid is installed) : Proxy server: 10.0.0.35 and port:3128 That does not work. Am i missing something, please help I then tried to set another windows PC on the network to: Proxy server: 10.0.0.35 and port:3128 That also does not work.
I also edited the conf file to http_access allow all, but i do not know if i have doen it correctly, but maybe there is another problem?
I have a server with centos 5 and plesk 9 and I have buy an additional IP address for my server, when i create it in plesk, there is no problem, all its ok I can assign it to a new domain, but the ip only responds ping, none of other services as http, ssh or smtp.I paste here the configuration of files
I have a problem on my LAN, then: I have a laptop on which Windows Vista is installed, and every time I try to do ping to my server centos, my centos server does not respond to ping. The server is operating normally, because I found other PCs on my network that communicate normally with my centos server.
we are trying to install this NIC Rosewill RC-400 Chipset RTL8169S-32 in Ubuntu 9.04 we downloaded the drivers from Rosewill website (For kernel 2.4.x and 2.6.x V 3.1) but when we follow the instruction in the readme file and do make clean modules and error comes out
So I went do realteak downloaded latest available drivers that seems to be were release yesterday did same command and same error So I made only make and it went fine did then make clean modules and went fine so made make install, depmod -a and modprobe r8169 verify int was up and getting correct ip from router but I'm not able to access the internet or ping any IP address
Code: xxx@xxx-desktop:~$ uname -a Linux xxx-desktop 2.6.28-18-generic #60-Ubuntu SMP Fri Mar 12 04:40:52 UTC 2010 i686 GNU/Linux xxx@xxx-desktop:~$
I recently setup a new Linux server running Fedora 10. For some reason all ping response times are rounded to the nearest 10ms. For example, running the simple command "ping yahoo.com" give the following sample results:
64 bytes from ir1.fp.vip.re1.yahoo.com (126.96.36.199): icmp_seq=12 ttl=57 time=60.0 ms 64 bytes from ir1.fp.vip.re1.yahoo.com (188.8.131.52): icmp_seq=13 ttl=56 time=50.0 ms 64 bytes from ir1.fp.vip.re1.yahoo.com (184.108.40.206): icmp_seq=14 ttl=56 time=40.0 ms 64 bytes from ir1.fp.vip.re1.yahoo.com (220.127.116.11): icmp_seq=15 ttl=56 time=50.0 ms
I could post a larger result set but its all the same... every response is rounded to a multiple of 10ms. This wouldn't be a big deal except that the server is running Nagios for monitoring so accurate stats are important. The Nagios check_ping and check_icmp commands are also returning rounded off results. How can I get ping to simply respond with the actual response times rather than a rounded off number?
I posted this already in the absolute beginner section, but no answer was found, so I thought I might try this place..Long story as short as possible:
- I installed Ubuntu 9.10 for a friend who was fed up with WinXP crashing all the time
- After the install, networks was broken. I could ping sites outside the LAN, could connect to the router via firefox, but NO application could access the web. - The router works just fine, I tried with my own notebook.
- Disabling ipv6 in grub (edit /etc/default/grub and 'sudo update-grub') seemed to solve the problem.
- Then update the standard packages + install restricted extras and boom, Network gone: No ping to sites outside the LAN, no nothing. Still can connect fine to the router and even the remote desktop connection works, connecting over the internet. But that's it.
I have tried setting the mpu to a value recommended by my isp, I have set static ip and dns, I really don't now what to try any more.
I have my router (192.168.1.1) connected to the internet. I have installed Debian on a server with Bind9 (192.168.1.254). The configurations files are: Code: $ cat /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback
# The primary network interface auto eth0 iface eth0 inet static address 192.168.1.254 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 Code: $ cat /etc/bind/named.conf include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones"; .....
I installed 11.3amd64 as a VM under Vista/VMWare Player - all worked fine. I have now installed it as a physical system. It nstalled cleanly BUT during first boot it could not access the repos. With each repo it gave the message
- download (curl) error for (repo) - error code connection failed - error message could not resolve host (repo)
This was followed by a message box containing
- UI syntax error - no widget with ID 'contents
Firefox could not access the internet (cannot find server) until I disabled IPV6 (I used about:config), now it works fine. I think the repos problem is because of IPV6 - I usually have trouble with IPV6. I tried disabling IPV6 with the following (How To Disable ipv6 on SuSE Linux | Linux Poison)
I've been using Debian for about 6-7 months now. I've had a bit of a major networking problem for the past 4 months or so that I've been trying to fix - specifically, it started when I upgraded to Jessie. I can connect to wifi just fine, and sometimes I can even use the internet for brief periods of time (exceedingly rarely). Then... nothing. No network access, period. I can't ping any outside servers, I can't ping other computers on my network, and I can't even ping my router. Pages I try to load just stay "connecting" for all eternity, network printing fails, and so on.
So after four months of searching online (I've read through way more wireless documentation than I care to say), I finally gave up and admitted that maybe I screwed something up during upgrade to Jessie (as a matter of fact, I did, I had to do the upgrade in two increments [somehow] because my root partition was too tiny by mistake) and I did a clean install. Since I had /home on a separate partition, I was able to keep all my user files, but all settings regarding networking were wiped. So after installing firmware-iwlwifi so I can use my wireless card, I tried connecting to wireless! Success! Then I tried connecting to the internet... success! Briefly. The next morning I tried using the internet again, and it failed in exactly the same pattern as before.
I don't know much about what's going on here, but here's what I do have available:
I do have to use firmware-iwlwifi, which I installed by doing apt-get install firmware-iwlwifi. I don't think it's an issue with the wireless card itself (hardware-wise), the laptop dual-boots Windows 7 (that I never use anymore), and Windows 7 is able to connect to the internet just fine. Connecting directly to my router by ethernet cable works fine, I have perfect internet/network access then.
I can confirm that my laptop is receiving an IP address and that it is using ARP correctly to get the MAC address of my router (I confirmed this by doing the arp command, it has the MAC address correct, I checked from another computer with my router's config page) All other computers on my network work perfectly with my router. To confirm the router/its configuration isn't at fault, I did a full factory reset of the router, but to no avail.
Out of curiosity I tried installing Wireshark (using an ethernet cable to download it) to monitor what happens when I try to access a webpage. I'm no expert on networking, but I noticed something out place when I compare a capture from the affected computer to a capture from one operating normally - there are a lot of STP packets showing up. I did some checking around, it looks like STP is involved in bridging and more complex networking setups (involving switches, for example)... but it shouldn't be found on a home network, especially where there's no bridging whatsoever. These STP packets don't show up on packet captures done from any other computer. I've attached a packet capture from the affected computer here, since the forums won't let me attach a .pcapng file.
Here's the output from a few commands I ran during past troubleshooting sessions:
Both systems connected in same LAN based network . Both WAN live ips are connected through different modems. Problem is that , no system is able to ping or connect with other system with Live ip , though they are able to connect through LAN ip and both systes are accessable and also able to browse internet (google etc..) Ping error :-- Destination Host Unreachable.
I have a desktop computer running OpenSUSE 11.2 with two network cards installed. I would like to use both cards for connecting to the internet using different networks. The setting would be the following: eth0 is the main (default) card, almost all programs should use this NIC for connecting to the internet. eth1 is used only by a few programs, which have setting for selecting which network interface to use. The two NIC's are connected to different networks, so the IP address of the NIC's, the related subnet masks and gateways are also different.
Saying short, I would like to have the two NIC's as they would be in two separate computers. I can set the IP address and subnet mask of the NIC's. The main problem is that I can only declare one gateway. How can i setup this? I do not use network manager, I configure network cards using yast, but if needed I can of course use ifconfig directly.
I'm having a strange problem with my network connection/DNS. I turn computer the on and it recognizes and connects to wireless or wired but I can't access any Internet resources or my router. If I ping the default gateway, I get no response and I get DNS errors from any network services that run at start up. If I stop and start the network daemon then it all works fine until the next time I turn on my laptop. It does this for both wireless and wired connection.
I've tried to edit the network interface information in YaST but it says that configuration is handled by knetworkmanager and I have no idea where that information is accessed. I should point out that it all worked fine until I tried to connect to open WAP at my school and couldn't so I connected to the wired network. Next morning I had this problem when connecting to my home network. My questions are 1. What could be the cause of this error and 2. where does one configure the network interfaces when using knetworkmanager
setup my static network connection Here are my details :
IP : 172.16.152.137 Subnet : 255.255.255.192 Gateway : 172.16.152.191 Primary DNS : 172.16.0.1
but after this setup when i restart my network #service network restart while bringing up the eth0 the following message is displayed before [OK] - RTNETLINK answers : Invalid Argument now it seems either this setup is wrong or not sufficient to set up the connection, whenever i try to ping 172.16.0.1 it showing connect : Network is Unreachable
I have set up a MythBox on Debian Lenny. I have a wireless connection using a Belkin USB WiFi Device. I am using ndiswrapper, wpa_supplicant, etc. I am using a static ip address. I have internet access without problems. However, if I try to ssh in or even ping my mythbox inside my network there is no connection. I have never had to do anything special to ssh into debian in my network before. I am confused that I have an internet connection but can't get a ping reply.
I dont even know where to start looking on Google.Just in case this matters, for completeness.I've an inactive eth0 (wired ethernet link) with static IP.Other possibly relevant details:I'm using an old 802.11b card. Cant imagine this is relevant, because the internet is working fine as far as pinging anything outside the local network goes.
This applies to my 2 opensuse PC's, my Windows PC is fine.I can ping a hostname, say "PC1" but I can not ping PC1.domain.local (even the host PC can not ping it's own FQDN). When I ping just the hostname the ping stats even list the FQDN.Onto the next issue, since all my PC's, have the domain prefix domain.local, my Synology can not. I can ping it's IP and that is it. I can resolve it's name with nmblookup just fine tho and that is what is killing me. How is this not resolving.Even weirder, I can browse to "Synology" in Network Servers under places on the slab.
I have an ubuntu kk laptop connected via wireless to my mixed network (xp, win7, other ubuntu), but i can not ping said machine or connect via ssh. Internet and smb-browsing ON this machine work, as does pinging FROM it. If this was a windows machine, I'd say a firewall is in the way, but since it's a vanilla karmic install, this should not be the case (or should it?).
I would like to ask something. Today my network Internet access suddenly slowed down, after inspecting the problem the hard way we disconnected one of our servers(ip=190, debian squeeze) from network and the network was alright again. When we plugged it back in, following symptoms were observed: computer 190 pinged gateway app. each 6th time. gateway(debian lenny) pinged computer 190 app each 6th time whole network Internet access was slowed down, local network functioned just fine
While pinging themselves, i ran iptraf on icmp packets on gateway and I saw what i thought was ping attack, lots of echo request coming from external address to computer 190. Blocking that address in iptables didn't help but restarting the gateway did, network Internet conenction is at full speed and gateway and computer 190 ping just fine.
My question is, what steps should I undertake in similar case (it's second time in 2 months) - to debug similar problems. Is it even possible for ping DOS to this kind of damage?