NetUSBee troubles

[Gaiyan]

Hi,

I'm supposed to be an expert in this field but I can't get this bloody thing to work at all. I just got my NetUSBee today from Lotharek. I've tried Sting, MagicNet and MiNTNet. I'd rather use MiNTNet.

Anyway, here's my setup so far.

TT030
Fresh VanillaMint
ENEC3.XIF in C:\MINT\1-19-CUR\ it shows up at boot as en0 and get's a MAC address
ifconfig shows that en0 is up "inet 192.168.1.30 net mask 255.255.255.0 broadcast 192.168.1.255" just like it's supposed to
route is good: default 192.168.1.1 en0

Link is up on the device and switch

Nothing works though! I can't ping or anything. Sting didn't work either. I'm beginning to think that this is cactus. HELP!

[Gaiyan]

I've tried a different cable, bypassed the switch directly to router nothing.

I tried Sting again. Nothing. I can ping myself but not outside. My IP is set right. My route.tab is:

0.0.0.0 0.0.0.0 EtherNet 192.168.1.1

It's cactus.

[Gaiyan]

uIP tool doesn’t work it says:

uIP tool, version 43
RTL8019 init .. MAC: 0:0:0:0:0:0
DHCP: (just blinks)

When I press a button, it disappears.

[Gaiyan]

I've emailed Lotharek and he's been in contact. If any of you have ideas, I'd appreciate it.

Meanwhile I'll be installing Thunder + Storm

I'll take a look at the cartridge port and fuse at the same time.

[AdamK]

With Sting you have to be very careful editing route.tab - whitespace matters, eol matters.

[Gaiyan]

Yeah, no problems there.

I'll try my MSTE when I'm done installing Thunder + Storm

[rpineau]

IT seems that the MAC address is not set on the chip. The NetUSBee when it comes from Lotharek is supposed to already have a MAC set.
If your MAC is not set the switch/router will not know to which MAC to send packets and that's probably why it doesn't work even though everything is up.
In MiNT, if you do a ifconfig en0, what MAC do you see, If it's all 00:00:00:00:00:00 that would confirm that this is indeed the issue.
The NetUSBee should have an eeprom on it that contains the MAC and I believe there is a tool to set it of it's not set : http://lotharek.pl/zasoby/produkty/73/pliki/setmac.prg

Try that and that might fix the issue
Rodolphe

[Gaiyan]

IT seems that the MAC address is not set on the chip. The NetUSBee when it comes from Lotharek is supposed to already have a MAC set.
If your MAC is not set the switch/router will not know to which MAC to send packets and that's probably why it doesn't work even though everything is up.
In MiNT, if you do a ifconfig en0, what MAC do you see, If it's all 00:00:00:00:00:00 that would confirm that this is indeed the issue.
The NetUSBee should have an eeprom on it that contains the MAC and I believe there is a tool to set it of it's not set : http://lotharek.pl/zasoby/produkty/73/pliki/setmac.prg

Try that and that might fix the issue
Rodolphe

Thanks. No, the MAC is fine. It shows up on boot and also in ifconfig.

Thunder + Storm installed. NICE! I don't have an IDE device yet But the RAM is nice and fast.

Anyway I checked the rom port fuse and it was fine. I'll have to try the MSTE.

[rpineau]

Ok.
Next thing would be , if you have a managed switch (I use Cisco and Arista switches), to check if the port goes in errdisable on the switch and if it does what is the reason for this.
At this point as it fails with multiple TCP/IP stack and other tools it's most probably a hardware issue like a bad chip, bad RJ45 plug or bad MAC even if present, also .. I assume you checked the cable .

[Gaiyan]

Ok.
Next thing would be , if you have a managed switch (I use Cisco and Arista switches), to check if the port goes in errdisable on the switch and if it does what is the reason for this.
At this point as it fails with multiple TCP/IP stack and other tools it's most probably a hardware issue like a bad chip, bad RJ45 plug or bad MAC even if present, also .. I assume you checked the cable .

Unfortunately no managed switches here. I've tried different cables and network devices

Weirdness continues. I tried my MSTE.

uIP tool works. It assigns a MAC: 00:0a:77:e4:a0:9e and browser window thingy works fine.
Sting STILL doesn't work but gets a MAC: f4:04:02:31:2e:31
SetMAC.prg assigns a MAC: 00be:7d:af:f4

I'm going crazy.

[stormy]

Okay try:
1. Make sure you have the correct ENEC3.XIF, the Assamsoft driver seems to be the very best. If you use Assamsoft your port will be ne0 not en0. (http://assemsoft.atari.org/ne2k/index.html)
2. Use the Vanillamint network setup utility only, don't mess with mac address stuff.
3. profit

Also note uiptool does not work inside mint, only TOS.

[Gaiyan]

Okay try:
1. Make sure you have the correct ENEC3.XIF, the Assamsoft driver seems to be the very best. If you use Assamsoft your port will be ne0 not en0. (http://assemsoft.atari.org/ne2k/index.html)
2. Use the Vanillamint network setup utility only, don't mess with mac address stuff.
3. profit

Also note uiptool does not work inside mint, only TOS.

Oh, come here and I'll give you a big hug! That was it! ENEC3.XIF didn't work at all. NE2KENEC.XIF and ne0 did the trick. Thanks!

[stormy]

Thanks for the hug, lol

[Gaiyan]

Still, even though it works, it doesn't explain why uIP tool won't work on the TT in TOS. Or why Sting won't work with ENEC3.STX on either machine. Hmm. But Litchi works, transfer files, resolves domain names. I'm happy. Although no idea why my own FTP won't list files from my Synology NAS. Works from any other device including Aranym.

[trecool]

For running uIP tool, make sure you are not loading any tcp/ip stack.
Just boot on plain TOS.

[susher]

I've a Netusbee Lite which works on ST(e)s but not on my TT, giving the same issues with UIP.

HT2ENEC.TOS is returning the correct MAC address though.

[susher]

Having done more cleaning of the cartridge port netus.tos now passes the diagnostics.

However UIPtool doesn't work and I think that I've found out why, having looked at the source code. It's using hard-coded timing loops!

On a MegaSTE this probably doesn't matter too much as it'll only halve the time that the loops take but on the TT the 68030 will run through these increadibly quickly as not only will they fit in the cache but will be pipelined. No-wonder it doesn't work!

Now, to see if I can get STing to work... Not managed it so far this afternoon.

[jd]

Having done more cleaning of the cartridge port netus.tos now passes the diagnostics.

I can't emphasis enough how important this is, I spent days trying to get my Hydra (Netusbee with only ethernet) to work thinking it was everything from faulty cartridge port, faulty hydra, broken Sting config, screwed Falcon.

Final throw of the dice cleaned the hydra copper cartridge contacts with contact cleaner and blew a whole air can on the cartridge port.

Prayed and now works like a charm.

So just so no-one has to go through my pain - clean every contact especially anything cartridge port based!