AmigaOS 4.1 - network problems

Hi,

I have troubles with OS4.1 and my network.

When i boot from my OS4.0 partition i can always connect to the internet.

When i try to configurate the network in OS4.1 with network-prefs it hangs
afther i choose the eth3com.device. I have also tried to change to the older
(OS4.0) eth3com.device but the result is the same.

With the wizzard i have the same problem.

I had to reinstall OS4.1 because i had tried with the post-install to configurate
the network and when booting it hanged on the bootscreen, no way out.

Has something changed in OS4.1?

@Dirk-B

I made a fresh install of OS 4.1.

It seems I had the same problems as you.

The solution I found is :

First verify using your internet connection editor (in internet drawer) in the net interface (fourth tab) the name of your interface (mine is PPPoE).

Of course, it was the only thing I verified because I saved my preferences before the fresh install. So, if you have not made a backup, verify all the provider datas.

Second, in the internet prefs (in drawer prefs), click on net interface (first tab).

Choose as name the name of net interface (PPPoE here), the device (eth3com.device) and port 0.
I have a router so I clicked on static ip address (192.168.0.2 the same ip used in hosts tab).

At last, I verified the domain name servers ip.

I tried a couple of times because when I selected the eth3com, the soft didn't write ethernet in the line below.

Hope that this can be helpful.

Jesus

@yescop

Thanks, for your help.

I have retried to reconfigure my connection under OS4.0 and
i had no problems to connect true the eth3com.device.
Even the wizzard worked.

But when i try exact the same thing under OS4.1 the system
hangs when i choose the eth3com.device. I have even tried
to do the same thing as you.

In the morning i will try an other port on the router for OS4.1,
maybe that could solve the problem, but i am not sure.

My connection is: cabelmodem -> router -> connection via electric -> A1

@Dirk-B

An old thread on AW about setting up a net connection is here roadshow.

My static IP settings are in post #29.

@sundown

Thanks, for the link.

Well, i have set the ip-adresses but it stays the same because
i have to select the eth3com.device and it is then that OS4.1 hangs.

In the mean time i have commented the startup-line out via the boot-cd
and have removed the devs/netinterfaces and internet/connections afther
a configuration, so this way i do not have to do a new install of the OS.

I have also tried the older (OS4) internet-prefs but it is the same under
OS4.1, as soon as i select the eth3com.device a few seconds later the
system hangs.

Under OS4.0 all is working fine, even via an other router-port.

@Dirk-B

Did you try to do a format of your system disk and make a new fresh install ?
Just to make sure that you have no icompatibility between different versions of software.

If you want to post your configuration files, we could compare.

Interesting files should be :

internet/connections/file_name_of_your_connection

and hosts and route in devs/internet/tcp

@yescop

I have made a new partition and i have quick formatted it.
No old files on the partition. Then i have made a new install.

I can not give you working connections because then i have
to use the eth3com.device and OS4.1 hangs then. I can make
non-working ones, but those are useless anyway.

The only thing i can do is to use an OS4.0 connection, but then
again i uses the eth3com.device under OS4.1 and hangs. Here
are those settings that work fine under OS4.0:

device=eth3com.device
hardwaretype=Ethernet
configure=dhcp
id=telenet.be
mtu=0

I have no tcp in the devs/internet/ drawer.

Again, it's not the settings that are a problem, it is the
use of the eth3com.device that hangs OS4.1 from the
moment that i select it in the wizzard or the prefs.

@Dirk-B
The really fast solution to this is probably to copy over all your configuration files from your 4.0 installation: Everything in Devs:Internet and Devs:NetInterfaces. If you have special settings in your ENVARC:Roadshow/ directory, copy that complete directory as well. Then you *should* be up and running exactly like under 4.0, with no need to go through the wizard and Prefs editor again.

Of course, you won't know what the problem was, then (unless you make the effort of copying all the files one at a time and testing after each one).

Best regards,

Niels

@Dirk-B

I have understood well your problem.
When you select the device OS4.1 hangs.

I didn't have this problem but I noticed that there were some weird things with the soft.
For me it worked, when I restarted the prefs and selected ip static and no dhcp configuration.
After that and choosing eth3com, I had all the good port and messages.
And all was fine.

I don't know if this can be helpful. You have something strange things like me but with the usb.

Nbache has a good idea to test.

I made an error the tcp drawer is not in devs but in envarc:roadshow.

@nbache

Thanks, for your help.

The only file i have is in Devs/Interfaces, that's the one i
have copied over to OS4.1, normaly it should work, but it's not.

I have no settings for Roadshow in envarc/.

I even tried to make a connection with the ppp-ethernet device and
the wizzard (Roadshow?) said that it was not nessesairy to do that and
to go just to prefs/internet and make the connection there.

@yescop

Ok, this is what i have done. Under OS4.0 i have runned
ShowNetStatus and from there i could see the ip-address:
192.168.2.107 and mask: 255.255.255.0. Still under OS4.0
i have filled in these numbers under static and disabled dhcp.
Then i tried to make a connection but it failed for some reason.
I also tried other ip's like, 192.168.2.100, 192.168.2.1, etc.

Then i booted in OS4.1 and filled in this ip and mask and tried
to make a connection. Still no go as i suspected because i was
again using the eth3com.device to make the connection.
I even had to reset my cablemodem/routers afther that.

So, no matter what settings i use, it does not matter, it is the
start of the eth3com.device that stops OS4.1 from working.
I have a few seconds that it tries to connect and afther that
the mouse does not move anymore or with the booting up
(startup network comment on) it stays in the bootscreen.

So, there is something that has changed in OS4.1, but what
software that is changed, that i do not know. I have used the
OS4.0 internet-prefs, eth3com.device, and netinterface-file
but still no go under OS4.1.

I was looking for the Roadshow program but i could not
find it, instead i found in c/ roadshowcontrol and in
internet/ dialer. But both these have the same date from
2006 so they have not changed.

Are there any other programs related to roadshow?

Update:

Aha, i found the file ethernet_devices.db that was new
and much more smaller then the old one. I replaced it,
tried the connection again, but sadly it was not working. :(

@Dirk-B

Quote:
192.168.2.1 doesn't look like the IP of your router. Try this in a shell, type ping 192.168.2.1, if nothing happens, hit Ctrl-c & try ping 192.168.1.1. I'm guessing the last IP will fill your screen, if so, use that IP in your setup. I use 192.168.1.100 for my static IP of my A1.

In Prefs/Internet

Interfaces:
.name=Amiga
.driver=DEVS:Networks/eth3com.device
.type=Ethernet
.unit=0
.static IP on
.static IP=192.168.1.100
.mask=255.255.255.0
.DHCP off
.IP packet=default

Routes:
.gateway=192.168.1.1
Routes/New:
.type=Auto

Hosts:
.host=192.168.1.100

Name Resolution:
.name resolution=192.168.1.1


Roadshow is just a name for the A1 net interface, not a file or directory.

@sundown

This is what i got when typing "ping 192.168.2.1" in OS4.0:

PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=255 time=10.22 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=255 time=3.009 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=255 time=3.259 ms
etc...
--- 192.168.2.1 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 2.89/4.451/10.22 ms


"ping 192.168.1.1" gives 100% packet loss.


Ok, i have tried again in OS4.0 to make a static connection and
i succeeded, this is what my interface is:

device=eth3com.device
hardwaretype=Ethernet
address=192.168.2.101
netmask=255.255.255.0
mtu=0

The ping command worked also.


I am now again in OS4.1 and have connected with the same
settings, but again afther a few seconds my system hangs,
again true the use of the eth3com.device.

@Dirk-B

Quote:
Roadshow is just the collective name for all the modules making up or related to the TCP/IP stack. The main part of it is implemented in bsdsocket.library, which (unlike in Miami or AmiTCP/Genesis, where it s created on the fly) is a "real" disk-based library living in LIBS:. I believe it did change between 4.0 July update and 4.1, but I wouldn't expect that to create this sort of problems.

Quote:
That shouldn't have much significance. It is just a list of some known network card types and their features, like the number of devices on the unit. The only effect of that is to fill in some defaults when using the wizard and/or prefs program, AFAIK.

And the reason the new one is smaller? Look at the contents of the old one; it seems all the devices mentioned in there are from the ancient past where only classic hardware existed. It has stuff like the Ariadne and the X-Surf etc. And the version tag is dated in 2003 ...

The new one seems to mention only some devices likely to be used on an A1 -- which incidentally is the only one OS 4.1 is relevant for at this time.

Best regards,

Niels

@Dirk-B

Quote:
Just to make sure: Did you copy also all files from Devs:Internet over from 4.0 to 4.1 (files like groups, hosts, name_resolution, networks, ...), as well as the Devs:NetInterfaces/ contents? If it works under 4.0, and all files storing that setup are copied to 4.1, I can see no reasone for it not to work there also. I did exactly that numerous times during the test phase, on two different A1s.


Best regards,

Niels

@nbache

Thank you very much for the explanation.


Well, you never know, I will try and replace that library.

...

Ok, i replaced the libs and rebooted, but the result stays the same.

I have no idea anymore what it is that causes this problem.

It will be interesting to hear from others with an A1(SE) and
how it went with their connections with the internet.

@nbache

No i did not replace those, i will try it.

...

Ok, replaced those files, but the same result.

@Dirk-B

Quote:
Well, then I'm out of ideas, sorry.

You might want to find someone in your area who can help you on-site or something, there's got to be some setting or file somewhere you have accidentally screwed up, but I can't guess what it could be without actually sitting next to the machine and your LAN and going through it all systematically.

Best regards,

Niels

@nbache

I have booted from the OS4.1 CD and done a quick format of
the OS4.1 partition and did a new install of OS4.1.
Now i have no files or settings screwed up.
Checked in s/startup that the network line is commented out.

Reboot.

Done the post-install but scipped the network-installation, i
will do that myself.

Ok, my first test is with the internet-prefs: OS4.1 hangs a few
seconds after selecting the eth3comdevice.

Reboot.

My second test is with the wizzard: OS4.1 hangs a few seconds
after the dialer-requester that says "searching for ethernet adapters...".

Conclusion, it is when the eth3com.device is selected that
a few seconds later OS4.1 hangs. And it is not my fault.
I have a great working connection under OS4.0 so there is
no reason why it should not work under OS4.1, unless there
is something that has changed in OS4.1.

@Dirk-B

I am sorry but I don't have any idea to help you.
The only difference with me is that I have an A1XE G4.

If you can, test with an another router even if yours works under OS4.0.

I hope you will find something.