Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Good evening all,

Strange situation: I work from a local development machine running apache and lighttpd in tandem. Today I tried to install curl-php5 which stated that the repository is unreachable. After further analysis it seems to me that debian cannot connect to the internet ( outside the network ) for some reason. I do not possess the necessary knowledge to debug this issue any further and have run out of URL's with bash snippets to try. I therefore kindly request your assistance in this matter.

dmesg | grep egiga0
egiga0: mac address changed
egiga0: link down
egiga0: started
egiga0: link up, full duplex, speed 1 Gbps

The network is routed through a switch that connects several computers and the devbox to the modem where the devbox is assiged statically.

The interface egiga0 has the following properties:

ifconfig -a
egiga0    Link encap:Ethernet  HWaddr 14:d6:4d:a6:97:76
          inet addr:  Bcast:  Mask:
          RX packets:7275 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12545 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:646188 (631.0 KiB)  TX bytes:14662888 (13.9 MiB)

As per your request, the output of nano /etc/resolv.conf:


and the output of ip route show: dev egiga0  proto kernel  scope link  src dev egiga0  scope link
default via dev egiga0

The machine itself is a d-link sharecenter running the ffp ( fun plug ) debian squeeze. All servers running on it are accessible from the local network as one should expect, however every external command like wget, or ping result in an unresolvable hostname from which I deduce that the internet itself cannot be accessed.

I'll be happy to provide any information requested in order to solve the problem. Input anyone?

share|improve this question
Could you add the content of /etc/resolv.conf file and the output of ip route show to your question? – Mircea Vutcovici Apr 11 '13 at 21:26
I will update it. Thanks for responding. – Digitalis Apr 11 '13 at 21:34
Add the output of ping -c 3, of host and of host – Mircea Vutcovici Apr 11 '13 at 21:45
Host is an unrecognized command, the first one works as expected. – Digitalis Apr 11 '13 at 21:52
You can use nslookup instead of host. – Mircea Vutcovici Apr 11 '13 at 21:58

You need to find out where the problem is - if it is on the box or in the network. Try pinging your default gateway for starters.

In your configuration: that will most likely be Therefore: ping

If that responds, most likely the router does not route your traffic. Also, check for iptables rules with iptables -L -n to ensure that no rules are blocking traffic.

If you can ping the default gateway - try pinging something on the outside based on IP and not on hostname, e.g. Google nameserver: ping - does it respond? If it responds, well then DNS is probably the culprit. You would fix that by editing /etc/resolv.conf and inserting functioning nameservers (e.g. and which are Google nameservers)

share|improve this answer
Ok, is indeed the gateway, and that returns pings – Digitalis Apr 11 '13 at 21:40
Also, works, albeit a little bit slower. – Digitalis Apr 11 '13 at 21:41
I think the local DNS service on the router is down. – Mircea Vutcovici Apr 11 '13 at 21:46
Any way to test for that? – Digitalis Apr 11 '13 at 21:48
@Frands Hansen, Interestingly enough, iptables cannot initialize due to the table filter being non-existent. – Digitalis Apr 11 '13 at 21:57

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.