XMC-1 Network setup problem

[TheTerrorBeyond]

Sept 4, 2014 0:40:27 GMT -5 doc1963 said:

Sept 3, 2014 23:14:27 GMT -5 bluescale said:

TheTerrorBeyond and doc1963 - Have either of you tried backing up settings and doing a factory reset? I'd be curious to know if that makes a difference. Keith suggested in another thread that they've seen a few cases of odd, inexplicable behavior go away. I'm thinking this step might shoot to the top of the troubleshooting list.

Yes… I did try a hard reset, but it made no difference.

Mine has maintained a network connection (with DHCP unchecked), so I've never given it a second thought until I read this post.

With this in mind, I will skip the reset. Thanks!

[markstubb]

So, I know a lot of folks have discussed this DHCP 'bug', but this is what I think is happening:

I think the VAST majority of folks have a 192.168.1.x/24 network in their house. It's probably the default network on just about most consumer networking gear. When you 'uncheck' dhcp, there's just an initial static IP assigned of 192.168.1.127, which probably works in most everyone's network. Your subnet being wrong won't really impact anything, so having 255.0.0.0 (or any variant below 255.255.255.0) will actually work fine.

For instance, on my network, I use 192.168.15.x, and when I unchecked DHCP, i got the same IP yall got - 192.168.1.127, which doesn't exist anywhere in my network.

DHCP checked doesn't worked either.

I haven't tried to leave it checked and reboot, but the weirder thing is my router is showing a lease to the right MAC on the XMC-1, but it doesn't ping and it doesn't show up in the network information area.

Just my .02

[sandiway]

I just got my brand-new XMC-1 (FW 3.0) and I confirm I see the same bug when I use a Netgear WNCE2001 wireless adapter (bridge) to connect to a Netgear router.
The WNCE2001 is working properly. The Netgear router is working properly.

Are people able to use Dirac despite the bug?

DHCP checked results in the 62.0.0.0 address and the weird subnet mask etc.

DHCP unchecked results in the 192.168.1.127, which seems self-assigned.
This address is unping-able and useless.

If I manually uncheck DHCP and manually set in something like 192.168.0.20 (unused) with the correct net mask 255.255.255.0, gateway etc. it becomes pingable:

ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=6.210 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=5.116 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=4.905 ms
...

The WNCE2001 is working fine. It is pingable (on my LAN). And it even has a webserver which says it is okay.
The router also sees the WNCE2001 correctly. But it obviously does not have the XMC-1 in its "Attached Devices" table.

With the DHCP re-checked. The 192.168.0.20 I typed in seems to survive the XMC-1 cold boot.
The DNS I typed in manually got wiped.
And it's ping-able using the 192.168.0.20 after the cold boot.

I don't have an ethernet cable long enough to hardwire the XMC-1 to my router to try taking the WNCE2001 out of the equation.
But I'll try to pick up a long cable tomorrow

Sandiway

[geebo]

Apr 10, 2015 6:01:34 GMT -5 sandiway said:

I just got my brand-new XMC-1 (FW 3.0) and I confirm I see the same bug when I use a Netgear WNCE2001 wireless adapter (bridge) to connect to a Netgear router.
The WNCE2001 is working properly. The Netgear router is working properly.

Are people able to use Dirac despite the bug?

DHCP checked results in the 62.0.0.0 address and the weird subnet mask etc.

DHCP unchecked results in the 192.168.1.127, which seems self-assigned.
This address is unping-able and useless.

If I manually uncheck DHCP and manually set in something like 192.168.0.20 (unused) with the correct net mask 255.255.255.0, gateway etc. it becomes pingable:

ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=6.210 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=5.116 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=4.905 ms
...

The WNCE2001 is working fine. It is pingable (on my LAN). And it even has a webserver which says it is okay.
The router also sees the WNCE2001 correctly. But it obviously does not have the XMC-1 in its "Attached Devices" table.

With the DHCP re-checked. The 192.168.0.20 I typed in seems to survive the XMC-1 cold boot.
The DNS I typed in manually got wiped.
And it's ping-able using the 192.168.0.20 after the cold boot.

I don't have an ethernet cable long enough to hardwire the XMC-1 to my router to try taking the WNCE2001 out of the equation.
But I'll try to pick up a long cable tomorrow

Sandiway

I have my XMC connected to a bridge and Dirac work perfectly with it.

I wonder if your DHCP box is reversed.

[dkojevnikov]

I just entered IP address, mask, router and DNS manually. Works like a charm. DHCP functionality is broken

[sandiway]

Apr 10, 2015 6:58:42 GMT -5 dkojevnikov said:

I just entered IP address, mask, router and DNS manually. Works like a charm. DHCP functionality is broken

I bought a 25ft long ethernet cable today. Same thing weird thing I (and others) reported also happened with a direct connection to my Netgear router.

So it's not my Netgear WNCE2001 Universal WiFi Internet
Adapter.

I'm pretty sure it's not my Netgear router. I connect everything to the router from a Wifi thermostat for the house, the Oppo, flat screens, samsung, apple cellphones, lots of computers. And everything works flawlessly except the XMC-1.  The XMC-1 is the odd one out. Yes, I agree DHCP functionality is broken. You are right.

I've checked the router settings carefully via the Netgear web browser-interface.
(I could have missed something but I don't believe so: as a computer scientist, I think I'm technically up on computers as well.)

So at the moment, I uncheck DHCP and give it a LAN address in the 192.168.x.x block that I know the router won't hand out to other devices using DHCP. And I can ping it fine. I can telnet to it fine on port 23. I can ping from the XMC-1 to my LAN attached devices. ifconfig eth0 looks fine.

[pode]

Dear all
I just experienced the same problem of connection with my (brand new ; ) XMC-1 to my home network. I found that the factory-given IP address (127) was out of range of my box (max is 50). I changed it to 192.168.1.40 and now it works and the Dirac program finds directly the XMC-1. I copied all other parameters (DNS, Gateway...) as they are stated on my computer. Last, I set the XMC-1 IP address as fixed in the Box. I hope this helps.

[ericl]

So does it "work" with DHCP unchecked?

[mickseymour]

Jan 15, 2017 14:13:25 GMT -5 ericl said:

So does it "work" with DHCP unchecked?

Yes if you set the IP address of the XMC-1 manually.