Feisty networking stops working after a couple of hours (sometimes minutes)

[Fredrik]

After some hours (or sometime minutes) my network connection stops working (totally)

I use DHCP on eth1 towards Internet and static on eth0 towards LAN and a router that connects to internet too if this tow interface-stuff is an issue.

Doing

sudo /etc/init.d/networking restart

renew my ip and everything starts working again.

Saw some notice about utc = no / yes. I have it set to no as I also run a game OS (Windows).

My routing table if this is an issue:

f@air:~$ route
Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.253.0 * 255.255.255.0 U 0 0 0 vmnet1
192.168.91.0 * 255.255.255.0 U 0 0 0 vmnet8
80.217.80.0 * 255.255.254.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth0
default VT-DOC-6-Cable5 0.0.0.0 UG 0 0 0 eth1

[Fredrik (fredrk)]

it seems to happen every other hour. Then lease is renewed?

[Fredrik (fredrk)]

This is getting RELLAY annoying!

It's not even 24 minutes since last time...

[Fredrik (fredrk)]

This is a HUGE issue.

No comment at all?

Remove that none working dhcp3-client if it can't work in the most basic way with UTC = no

[Tormod Volden (tormodvolden)]

Maybe you should try answering to the questions we ask you in bug #33968?
I don't think your set-up sounds like "the most basic way". Please note that dhcp3-client works for most people, including those with UTC=no.

[Fredrik (fredrk)]

It seems like it fail if UTC=no and you are in a timezone > UTC + 2 (Like sweden now in the summer).

[Tormod Volden (tormodvolden)]

It works well for most people in UTC+2 as well. I think there's a problem if your lease time is shorter than your timezone offset, but I can not get it confirmed if people don't provide the information.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.