Karlnet
[Top] [All Lists]

[Karlnet] Very Odd KN-100 Forced Reload Issue (WAS: ConfiguringKN-100 SA

To: "'Karlnet Mailing List'" <karlnet@wispnotes.com>
Subject: [Karlnet] Very Odd KN-100 Forced Reload Issue (WAS: ConfiguringKN-100 SAT SOHO)
From: "Brad Gass" <bradlists@mnns.com>
Reply-to: bradlists@mnns.com,Karlnet Mailing List <karlnet@WISPNotes.com>
Date: Thu, 6 May 2004 09:58:20 -0500 (CDT)
List-post: <mailto:karlnet@WISPNotes.com>
Rick,

Same network, same switch, and three foot patch cables even.

It's my understanding that as you said, if the license was bogus, it would
come up all red LED's.  And I assume that the configurator or the board
does some kind of checksumming on the BIN file to at least do something to
verify it's not corrupted?

Reg/Karlnet, can you give me any ideas as to what's going on here?  After
a forced reload, the unit is clean, right?  So, I can just scan network,
change IP, open remote config, make my changes, save config and reboot,
right?  Am I missing something?

Does anyone have an older version of the SAT SOHO firmware I can try out
(maybe 4.31)?  All I've got is 4.44 for it.


Brad

> Your computer is on the same network as the board isn't it.  It almost
> sounds like your NIC card is not on the same subnet.  The board sounds
> like it is acting fine.  If it was the wrong license, all the lights
> would be red.
>
> Rick Harnish
> President
> OnlyInternet Broadband & Wireless, Inc.
> Supernova Technologies, Inc.
> Supernova Network Services
> rharnish@oibw.net
> www.oibw.net
> 260-827-2482 office
> 260-307-4000 cell
> MSN: r_harnish62@hotmail.com
> ICQ: 293578162
>
>
> -----Original Message-----
> From: Brad Gass [mailto:bradlists@mnns.com]
> Sent: Wednesday, May 05, 2004 3:51 PM
> To: Karlnet Mailing List
> 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

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