This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Curious DHCP behavior

I'm moving a machine from one network to another and finding that the Astaro DHCP server sees that the machine is in different networks but it assigns it the same ip address no matter what network it's in. This is not helpful.

[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPOFFER on 10.1.10.1 to 00:0c:29:bf:76:b7 (aardvark) via eth0 [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPOFFER on 172.16.1.10 to 00:0c:29:bf:76:b7 (aardvark) via eth3 [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPOFFER on 10.3.10.1 to 00:0c:29:bf:76:b7 (aardvark) via eth2 [/FONT]
[FONT=monospace]2013:10:11-16:53:13  wahine dhcpd: if aardvark.ravennasprings.com IN A rrset doesn't exist  add aardvark.ravennasprings.com 43200 IN A 10.1.10.1: timed out. [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPREQUEST for 10.1.10.1 (10.1.1.2) from 00:0c:29:bf:76:b7 (aardvark) via eth0 [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPACK on 10.1.10.1 to 00:0c:29:bf:76:b7 (aardvark) via eth0 [/FONT]
[FONT=monospace]2013:10:11-16:53:13  wahine dhcpd: DHCPREQUEST for 10.1.10.1 (10.1.1.2) from  00:0c:29:bf:76:b7 (aardvark) via eth3: wrong network. [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPNAK on 10.1.10.1 to 00:0c:29:bf:76:b7 via eth3 [/FONT]
[FONT=monospace]2013:10:11-16:53:13  wahine dhcpd: DHCPREQUEST for 10.1.10.1 (10.1.1.2) from  00:0c:29:bf:76:b7 (aardvark) via eth2: wrong network. [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPNAK on 10.1.10.1 to 00:0c:29:bf:76:b7 via eth2 [/FONT]
[FONT=monospace]2013:10:11-16:53:13  wahine dhcpd: DHCPREQUEST for 10.1.10.1 (10.1.1.2) from  00:0c:29:bf:76:b7 (aardvark) via eth4: wrong network. [/FONT]
[FONT=monospace]2013:10:11-16:53:13 wahine dhcpd: DHCPNAK on 10.1.10.1 to 00:0c:29:bf:76:b7 via eth4 [/FONT]

Can anyone think of a solution. I don't want to manually change network addresses [that's what DHCP is for] and I'd rather not generate static entries for all my machines that travel.

Thoughts?

Thanks.

This thread was automatically locked due to age.

Parents

0 derrickoltmann over 11 years ago
Not trying to hijack your thread, but I am having a somewhat similar issue.

Sophos is running on a very simple ESXi VM at home, I have a single notebook that can not get on the correct subnet when it resumes from sleep.
This same notebook has some serious connection throughput issues as well. I'd say it's this computer, however it did not have these issues before I put the Sophos UTM in place.

2013:11:02-02:30:25 redrocker dhcpd: DHCPDISCOVER from 2c[:D]0:5a:79:1b:75 (hp-ENVY_m6) via eth0
2013:11:02-02:30:25 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 (192.168.17.1) from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:30:25 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0
2013:11:02-02:30:26 redrocker dhcpd: DHCPOFFER on 192.168.2.176 to 2c[:D]0:5a:79:1b:75 (hp-ENVY_m6) via eth0
2013:11:02-02:31:12 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:31:12 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0
2013:11:02-02:31:26 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:31:26 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0
2013:11:02-02:31:31 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:31:31 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0

It should be getting x.x.2.100+.
The only way to fix it is to fully reboot the machine, on a fresh start it's fine, but if it's put to sleep it resumes with this problem.

I just updated Sophos to 9.004-33 earlier today, but the throughput issue and I believe this issue was present beforehand. Going to restore the pre-update snapshot and check.

EDIT: No longer corrects itself on reboot. Not really sure what could be going on, as that subnet is not one which is assigned or issued anywhere in my UTM.
Creating a static mapping does not correct the issue either. I feel strongly that this is an issue with this particular instance of Win 8, but not sure why it would have been working fine before Sophos went in place.
If I assign the IPv4 info on the machine itself, all works fine (except it's still very slow).

EDIT: It's definitely Sophos, as it has started handing this same address to android phones as well.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 derrickoltmann over 11 years ago
Not trying to hijack your thread, but I am having a somewhat similar issue.

Sophos is running on a very simple ESXi VM at home, I have a single notebook that can not get on the correct subnet when it resumes from sleep.
This same notebook has some serious connection throughput issues as well. I'd say it's this computer, however it did not have these issues before I put the Sophos UTM in place.

2013:11:02-02:30:25 redrocker dhcpd: DHCPDISCOVER from 2c[:D]0:5a:79:1b:75 (hp-ENVY_m6) via eth0
2013:11:02-02:30:25 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 (192.168.17.1) from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:30:25 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0
2013:11:02-02:30:26 redrocker dhcpd: DHCPOFFER on 192.168.2.176 to 2c[:D]0:5a:79:1b:75 (hp-ENVY_m6) via eth0
2013:11:02-02:31:12 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:31:12 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0
2013:11:02-02:31:26 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:31:26 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0
2013:11:02-02:31:31 redrocker dhcpd: DHCPREQUEST for 192.168.17.7 from 2c[:D]0:5a:79:1b:75 via eth0: wrong network.
2013:11:02-02:31:31 redrocker dhcpd: DHCPNAK on 192.168.17.7 to 2c[:D]0:5a:79:1b:75 via eth0

It should be getting x.x.2.100+.
The only way to fix it is to fully reboot the machine, on a fresh start it's fine, but if it's put to sleep it resumes with this problem.

I just updated Sophos to 9.004-33 earlier today, but the throughput issue and I believe this issue was present beforehand. Going to restore the pre-update snapshot and check.

EDIT: No longer corrects itself on reboot. Not really sure what could be going on, as that subnet is not one which is assigned or issued anywhere in my UTM.
Creating a static mapping does not correct the issue either. I feel strongly that this is an issue with this particular instance of Win 8, but not sure why it would have been working fine before Sophos went in place.
If I assign the IPv4 info on the machine itself, all works fine (except it's still very slow).

EDIT: It's definitely Sophos, as it has started handing this same address to android phones as well.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data