Roadshow and Ateonet

[MBry0]

Hi there,
I've been using MiamiDX for ages and just bought Roadshow for curiosity.
My A1200 has an ateobus ISA bridgeboard, and the NIC is an Ateonet, whom use tha ateonet.device driver (and a Blizzard 1260 if it could be an useful information).
I tried the A2065 configuration file, but can't get the ateonet to work.
I downloaded Roadie from aminet, when I try to connect I get some "unknown keyword" errors (screenshot attached).
I tried to browse the net, and the only thing I can do is open the aminet main page. Everything else gives me a netwrok error: no route to host.

In the A2065 configuration file I've setted ateonet.device as device, disabled dhcp, setted a fixed IP and netmask.
In the name_resolution dns file i've setted my router ip an the two google dns and "prefer static"

Roadie's "show net status" gives me the correct ip, the correct dns', but a "not configured" gateway. (screenshot attached)
"get network status" informations are in the attached screenshot.

I'm sure that is an easy fix, but my knowledge is the limit here.

[MBry0]

Nevermind... I've added the gateway, as soon as the new year's day hangover passed...
Now everything works as expected. Time to fine tune everything and make some tests.

[Thomas]

The driver ateonet.device belongs into Devs:Networks, not NetInterfaces. In NetInterfaces are only configuration files (text files). That's why you get those unknown keyword errors, because it is not readable text.

And normally you would not move and edit A2065, but you would copy it and name it Ateonet, then edit the copy. Just for consistency.

[MBry0]

Thanks for the reply. Done as you said, everuthing's fine.

[olsen]

Thanks for the reply. Done as you said, everuthing's fine.

Yikes. Just when I finally returned from the holidays and added a new network configuration file. Sorry!

Here is how the new AteoNet configuration file (which goes into DEVS:NetInterfaces) looks like:

# $VER: AteoNet 1.1 (9.1.2023)
#
# Configuration for the AteoNet 3 ethernet card, by Atéo Concepts

# The device name is mandatory
device=ateonet.device

# If not provided, unit number 0 will be used. You may
# have to change this if there are multiple cards of the
# same type installed in your machine, or if your network
# hardware supports several independent connections
#unit=0

# You must either pick a fixed (static) IPv4 address and
# a corresponding subnet mask, or request DHCP (dynamic)
# network address configuration.
# You can combine address/netmask/dhcp, which has the effect
# of asking the DHCP server to assign the requested IPv4
# address and subnet mask to this interface, if possible.
#address=192.168.0.1
#netmask=255.255.255.0
configure=dhcp

# If no DHCP server is present in your network, you can
# use automatic interface IPv4 address assignment through
# the ZeroConf protocol. Note that this will not set up
# default route and DNS servers for you, only the interface
# address is configured.
#configure=auto

# This variant of automatic IPv4 address assignment should
# be used in a wireless network instead of 'configure=auto'
#configure=fastauto

# You can enable diagnostic messages which can be helpful in
# tracking down configuration errors.
#debug=yes

# You can choose how much memory will be used when handling
# incoming and outgoing network traffic for this device.
# The default is to reserve 32 buffers of 1500 byte each, both
# inbound and outbound traffic. Larger values may provide
# better performance.
#iprequests=32
#writerequests=32

# For diagnostic and monitoring purposes it can be helpful to
# capture network traffic that flows through this interface.
# To enable this option, select one of filter=local,
# filter=ipandarp or filter=everything
#filter=local
#filter=ipandarp
#filter=everything

# This option disables a workaround required for the Ariadne
# network hardware, which, if enabled, would otherwise cause
# the interface setup procedure to take longer than really
# necessary.
requiresinitdelay=no

[MBry0]

Just copy-pasted on my amiga, works as expected. Thank you!

I'm facing a strange problem (not related to the configuration file), but I can't tell if it's whdload or roadshow. I've submitted the problem on whdload bug tracker a week ago, and I'm waiting for a response.

I configured the whdload startup, cleanup and prefs as they should. Everything works as expected, no crash or freeze, but it takes something like 2 minutes for the whdload splash screen to appear. During this time I can surf the net or upload/download files via ftpto my pc, so I think that roadshow works fine... The very same issue happens on my friend"s amiga 3000 with a pcmcia network card and roadshow, so I think that is not hw related...