Search:

Sorry for delay. I, in fact, was curious and checked driver source code at:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.31.y.git;a=blob;f=drivers/net/tulip/dmfe.c
to see if there are...

Could you also post output of:
lspci -nn

so we would know which exactly Davicom card we are talking about...

Looks that driver is not working properly (Tx timeout errors).
Maybe try forcing link settings:
sudo rmmod dmfe
sudo modprobe dmfe mode=5 # if under windows connection is 100Mb/s
sudo modprobe...

Let's try again with tcpdump to check if any packets are sent/received, this time also turn on driver debugging:

Run from terminal:
# Stop avahi/zeroconf to disable spamming network activity:...

To check if packets are received, run from terminal:
sudo tcpdump -ni eth0
and click on "Auto eth0" in NetworkManager to try to get connection.

But I suspect there won't be any replies because...

Most linux problems with suspend/hibernate come from dodgy video drivers.
I won't help you with this problem - I don't know how to diagnose those problems. You can try your luck with passing "quirk"...

Create config file in /etc/pm/config.d with SUSPEND_MODULES="via-rhine" line, i.e.

sudo sh -c 'echo SUSPEND_MODULES=\"via-rhine\" >> /etc/pm/config.d/01fix_resume_net_failure'


Ok, this is...

Looks like this option doesn't work in your case - after resume no DHCP packets are received...

My last idea:
Reboot to get working network, prepare to suspend - remove via-rhine driver:

sudo...

Check /var/log/daemon.log for dhcp server logs, there are entries like:

Nov 1 09:45:44 myserver dhcpd: DHCPDISCOVER from 00:00:00:00:00:01 via eth0
Nov 1 09:45:44 myserver dhcpd: DHCPOFFER on...

Log shows that network card tries to send packets, but doesn't seem to receive any.

This could be similar problem to:
http://ubuntuforums.org/archive/index.php/t-186430.html

Quick test -...

Yes, file could have been empty - this means no ubuntu specific kernel hacks were present, no problem. Simply add mentioned kernel module option.




Sorry for this, I made mistake, should be:...

Of course there is simplier solution: use iptables DNAT.


iptables -t nat -D OUTPUT -d remote_dns_ip -p udp --dport 53 -j DNAT --to remote_dns_ip:5353

OR, you can add so called "port forwarding" on router WRT54G, you can set it that incoming connections on port 80 will be forwarded to your laptop...

You can check manually each step:
Can iptables rule with "MARK" target be added?

sudo iptables -t mangle -A PREROUTING -i test -j MARK --set-mark 0x1
sudo iptables -t mangle -D PREROUTING -i...

Let's see what do you mean by "My internet... now it can be downright unbearable."

What is output of terminal commands:

time dig www.ubuntu.com

time ping -c5 www.google.com

time ping -c5...

Important question: what do you mean by "a little home server"?
What service will it provide? I ask this, because you mentioned DD-WRT, which by itself can act as a router, dns and dhcp server...

I have something like this configured on my Debian Lenny system:
snipped from smb.conf:


security = share
[homes]
read only = no
valid users = %S
[shared]
path = /home/shared

Because you use NetworkManager, remove lines:

auto eth0
iface eth0 inet dhcp
form /etc/network/interfaces

Reboot and check if internet connection works.

Of not, paste here log of...

From your log it looks that after resume your network card does not work (does not seem to receive packets).
Earlier in log there is information about network driver (NetworkManager: <info> (eth0):...

This is most important information. I suspect other name resolution "helpers" are taking very long time and only after timeout classic dns is tried.

You said you have


hosts: files...

Hmm, log is very short. Network manager ignores eth0 device (probably manually configured in /etc/network/interfaces), and log does not tell why eth1 does not start configuration.

Try waiting a...

I wanted to know if there are any differences from default configuration.

Now, try to suspend, and after resume run from terminal:

grep -A9999 'Waking up' < /var/log/daemon.log | tee wakeup.txt...

Important question:
Have you installed 9.10 from scratch or you upgraded 9.04 with "altered/amended various config files"?

What is output of:

dig PEER_HOSTNAME

Specifically, which server is used? SERVER line, third from bottom.

I use 8.04 kubuntu, but I got 9.10 installer to try newer network manager. I have one idea:

When you right click on Network Manager applet and select "Edit connections"
you probably have: Wired...