Karlnet
[Top] [All Lists]

Re: [Karlnet] Configuring KN-100 SAT SOHO (possible dumb question)

To: "Bob Hrbek" <bhrbek@jagwireless.net>
Subject: Re: [Karlnet] Configuring KN-100 SAT SOHO (possible dumb question)
From: "Brad Gass" <bradlists@mnns.com>
Reply-to: bradlists@mnns.com,Karlnet Mailing List <karlnet@WISPNotes.com>
Date: Wed, 5 May 2004 17:17:42 -0500 (CDT)
List-post: <mailto:karlnet@WISPNotes.com>
I found it very bizarre too, which is why I wondered if I'm missing
something in doing a forced reload, or if a corrupt LKF or BIN would cause
it, software bug, what?

It works just fine after a fresh reload and IP change *until* I save the
changes back to it and reboot.  Then, it boots, replies to pings a few
times, and dies.

I would have thought that an incorrect LKF or corrupted BIN would have
become apparent immediately on reboot from forced reload.  I'm really at a
loss here.

Karlnet?


Brad

> I've replaced 3 RG-1000's this year that were doing that.  I just figured
> they got a little more electricity than they could handle.  I never even
> bothered to try the reload.  (well I did on one last year but it was a
> failure...so I decided to not repeat my failures)
>
> Anyway....it is VERY strange that immediately after loading the BIN it
> works
> for hours/days.
>
> -b
> ----- Original Message -----
> From: "Brad Gass" <bradlists@mnns.com>
> To: "Karlnet Mailing List" <karlnet@WISPNotes.com>
> Sent: Wednesday, May 05, 2004 3:50 PM
> Subject: [Karlnet] Configuring KN-100 SAT SOHO (possible dumb question)
>
>
> OK, I've got a really odd problem here that I'm either missing something
> dumb (always possible), or something really bizarre is happening.
>
> I've got a KN-100 that I had to do a forced-reload procedure on.  I go
> into forced-reload mode, set an IP address, open the correct BIN and LKF,
> save it to the board, and it reboots as it should.
>
> Then, I do a local scan, it finds the unit, I assign an IP to it (same one
> I used in forced-reload mode), and it's fine.  I can sit there all day
> long (literally, been pinging/monitoring it for >24 hours now) and
> connectivity is perfect.
>
> I configure the IP settings (in this case, 192.168.251.99, 255.255.255.0,
> gateway 192.168.251.254), touch nothing else, save the config to the unit,
> and it reboots.
>
> Here's where it gets wierd.
>
> Right after reboot, the unit responds to pings a few times (4-8 to be
> exact), and then it drops off the face of the Earth.  A local network scan
> doesn't see it, nothing.  I power cycle the unit and I get the same thing.
>
> What am I doing wrong here?  I've fiddled with the ethernet port settings
> (defaults to 10M/half, tried 100M/auto and auto/auto with the same
> results), and tried two different hubs/switches (Linksys 5 port
> autosensing and a D-Link 8 port 10/100) and neither did anything
> different.
>
> Link lights are fine on both the KN-100 and the switch port.
>
> Am I missing something really dumb, or is there something deeper going on?
>  I'm trying to load 4.44 into the unit, and when it stops responding, the
> power LED is green, ethernet green (and see's activity), middle two LED's
> red BTW.
>
> Thanks!
>
>
> Brad
>
>
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com
> http://lists.wispnotes.com/mailman/listinfo/karlnet
>

_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet

<Prev in Thread] Current Thread [Next in Thread>