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

Using static address with DHCP server

Hi,

Keil Ethernet stack

I have trouble using static address when If I cannot find DHCP Server.
I enable Dynamic Host Configuration in Net_Config_ETH_0.h
I also specified my static ip address==192.168.0.100 and static Default Gateway =192.168.0.1.
Primary DNS Gateway =192.168.0.1.

I am connecting directly my Embedded device ethernet to PC.
My PC has static IP address = 192.168.0.1

If I disable Dynamic Host Configuration in Net_Config_ETH_0.h then it all works.

I thought If it cannot find DHCP server it will fallback back to using static DNS server which is my PC.

Kindly suggest what is wrong with my configuration. Does Keil Ethernet stack supports fallback?

Thanks,
Naeem

Parents
  • Why do you - in this thread - post a link pointing back to this very thread?

    M$ has documentation how to use APIPA for Windows 7. All you need to do is to say that the primary setting should have an IP automatically assigned. Then as alternative configuration you keep the default APIPA setting checked. 30 seconds with Google...

    But it is only relevant if you want to create a local island of non-connected machines. So friend A and friend B can connect their two computers together without any DHCP server.

    So it might be practical in a tent out in the wilderness. But most people have an existing network with at least a dirt-cheap router - and suddenly do not need APIPA.

    So - how have you ended up in a situation where you want your device and your Windows machine to be part of a local networking island? Remember that with APIPA you aren't expected to have a gateway, since the router that supplied that gateway would normally have been able to supply a working DHCP service, negating any need for APIPA.

Reply
  • Why do you - in this thread - post a link pointing back to this very thread?

    M$ has documentation how to use APIPA for Windows 7. All you need to do is to say that the primary setting should have an IP automatically assigned. Then as alternative configuration you keep the default APIPA setting checked. 30 seconds with Google...

    But it is only relevant if you want to create a local island of non-connected machines. So friend A and friend B can connect their two computers together without any DHCP server.

    So it might be practical in a tent out in the wilderness. But most people have an existing network with at least a dirt-cheap router - and suddenly do not need APIPA.

    So - how have you ended up in a situation where you want your device and your Windows machine to be part of a local networking island? Remember that with APIPA you aren't expected to have a gateway, since the router that supplied that gateway would normally have been able to supply a working DHCP service, negating any need for APIPA.

Children