Author Topic: LED Stuck on #3  (Read 1155 times)

fredwhit

  • Newbie
  • *
  • Posts: 7
LED Stuck on #3
« on: December 07, 2009, 08:33:36 PM »
Hello:

Ran my iobridge at my desk.  Just moved it to another building but on the same LAN, same DHCP server etc.  First attempt took several times plugging in the power before I got the green light. Had problems after I unplugged and replugged the fiber to the other building.  laptop works in that building fine (after fiber unplug and replug).  Now  I am stuck with a "3" on the LED and no green light.  Am able to ping the module so it clearly has an IP and I would have thought had negotiated the DNS?

Help!

Thanks

zero*gx

  • Full Member
  • ***
  • Posts: 116
    • zero*gx
Re: LED Stuck on #3
« Reply #1 on: December 07, 2009, 11:09:51 PM »
can we get info for what all of the numbers mean during ip negotiation? ive had my module has had 0 and 2 depending on my connection off site.
zero*gx | imagineering solutions

jason

  • Administrator
  • Hero Member
  • *****
  • Posts: 502
    • ioBridge.com
Re: LED Stuck on #3
« Reply #2 on: December 07, 2009, 11:45:16 PM »
Fredwhit,

If it's stuck on 3 then it's not able to resolve our servers hostname into an IP.  Is there more network traffic in the building as opposed to your desk?  I have seen that happen before.  I couldn't get it past 3 while I was running my network to the max.


zerogx,

From the wiki:

      Red Status Light Only - Module has booted successfully, looking for network connection
      1 - Network connection has been established
      2 - Successful DHCP transaction, the module now has an IP address
      3 - Starting DNS resolution
      4 - DNS resolved
      5 - Looking for an Internet gateway
      6 - Internet gateway found, initialing connection with server
      7 - Connected to server
      8 - Authencation
      Green Status Light Only - Everything is OK, begin normal operation
Jason Winters
ioBridge Developer

zero*gx

  • Full Member
  • ***
  • Posts: 116
    • zero*gx
Re: LED Stuck on #3
« Reply #3 on: December 08, 2009, 12:37:13 AM »
thanks... when i was facing the issue over the summer on the robotics network, that info wasn't available. (or if it was, i didn't know about it). I need to see if i can gwt the iobridge to go over the network. the main problem is all devices need to have a manual setup for a proxy/filter server.
zero*gx | imagineering solutions

fredwhit

  • Newbie
  • *
  • Posts: 7
Re: LED Stuck on #3
« Reply #4 on: December 08, 2009, 07:58:32 AM »
Jason:

Thanks for the response.  No, network traffic is pretty low.

My Linksys router is running DNSMasq software under dd-wrt so I don't know if that may be a problem.  In any event the module came back big time during the night and was sending me all kinds of messages.  This wasn't tied to anything I did (turning DNSMasq on and off) it just happened.  Oh well.


fredwhit

  • Newbie
  • *
  • Posts: 7
Re: LED Stuck on #3
« Reply #5 on: December 08, 2009, 01:37:46 PM »
Hmmm, now my module reports being offline again.  I can ping it however.

jason

  • Administrator
  • Hero Member
  • *****
  • Posts: 502
    • ioBridge.com
Re: LED Stuck on #3
« Reply #6 on: December 08, 2009, 01:54:32 PM »
I've never used DNSMasq, but it sounds like a potential source of your problem.  I sent you a PM with a possible solution.
Jason Winters
ioBridge Developer

WaveJam

  • Jr. Member
  • **
  • Posts: 63
    • WaveJam Technologies
Re: LED Stuck on #3
« Reply #7 on: December 09, 2009, 07:35:14 AM »
Just adding my experience with the #3 prob.

I have two modules, both running 4.1 firmware. I just upgraded one of them from 4.1 to 4.2 and it also got stuck at #3 after the 4.2 upgrade. I tried rebooting the module and it was stuck at #3 again. For giggles, I rebooted the module that was still at 4.1 and it came up just fine. I then jumped to the forum here and saw Jasons note about not being able to resolve the servers name. So, I double checked the DNS servers that DHCP assigns and they seemed to be resolving addresses just fine. Then I decided to check my DHCP tables and the IPs that were currently assigned and thats where it got interesting. I saw that the module running 4.1 was in the table, but the module running 4.2 code was not. I tried rebooting the 4.2 module again and still nothing in the DHCP table. It was as if the 4.2 module wasn't even trying to obtain an address. Or, maybe it wasn't waiting long enough for a DHCP response maybe? Anyways... the only other thing I can add is that out of frustration I rebooted the module several more times (in a row) and it finally obtained an address. This makes me wonder why/how the module wasn't first stuck at #2??
Pete Raumann
WaveJam Technologies
http://www.wavejam.com
http://www.tankedcam.com

Mr Sunshine

  • Newbie
  • *
  • Posts: 1
Re: LED Stuck on #3 (again)
« Reply #8 on: August 04, 2010, 11:16:23 AM »
Dear Jason,

My just bought and received my first iobridge.
For a long while (1 week of trying) it was stuck on #3 then today it went through and i got a connection logged on and flipped some switches, had a smile from ear to ear. ;D

But now it will not pass the 3 again, and I've changed nothing.
Any idea's on what to do.

Have done all kinds of hard reboots of linksys router (WRT610N) and cable modem.
No succes, please help.

best regards,

Wouter