Services

Since I've updated firmware to 1.3, my windows 7 laptop started logging these errors every hour:

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0xXXXXXXXXXXX.  The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

When I manually run "ipconfig /renew", I also get an error:

An error occurred while renewing interface Wireless Network Connection : unable to contact your DHCP server. Request has timed out.

What up with that?

Come on, anyone seeing this? My eventlogs are getting filled up..

Come on, anyone seeing this? My eventlogs are getting filled up..

Not on my windows 7 laptop, I just checked. If your eventlog is filling up, does it ever get an IP to get Internet access with?

The initial request succeeds, so the laptop gets an IP. Renewing it fails though (looks like monowall is ignoring the requests), and the laptop is just using the same address.. If I didn't check the event log I wouldn't notice that this was going on.

Do you use IPv6 in your network? This may just be warnings really, Win7 saying it can't get IPv6 address from the DHCP server.

Do you use IPv6 in your network? This may just be warnings really, Win7 saying it can't get IPv6 address from the DHCP server.

I've disabled IPv6 on the WiFi interface. Still there is the same problem:

Code:

C:\Windows\system32>ipconfig /renew WiFi

Windows IP Configuration

An error occurred while renewing interface WiFi : unable to contact your DHCP server. Request has timed out.

In the DHCP log of monowall, there is nothing logged about these attempts. To reiterate, the lease was obtained ok, but the renewal attempts fail. Anyone else seeing this?

can you check the raw dhcpd.log file ?

in /exec.php execute

cat /var/log/dhcpd.log

So, I started with "ipconfig /release".

The first time I ran "ipconfig /renew" - it was successful, and these were generated in /var/log/dhcpd.log:

Apr 29 00:25:09 mona dhcpd: DHCPDISCOVER from 00:23:12:1e:15:e5 via sis0
Apr 29 00:25:10 mona dhcpd: DHCPOFFER on 10.0.0.194 to 00:23:12:1e:15:e5 (valeriyo-mbp) via sis0
Apr 29 00:25:10 mona dhcpd: DHCPREQUEST for 10.0.0.194 (10.0.0.1) from 00:23:12:1e:15:e5 (valeriyo-mbp) via sis0
Apr 29 00:25:10 mona dhcpd: DHCPACK on 10.0.0.194 to 00:23:12:1e:15:e5 (valeriyo-mbp) via sis0
Apr 29 00:25:13 mona dhcpd: DHCPINFORM from 10.0.0.194 via sis0
Apr 29 00:25:13 mona dhcpd: DHCPACK to 10.0.0.194 (00:23:12:1e:15:e5) via sis0

Then I ran "ipconfig /renew" again - it failed with "unable to contact your DHCP server. Request has timed out.", and these were logged in /var/log/dhcpd.log:

Apr 29 00:26:18 mona dhcpd: DHCPINFORM from 10.0.0.194 via sis0
Apr 29 00:26:18 mona dhcpd: DHCPACK to 10.0.0.194 (00:23:12:1e:15:e5) via sis0

Somehow, my Windows 7 laptop never got this reply.. Does this info help?

P.S. I've upgraded to v1.32 and the problem still persists.

Finally, in 1.33 this issue appears to have been fixed. Thanks for fixing it, but at least admitting the bug would have been appreciated.

I don't see any fix put in place for this in 1.33, so one of the other changes must have fixed your issue.  Maybe the upgrade in ipfilter to 4.1.33.

I would have expected many reports of this type of problem, so I can only assume there is something different about your setup to the normal use case which is why we don't see others with this problem.

I am using m0n0 for a longer period of time on networks with many computers and different network scenarios and I haven't noticed such error at all. I think that something else caused it.