Any ideas? The DHCP server works, as when connected via cable, DHCP is leased without issue.
Update:
I’ve confirmed when using manual IP settings it works ok. Just DHCP is causing an issue. With manual settings:
IP Address: 10.1.3.2
Subnet Mask: 255.255.0.0
Default Getway: 10.1.1.254
DNS Server: 203.0.178.191
Test DNS www.ghielectronics.com: 207.58.176.212
The full MFDeploy output is below:
Connecting to EMX_EMX…Connected
Set MAC addr …
mac = 00:1A:F1:00:42:0D
Mac address Set
Set regional domain …
region = fcc
Set security …
setting PSK key …
security key set
Scan … for ssid "wlan-ap2 "
WiFi link is not available yet! Wrong AP settings?
Still waiting.
[0] bssid = 00:04:ED:A9:05:87
strength = ###…
If it works with the static IP, I’d try restarting the router. Unplug it and leave it off for 30 seconds, then power it back on and try. The difference between the two interfaces is that each has its own MAC address, which is how the leases are given out. I’ve had several routers that would stop giving out leases to a specific MAC unless you restart them.
Make sure you have different MAC address for ethernet and the WiFi. I believe you are using the same router to test Ethernet and Wifi. The router might think it is a conflict in MAC addresses with two devices. Or better restart the router after changing the interface from Ethernet to Wifi.
Yeah it seems to take around 30 seconds for it to throw the exception. I’ll try restart router and post back with result when I’m home in couple hours. Can I change the Mac of Ethernet / zerog? Assumed they would be different, will check this also.
But be careful, WiFi and Ethernet uses the same network configuration in the system so updating the mac for one interface will affect the other interface. We hope to change this fact in future after supporting multiple network interfaces.
We don’t have tested this kind of routers. Not sure if ZeroG did.
These are couple hints that might help you out:
Make sure that you have the latest firmware on your router.
Try your system with a different router. Just to make sure that the system and your code is working.
Since you said DHCP worked with Ethernat, then most likely it should work or It might be a compatibility issue in ZeroG.
Both WiFi and Ethernet share the same DHCP client engine
I have the same problem. Copied the example exactly. Only changing SSID & WEP/PassPhrase.
Same problem. I also get all the messages you describe in MFDeploy. Yes it takes about 30 sec to fail.
So then I verified my MAC Address settings w/ my router (motorola surfboard) the Cobra’s address is unique among the router, pc, and laptop that are connected.
Updating my Router settings to have NO security and the same for the WiFi module works; except when I call save settings it raises an error in NetworkChange_NetworkAvailabilityChanged which can be stepped over to continue.
There is a common known issue with WEP “in general, not only on ZeroG”:
If you put a wrong passphrase with WEP, you will NOT get authentication failure. On the other hand, the system will not be able to communicate with the access point.
So DHCP works fine when you’re using WPA but not WEP? Are you sure you tested WEP with a static IP and not just WPA? As Josef said, it may be a WEP issue unless you successfully tested WEP + static.
Unless you have a specific need to connect to WEP access points (there ARE a lot of them out there), WPA/WPA2 is generally the preferred encryption as it’s far more secure.