USBNet/Telnet fail, need help

[glasnost]

USB into the windows box. I am not touching the WAN or even the LAN for any of this!

My connection is Kindle (microusb) -> Windows box (USB3)

Nothing is virtualized, nothing should be out of the ordinary here -- if we find something that is amiss, then I may have bigger problems on my hands ;-)

[knc1]

Originally Posted by glasnost

After the update completed, the kindle tree showed up and a small box appeared that said "Bridge+" in the below the tree. Can I assume that this means the bridge worked correctly? And so in theory, I should have a stock+jailbreak system partition?

Correct, that was the bridge code re-installing the jailbreak certificate and other vital parts.

Your good to go -
You may have to re-install all of your add-ins, but that is normal after a firmware version update.

[NiLuJe]

@glasnost: Wipe the usbnet folder, reboot, reinstall usbnet, try again.

[glasnost]

I got it working (edited my OP, neglected to update here, apologies)

Flashing the system and then ignoring the conflicting advice in various threads re: usbnet settings & just following the wiki settings worked great :-)

Thanks for your help and patience.

[knc1]

In my list of customer_*.update links, I only went back to the most recent 5.7.x
I could include the most recent 5.6.x (5.6.5) if there was any interest in going back to the version with the broken browser.

[glasnost]

'meh - I never use the browser. But I love the idea of providing links with context :-) e.g. '5.6.5 - the one with the broken browser' '5.7.2 - new x' '5.8.3 - more secure, but breaks a, b, c'

it would help those of us who are just getting our feet wet understand what the options are! Thanks again for your help.

[knc1]

Originally Posted by glasnost

'meh - I never use the browser. But I love the idea of providing links with context :-) e.g. '5.6.5 - the one with the broken browser' '5.7.2 - new x' '5.8.3 - more secure, but breaks a, b, c'

it would help those of us who are just getting our feet wet understand what the options are! Thanks again for your help.

Go ahead and write it up somewhere, I'll reference in the already too long set of directions.
Putting it in the Wiki here might be a good idea, then others can help you keep it up to date.

[NiLuJe]

@glasnost: For future reference, always trust the original thread and bundled directions over *anything* else. (In USBNet's case, that means the bundled doc, since there's no doc in the thread, by design).

Unmaintained/old/incompatible third-party documentation is a recipe for disaster.

[knc1]

Originally Posted by NiLuJe

- - - - -
Unmaintained/old/incompatible third-party documentation is a recipe for disaster.

Just ask any of the zillion Chinese who bricked their Kindles last month.

[geekmaster]

Originally Posted by knc1

Just ask any of the zillion Chinese who bricked their Kindles last month.

Revenge for Chinese cyberterrorism? Or just karma?

[knc1]

Originally Posted by geekmaster

Revenge for Chinese cyberterrorism?
Or just karma?

karma
well deserved karma

[glasnost]

Originally Posted by NiLuJe

@glasnost: For future reference, always trust the original thread and bundled directions over *anything* else. (In USBNet's case, that means the bundled doc, since there's no doc in the thread, by design).

Unmaintained/old/incompatible third-party documentation is a recipe for disaster.

I always try to trust the documentation. But in this case, the documentation sent me to a post that - while delightfully snarky - failed to impart a few steps in the process that were essential AND added a little bit of confusion. Moreover, some of these release threads have posts going back several years - and what worked 4 years ago may not work today, putting a lot of thread information into the category of 'unmaintained third-party documentation.'

That said, your documentation looked perfect from a linux shell - if I had my project box up and running with me, I wouldn't have had an issue. I've been maintaining a cutting edge Gentoo/Funtoo build for years. Unfortunately, I just have this work laptop and it's win10 exclusive :-(

So, for me, the solution was to go to the wiki and hope that whoever wrote it was working on the latest info. In this case - they were! And I subsequently tried to clarify the wiki further on this point (yay for community involvement!)

I ~love~ and ~greatly appreciate~ your work & I think it speaks volumes about the community that several old hands tried to help me mitigate a potential PEBKAC.

[NiLuJe]

@glasnot: Which post was that, for future reference? (And which exact wiki page, too, since I recall there are a few of them).

I readily admit not ever having *once* set this up on a Windows box, so, yeah, that doesn't help, documentation writing wise .

Meaning I'll take anything you can point me to that looks sane and better than what's currently in the doc .

[glasnost]

Originally Posted by NiLuJe

@glasnot: Which post was that, for future reference? (And which exact wiki page, too, since I recall there are a few of them).

I readily admit not ever having *once* set this up on a Windows box, so, yeah, that doesn't help, documentation writing wise .

Meaning I'll take anything you can point me to that looks sane and better than what's currently in the doc .

I'll write you up something sane and probably add it to the wiki. :-)

Meanwhile:
In the doc, you reference https://www.mobileread.com/forums/sho...22&postcount=3 as a good post for windows users. I had two problems with it: 1. the author changed the recommended IP settings, contrary to your doc (ln 82-85). And the author seemed confused about why the IP settings were set in that manner. 2. The sarcasm, while witty and amusing, was a little distracting and it may be difficult for a non-native/non-fluent English speaker to follow the instructions.

I was a special case, in that I used #bash for windows (yay for getting a sane commandline and access to unix tools in native win10!) and followed the doc and used the steps here: https://wiki.mobileread.com/wiki/Kind...USB_Networking

Thanks again for your help & I'll post steps this weekend.