Help setting up Roadshow with X-Surf 100

[Overmann]

Hi,

So, right away I can say that I've been using roadshow since release now and I've never been able to get it running smoothly or easily. I've only tried PCMCIA wifi before but now I am trying to configure it with X-Surf running on my Elbox Zorro IV busboard in my towerized A1200. I was hoping it would be a breeze but this is more frustrating then ever.

I have xsurf100.device in devs/netinterfaces and set up with

address=192.168.10.142
netmask=255.255.255.0

DHCP does not work. If I write configure=DHCP initialization times out when I try adding the netinterface.
I have roadshows routes set up as:

default 192.168.10.1

That is the adress to my router. I have roadshows name_resolution set up as:

nameserver 109.247.114.4
nameserver 92.220.228.70

Those numbers are from ipconfig /all on my PC's.

When I start the internet-startup (addnetinterfaces etc.) everything seems to detect fine. The Amiga gets it's IP, name resolution is set gateway detected etc. but when I start a browser and try to load a website I get a message saying:
"Host lookup failed, no DNS entry found."

I've tried reading the roadshow manual and I've tried my best to understand what I am doing wrong, but this looks perfectly fine to me. I've tried PING to one of my other computers on the network (just PING 192.168.10.122), but get:

PING: wrote 192.168.10.122 64 chars, ret=1
PING: sendto: unknown error code

--- 192.168.10.122 ping statistics ---
276 packets transmitted, 0 packets recieved, 100% packet loss

I have no idea what I'm doing so I once again turn to this forum and it's users for help. Every suggestion is greatly appreciated!

[patrik]

Originally Posted by Overmann

I have xsurf100.device in devs/netinterfaces and set up with

Is x-surf-100.device located in DEVS:Networks/?

Originally Posted by Overmann

address=192.168.10.142
netmask=255.255.255.0

If the above changes are applied to DEVS:NetInterfaces/X-Surf-100, they look correct.

DHCP does not work. If I write configure=DHCP initialization times out when I try adding the netinterface.
I have roadshows routes set up as:

Originally Posted by Overmann

default 192.168.10.1

If this is added to DEVS:Internet/routes, it looks correct. Can you ping your router? If not, something is very wrong.

Some more suggestions:
Have you tried setting the X-Surf-100 to Zorro2 mode?
Are you using the latest x-surf-100.device? The latest has one driver for all CPU:s and does not give troubles if wrong version is chosen.

[Overmann]

Originally Posted by patrik

Is x-surf-100.device located in DEVS:Networks/?



If the above changes are applied to DEVS:NetInterfaces/X-Surf-100, they look correct.

DHCP does not work. If I write configure=DHCP initialization times out when I try adding the netinterface.
I have roadshows routes set up as:



If this is added to DEVS:Internet/routes, it looks correct. Can you ping your router? If not, something is very wrong.

Some more suggestions:
Have you tried setting the X-Surf-100 to Zorro2 mode?
Are you using the latest x-surf-100.device? The latest has one driver for all CPU:s and does not give troubles if wrong version is chosen.

I have it set in Zorro II mode (with the jumper on the card). Pinging the router (192.168.10.1) gives the same results as pinging the PC.
Perhaps I have to do a clean install. This machine/setup has been through many changes these past months. After I read your message I tried enabling debug in the x-surf config-file and the program crashed. I had addnetinterface set to autostart on boot so now I needed to boot from floppy to change the user-startup so that doesn't happen BUT after I did that the machine won't boot.. :P

[patrik]

What exactly do you mean by “addinterface set to autostart on boot”? The normal way to automatically activate an interface on boot is to have the interface file and it’s icon (.info) in Devs:NetInterfaces/ instead of Sys:Storage/NetInterfaces/.

If it doesn’t boot, boot without startup-sequence and move the files from Devs:NetInterfaces/ to prevent it from being loaded.

[Overmann]

Ok, it appears the problem is with my universal repeater. If I connect the Amiga directly to my modem/router it works fine, but if I connect it to my universal repeater (which is what I use to connect my old computers) the amiga/xsurf won't fetch any data from the internet or ping anything.

The Amiga is the only device that is unable to work with my universal repeater. I'm sure I've done something wrong in the setup that the Amiga doesn't like, but my win98 and XP-machines all work perfectly fine with it.

[patrik]

What kind of repeater is it?

[Overmann]

Originally Posted by patrik

Is x-surf-100.device located in DEVS:Networks/?



If the above changes are applied to DEVS:NetInterfaces/X-Surf-100, they look correct.

DHCP does not work. If I write configure=DHCP initialization times out when I try adding the netinterface.
I have roadshows routes set up as:



If this is added to DEVS:Internet/routes, it looks correct. Can you ping your router? If not, something is very wrong.

Some more suggestions:
Have you tried setting the X-Surf-100 to Zorro2 mode?
Are you using the latest x-surf-100.device? The latest has one driver for all CPU:s and does not give troubles if wrong version is chosen.

Originally Posted by patrik

What kind of repeater is it?

It is a Jensen AirLink 89300. I've been trying to get a stable connection up and running with it for a while now with no luck. I got it to work for an evening, but the next day I was back to no DNS.

[patrik]

When I google on Jensen AirLink 89300 it looks like a router, not a repeater.

[Overmann]

Originally Posted by patrik

When I google on Jensen AirLink 89300 it looks like a router, not a repeater.

Yes, that's correct, but it can be set up as an access point and repeater.

EDIT:
Do you think I would be better off buying a device that is a dedicated repeater? Always seemed like a waste of money to me, as most routers that i've owned have had a repeater-mode.

[patrik]

It just sounds like it does something fishy. Preferably it should be completely transparent and just bridge any Ethernet<->WiFi traffic on the Ethernet packet level - acting as a wirelessly attached switch to your normal AP.

Are you sure it still isn’t acting as a router, creating a separate network for anything connected to it?

[Overmann]

Originally Posted by patrik

It just sounds like it does something fishy. Preferably it should be completely transparent and just bridge any Ethernet<->WiFi traffic on the Ethernet packet level - acting as a wirelessly attached switch to your normal AP.

Are you sure it still isn’t acting as a router, creating a separate network for anything connected to it?

I've wired my Amiga back up with my main router now, and this time around my config isn't working with that either. I have no idea what is going on!

I wish someone could make an idiot-proof front end for roadshow. I am clearly doing something wrong but I have no idea what. shownetstatus shows that my amiga has the requested IP, the ip of the router checks out and that my two DNS adresses are assigned, but my browser does not want to open any websites and PING gives 100% packet loss.

I'm having another strange issue. My floppy drive isn't working in workbench. It works fine on boot, but as soon as the startup-sequence kicks in it somehow disables the floppy drive. There is something stupid going on in my startup sequence I bet. I have to give it a comb through, or start over with a fresh install again. I have a strange habit of messing things up without understanding how, it seems.

[patrik]

You should try most basic stuff first. Can you ping your router ip or some ip of another computer on the same switch?

For that step, the “front end” is more or less idiot-proof - the only thing needed is that you configure the NetInterface file with a valid ip-address, nothing else is required.

If it still isn’t working you either have no link (check link LEDs), ip-address conflict (verify no other computer have same ip) or a driver/hardware issue. Then move the NetInterface file to Storage/NetInterfaces and run “addnetinterface x-surf-100” manually after boot and see what it says.

[Overmann]

Originally Posted by patrik

You should try most basic stuff first. Can you ping your router ip or some ip of another computer on the same switch?

For that step, the “front end” is more or less idiot-proof - the only thing needed is that you configure the NetInterface file with a valid ip-address, nothing else is required.

If it still isn’t working you either have no link (check link LEDs), ip-address conflict (verify no other computer have same ip) or a driver/hardware issue. Then move the NetInterface file to Storage/NetInterfaces and run “addnetinterface x-surf-100” manually after boot and see what it says.

I'm on a clean WB 3.9 now and the problems persist. I've tried pinging the router or a different computer on the network but I get 100% packet loss.

Now, the first time I connected after doing a clean reinstall x-surf-100 was set up to configure using dhcp and it worked. I was online, downloaded a few files and stuff. Then after a reboot it won't work. Dhcp won't work and manual config won't work. I've changed nothing since the first time. There is no IP-config and the LED on the xsurf blinks when attempting to configure.

So now, when trying to configure using dhcp it simply times out, when doing it manually all adresses are assigned and it doesn't complain, but I get 100% packet loss. One strange thing I noticed. When I first connected with DHCP and everything worked I typed "shownetstatus" and it had 5 or 6 DNS-adresses assigned. I've only specified two in my "name_resolution" file. Ipconfig on my PC only reports two.

I've moved the NetInterface file to Storage/NetInterfaces and I've run “addnetinterface x-surf-100” manually, but it acts the same way.

[Overmann]

I've enabled debug in x-surf-100 now, and the message that keeps repeating is:

Fri sep 21 10:23:51 2018 [debug]: Interface 'x-surf-100' hardware address = 00.00.00.00.00.00.
Fri sep 21 10:23:53 2018 [debug]: Setting up BOOTP packet for 'x-surf-100' with hardware address 00:00:00:00:00:00.
Fri sep 21 10:23:53 2018 [debug]: Sent initial DHCPDISCOVER request for 'x-surf-100'; transaction ID=0x1A5E2A68, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours."
Fri sep 21 10:23:58 2018 [debug]: DHCP retry timeout for 'x-surf-100' has elapsed.

The transaction ID changes and the timestamps, but everything else remains the same. The repeat is ended a messages that is different:

"Fri sep 21 10:23:51 2018 [debug]: Address allocation request for 'x-surf-100' has timed out."

[Overmann]

I just managed a connection again. Spent a few minutes surfing (downloaded highgfx for my indivision, but when I tried to use highgfx screenmode my system crashed). After a cold reboot it didn't want to connect to the internet any more. Same issues as before. Could the 24 hour lease setting on my router have anything to do with it?

[kriz]

Try with MiamiDX instead ..

[Overmann]

Originally Posted by kriz

Try with MiamiDX instead ..

Ok, I've tried now. I remember using it years ago when I had a mediator setup. Nice program to use, but I had the same issues with MiamiDX as I do with Roadshow. It seems to be DNS-related.

Init reported both my DNS servers as unresponsive, and when time came to test a website it behaved the same.

EDIT: I tried using opendns now, after seeing that suggested elsewhere, but no luck. Same results.

[Overmann]

Is there a chance that there is something wrong with either my x-surf or the ZorroIV busboard? I just assumed that since it worked a couple of times then the hardware was fine.

[patrik]

Originally Posted by Overmann

I've enabled debug in x-surf-100 now, and the message that keeps repeating is:

Fri sep 21 10:23:51 2018 [debug]: Interface 'x-surf-100' hardware address = 00.00.00.00.00.00.
Fri sep 21 10:23:53 2018 [debug]: Setting up BOOTP packet for 'x-surf-100' with hardware address 00:00:00:00:00:00.
Fri sep 21 10:23:53 2018 [debug]: Sent initial DHCPDISCOVER request for 'x-surf-100'; transaction ID=0x1A5E2A68, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours."
Fri sep 21 10:23:58 2018 [debug]: DHCP retry timeout for 'x-surf-100' has elapsed.

The transaction ID changes and the timestamps, but everything else remains the same. The repeat is ended a messages that is different:

"Fri sep 21 10:23:51 2018 [debug]: Address allocation request for 'x-surf-100' has timed out."

Do you mean that you enabled debug for the x-surf-100 interface in Roadshow?

[patrik]

This is how it looks for me if I run with debug=yes and configure=dhcp in DEVS:NetInterfaces/X-Surf-100:
25-Okt-18 20:59:20 [Debug] Unknown Interface 'X-Surf-100' hardware address = 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:20 [Debug] Unknown Setting up BOOTP packet for 'X-Surf-100' with hardware address 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:20 [Debug] Unknown Sent initial DHCPDISCOVER request for 'X-Surf-100'; transaction ID=0x726FF515, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours.
25-Okt-18 20:59:24 [Debug] Unknown DHCP retry timeout for 'X-Surf-100' has elapsed.
25-Okt-18 20:59:24 [Debug] Unknown Setting up BOOTP packet for 'X-Surf-100' with hardware address 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:24 [Debug] Unknown Resent DHCPDISCOVER request for 'X-Surf-100'; transaction ID=0x3AF3361B, retry timeout=0:00:08 hours.
25-Okt-18 20:59:24 [Debug] Unknown Received BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Picking up BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Configuration information for 'X-Surf-100': Server identifier = 192.168.0.1.
25-Okt-18 20:59:24 [Debug] Unknown Setting up BOOTP packet for 'X-Surf-100' with hardware address 28:CD:4C:FF:FD:1E.
25-Okt-18 20:59:24 [Debug] Unknown Setting up DHCP packet for 'X-Surf-100' with transaction ID = 0x3AF3361B, server address = 192.168.0.1, client address = 192.168.0.30.
25-Okt-18 20:59:24 [Debug] Unknown Responding to DHCP offer; sent DHCPREQUEST request for 'X-Surf-100'; transaction ID=0x3AF3361B, retry timeout=0:00:03 hours.
25-Okt-18 20:59:24 [Debug] Unknown Received BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Picking up BOOTP/DHCP server message for 'X-Surf-100'.
25-Okt-18 20:59:24 [Debug] Unknown Server has responded to address allocation request for 'X-Surf-100'. Suggested IP address is 192.168.0.30.
25-Okt-18 20:59:24 [Debug] Unknown Checking if the IP address 192.168.0.30 proposed for 'X-Surf-100' is already in use.
25-Okt-18 20:59:24 [Debug] Unknown Configuration information for 'X-Surf-100': Server hardware address = 00:1B:21:81:1E:6C.
25-Okt-18 20:59:26 [Debug] Unknown IP address verification timeout for 'X-Surf-100' has elapsed.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Server identifier = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Address lease time = 0 day(s), 0:10:00 hour(s).
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Subnet mask = 255.255.255.0.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Router = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Domain name system server = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Domain name = "localnet".
25-Okt-18 20:59:26 [Debug] Unknown Binding address of 'X-Surf-100'.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Server identifier = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Configuration information for 'X-Surf-100': Server IP address = 192.168.0.1.
25-Okt-18 20:59:26 [Debug] Unknown Setting interface 'X-Surf-100' address to 192.168.0.30.
25-Okt-18 20:59:26 [Debug] Unknown Setting interface 'X-Surf-100' net mask to 255.255.255.0.
25-Okt-18 20:59:26 [Debug] Unknown Interface 'X-Surf-100' IP address is now set to 192.168.0.30/255.255.255.0.
25-Okt-18 20:59:27 [Debug] Unknown Interface 'X-Surf-100' address successfully changed to 192.168.0.30/255.255.255.0.


One thing that is very interesting is that your card reports the hardware address as 00:00:00:00:00:00, which is not correct, it should report an address starting with the Individual Computers OUI 28:cd:4c.

Have you tried xsurftest included in the driver archive? Should look like this:
7.Ram Disk:> xsurftest
X-Surf TestPrg V1.10 (Sep 12 2013)

Searching for X-Surf 10 (VEN_ID=4626, PROD_ID=23)
or X-Surf 100 (VEN_ID=4626, PROD_ID=100)....found X-Surf 100
found
Board address = 0x40000000
nic=40000c00
Searching for RTL8019 at 0x300...not found! (ID0=255, ID1=255)
Testing 16bit memory...ok!
Ethernet address = 28:cd:4c:ff:fd:1e
Chip is in jumper mode
Chip is using full-duplex mode
Chip is using IOBase something (0xf) and IRQ something (7)

IRQ / Loopback / cable connection test in progress:
IRQ received ok.
Packet send......via 100Mbit/s full duplex!


This should not be run when the interface is online.

On that note, which version of the driver are you using?