Windows 10: why is dhcp server pushing the link local address for the gateway...but gives the correct...

Trying to setup an IPV6 standalone environment. why is dhcp server pushing the link local address for the gateway...but gives the correct IP for the regular IP

:)

 

Rogue DHCP Server is running in a VM

The whole of 192.168.x.x is a Private address range available for your router to use. You have the whole of 192.168.0.x assigned to the DHCP pool, but the DHCP server on your router will use a fixed IP address outside this range.

What is the IP address of your router for web admin? Or the IP address of the default gateway? On my router they are the same as the DHCP server address.

 

Rogue DHCP Server is running in a VM

My router- gateway address is 192.168.0.1

- - - Updated - - -

Just to explain how I know that this is a rogue DHCP Server, This is the result I receive after typing the Ipconfig commend:-

C:\Users\BSAdmin\Desktop>ipconfig /all | find /i "DHCP Server" DHCP Server . . . . . . . . . . . : 192.168.58.254

As you can see this address is not part of my subnet.

 

DHCP with redundant Gateway does not work

I am having trouble connecting to my office network using Wifi.

I have done some investigation and found the problem which is...

When DHCP server serves the request and replies with multiple/redundant gateways, the device does take the IP and communicates within the local network but ignores the gateway and is not able to connect the outside network.

When I requested my Systems Administrator and he added specific setting for my device's MAC address and sent only one gateway in DHCP reply, device starts to connect outside.

Our office has other debian based and CentOS based systems running including Ubuntu workstations but none of them is having problem with multiple/redundant gateways but only N900 is having this problem. It means that the problem is not inherited from Linux
or Debian but the bug is related to Maemo itself.



I have tried to tell add some technical details and do not expect answers like to check firewall and so. This is a genuine problem and is not intermittent. We have experienced it using MS DHCP server under windows 2003 and win 2k as well.



End users: Please try to duplicate the problem before suggesting a work around or anything



Developers/Admins/Officials: I hope you acknowledge the problem soon.