I recently obtained a VM201 and have it set up with a static IP address (DHCP disabled). Then I noticed that a rogue DHCP server had shown up in my network, assigning IP addresses to clients. It turns out that it’s the VM201 that is giving out IP addresses (actually, it seems to only give out 192.168.10.2 in my case - to everyone!):
I can’t find a way to turn that off which is quite a big problem for me as I don’t want clients on my network to get IP addresses that are assigned by the VM201.
Details:
Ethernet Relay Card
Build: 1236
Build date: Sep 07 2012 08:56:42
TCPIP Stack: v5.42
I really hope that someone can help me here.
We will need some more information to look into this. What devices are on your network and how is everything connected?
[quote]I recently obtained a VM201 and have it set up with a static IP address (DHCP disabled).[/quote]What IP adres?
[quote]Then I noticed that a rogue DHCP server had shown up in my network, assigning IP addresses to clients.[/quote]How did you notice? What clients got which IP addresses?
[quote]It turns out that it’s the VM201 that is giving out IP addresses (actually, it seems to only give out 192.168.10.2 in my case - to everyone!):[/quote]How did you know that it turned out ot be the VM201? And who is everyone?
I’m quite advanced when it comes to networks. The VM201 has the IP address 192.168.10.194 in 192.168.10.0/24, a DHCP server is active there but the VM201 has been configured with a static IP address:
IP Address: 192.168.10.194
Gateway: 192.168.10.1
Subnet: 255.255.255.0
Prim. DNS: 192.168.10.10
Sec. DNS: 192.168.10.11
MAC Address: 00:04:A3:8D:6C:27 (Microchip Technology)
This is the same IP address that is sending out the DHCP responses, as can be seen in the tcpdump that I pasted earlier, and the DHCP dump below:
Seeing as both the IP address and MAC address match those of the VM201, I am confident that it’s the VM201 that’s running a DHCP server. I noticed because I saw clients getting IP addresses that they’re not supposed to have. The VM201 seems to give out only one IP address, 192.168.10.2. It seems to give this to every client that asks (hence ‘everyone’).
This seems to be caused by the DHCP server that seems to be compiled in in your TCP/IP stack, as the ‘STACK_USE_DHCP_SERVER’ define in TCPIPConfig.h seems to be enable the ‘functionality’ that i’m currently seeing:
#define STACK_USE_DHCP_SERVER // Single host DHCP server
If this is the case then this can probably be easily solved by removing the define and recompiling the TCP/IP stack.
You are 100% correct, we will do our best to get this problem fixed as soon as possible. We still have some other pending bugfixes and feature changes for the VM201, so this may take a little bit of time.
I’m running Windows 7 32/64 bit and IOS on our Iphones/Ipad. We have 2 Android mobiles too.
It seems like all the devices that is set to DHCP, get the IP adress as gateway to the router. Instead af 192.168.1.1 it gets 192.168.1.160 whitch are the fixed ip for VM210.
It’s really a problem, when do you think there is a update ready?
I am having a similar problem, appears the VM201 is acting a DHCP server and confusing our network.
Plugged the VM201 into our work network over the weekend, come Monday morning and none of the staff could obtain an IP address automatically on the client machines.
Unplugged the VM201 and everything returned to normal.
We have a Windows 2012 server acting as the domain controller and DNS server.
A Netgear cable router acting as the DHCP server.
All client machines configured to obtain IP address automatically
And the VM201 has a fixed IP address
Hi!
I have the same problem and tested updating however the vm201 does not accept the firmware
Wireshark shows the the tftp transfer beeing retried but vm201 does not ACK the file.
I’m running linux and i’m executing “tftp VM201-ipaddress -c put VM201Build1315.bin”
I had the same problem with the tftp upload failing when using an linux based tftp client/third party windows tftp client. It only worked using the ‘stock’ Windows tftp client for me.
Also, we’ve been running with the latest firmware for a while now (after I had been contacted by a Velleman technician) and the problems I mentioned earlier have been resolved.
This was a nasty problem (for me at least)! The VM201 was just one of quite a number of changes I recently added to my network (I know…). It took me some time to figure out that some new device was acting as a new, second DHCP server, handing out “illegal” IP addresses, or actually constantly the same one: 192.168.1.2 in my case, after which I ran into lots of different issues. Initially it did not appear to make sense that the VM201 would also act as a DHCP server but after (eventually…) unplugging it and seeing things going to normal again in my rather complex home network I decided to take a deeper look into the VM201 fora and issues. And voila, I ran into this entry.
Using a Windows XP SP3 computer I managed to upload the bin file to the VM201 using TFTP (Windows7 did not respond to a TFTP command). I have not yet tested whether this firmware fixes my problem but will test that in the next couple of days. Just wanted to reassure others that my firmware release 1236 indeed did have a similar problem and that I eventually successfully managed to TFTP the new firmware to the VM201.
Further to the above, herewith confirming that the VM201 no longer acts as a DHCP server after successfully installing the latest firmware linked earlier in this thread.
Thank you for helping; hope this helps others too.
I don’t know if i’m the only one who still struggling to download the the image file: VM201Build1315.bin
the link you pointed doesn’t work.
please post a valid one.
I’m waitting.
The link is working perfectly. It is probably your browser that is desperately trying to figure out what application to open it in instead of simply downloading it.
Downloading the zipped version will probably be less of a problem