Inet 225 TCP/IP Internet Access Problem

[pneron]

SPECS:
======
Amiga 2000
OS 3.9 (a new install ---still working my way through the new features!)

TCP/IP Stack & Software
================
Inet 225 - TCP/IP Stack
Aweb 3.3 Browser
Amiganet NIC card - (Hydra Systems) + Hydra.device ver 1.44 (latest network protocol)
==============================================

Dear Amiga SMEs:

I just finished getting OS3.9 installed and having issues connecting to the internet with my old Amiganet NIC card + Inet 225 stack from "InterWorks:
I use to have access to the Web, but at that time I was using dialup PPP connected to my modem directly.

My home network has a bunch of PC's, Macs, etc connected to a Netgear router (gateway 192.1681.1). I can ping my router from my Amiga and I can even login via Amiga's browser AWeb  and get access to Netgear's admin control panel. However, I cannot get access to the internet. I suspect I am having gateway routing or hosting issues, but not sure. I have copied the Inet 225 Network initialization file below, along with a "Ping" test from my Amiga to my router and my host file.  I did add the Gateway address to one of my init files, but still not convinced if this card support such LAN setup.

Any thoughts on what I can do before I buy a new card ? :confused:



Inet 225 Amiga Outputs
===============

´´ I-Net 225 © 1995,1996 by Interworks ' '
Network startup has begun.
Configuring Hostname: amiga2000
Configuring for User: batman
Adding default gateway route.
add net default: gateway 192.168.1.1
Adding 'shortcut' route to localhost.
add host amiga2000: gateway localhost
Starting INetd.
Starting PortMapper.
Network startup complete.
Running 'INet:s/StartINet-After'...


Ping Test to Netgear Router
=======================
6.MISC{150-DH1}:NetWking/Inet225/Inet/c> ping 192.168.1.1
192.168.1.1 is alive!
6.MISC{150-DH1}:NetWking/Inet225/Inet/c>


Host File:
=========
127.0.0.1 localhost
192.168.1.76 amiga2000

[kolla]

You should really look into trying a different TCP/IP stack before you run off buying a new card! For example Roadshow.

It looks to  me that you lack default gateway. Do you have a "route" command? Or "netstat"?

[pneron]

Thanks Kolla...I do have a route command in my C dir

[pneron]

correction,  NETSTAT is there but does not see anything beyond anything local. I don't *think* Inet-225 can be configured for a Gateway config across Ethernet but I am no expert and might be wrong. I followed the examples in the doc with no luck.

 I am also in the process of upgrading OS3.9 and thought it had a free stack?

[kolla]

Well... the "route" command is typically used to set default gateway.

Something along the lines of

route add default gateway 192.168.1.1

You should be able to use netstat to see what is already configured as default gateway:

netstat -rn

[kolla]

I am also in the process of upgrading OS3.9 and thought it had a free stack?

Yeah, it comes with Genesis, which in all essence is AmiTCP with a GUI.

[Oldsmobile_Mike]

Genesis is fine, but AFAIR it does not support DHCP (someone feel free to correct me if I'm wrong). Many here will recommend Roadshow, if you can get past its lack of GUI there's a free time-limited (30 minutes) trial available. Maybe give that a try?

Personally I still use MiamiDX, even though it's slower and the author has completely abandoned it, I'm a sucker for its interface.

[pneron]

OK, thanks, I will try that tonight and check the dumps

Also, I did see some notes in the documentation that indicated that I-Net 225 can connect using SLIP, CSLIP or PPP (which I use to use during my dialup days) so perhaps it can only support Ethernet connection to LAN?

[kolla]

No, it connects just fine to the outside world too if configured correctly. But I would _really_ suggest using something else, such as the much mentioned Roadshow.

[pneron]

Thank for the advice Kolla, I am looking at both new stacks right now, one from OS3.9 Genesis and Roadshow.

Still not sure if these will work with my Amiganet (Hydra) NIC card but will try. In the meantime, here are some important docs for reviews:

As shown in docs it looks like the only way I can get access to the internet is via SLIP, CSLIP or PPP configuration.
and the Example they provided is for Ethernet to LAN only?
When I follow this setup (with my Gate pointing to router my 192.168.1.1), I get the following errors:

StartInet with Gateway Added
=========================
´´ I-Net 225 © 1995,1996 by Interworks ªª
Network startup has begun.
Configuring Hostname: amiga2000
Configuring for User: batman
Adding point-to-point route.
ifconfig: ioctl (SIOCSIFDSTADDR): Invalid argument supplied
inet:c/ifconfig failed returncode 10
Network problem: could not configure SANA II device.
Is the device installed properly?

It also looks like it wants to bind a PPP protocol on startup?
I have tried to use a ROUTE file in my db directory and with no luck.
Thus, based on docs, doesn't this indicate no internet access without using SLIP, CSLIP or PPP?


Output Files Below: (no error but no gateway)

StartInet with NoGateway Added
=========================
´´ I-Net 225 © 1995,1996 by Interworks ªª
Network startup has begun.
Configuring Hostname: Configuring for User: Adding default gateway route.
add net default: gateway amiga2000
Adding 'shortcut' route to localhost.
add host amiga2000: gateway localhost
Starting INetd.
Starting PortMapper.
Network startup complete.



OUTPUT FILES WITH GATEWAY OPTIONS
=============================


Init.prefs file
===========
SERVERS
activate "s0" DEFROUTE HOSTNAME amiga2000 IP 192.168.1.76 GATEWAY 192.168.1.1 DEVICE Devs:Networks/hydra.device UNIT 0 IPTYPE 2048 ARPTYPE 2054

StartInet with Gateway Added
=========================
´´ I-Net 225 © 1995,1996 by Interworks ªª
Network startup has begun.
Configuring Hostname: amiga2000
Configuring for User: batman
Adding point-to-point route.
ifconfig: ioctl (SIOCSIFDSTADDR): Invalid argument supplied
inet:c/ifconfig failed returncode 10
Network problem: could not configure SANA II device.
Is the device installed properly?

Hosts File
=========
127.0.0.1 localhost
192.168.1.76 amiga2000

Config File
=========
Hostname amiga2000
User batman
MailDir Inet:Mail
MailEditor Ed
SMTPMailDir INet:Mail/
SMTPSpoolDir INet:MailSpool/
SMTPRmail INet:c/SMTPpost -r
SMTPRoute mx,smtp,smarterhost

NetStat
=======
Routing tables
Destination      Gateway            Flags     Refs     Use  Interface
127.0.0.1        127.0.0.1          UH          0        0  lo0
192.168.1        192.168.1.76       U           0        0  s0



Routes File
==========
; Add NEtgear Router Info
Inet:c/Route add net 192.168.1.1 >0

[kolla]

Well, I used to have AS225 online via ethernet, and Inet-225 is its succeeder, so for sure it works, given that you have the SANA2 device driver for the Hydra.

Adding point-to-point route.
ifconfig: ioctl (SIOCSIFDSTADDR): Invalid argument supplied
inet:c/ifconfig failed returncode 10
Network problem: could not configure SANA II device.
Is the device installed properly?

Well - is it? Do you have Devs:Networks/hydra.device there?

Also...

Inet:c/Route add net 192.168.1.1 >0

... will write output to a file named 0 - is that what you want? Or was your plan maybe >NIL: ?
Anyhow, maybe you would want to see the output till you get things working?

[pneron]

yes.....the driver is configured correctly (as per message below):

StartInet with NoGateway Added
=========================
´´ I-Net 225 © 1995,1996 by Interworks ªª
Network startup has begun.
Configuring Hostname: Configuring for User: Adding default gateway route.
add net default: gateway amiga2000
Adding 'shortcut' route to localhost.
add host amiga2000: gateway localhost
Starting INetd.
Starting PortMapper.
Network startup complete.



I only get this message when I try and add the "GATEWAY" option.

As for the ROUTE command, I believe that is the correct syntax for remote gateway switch (">") but will double check the syntax again to make sure

[kolla]

I got the impression that you manage to ping 192.168.1.1, so what happens if you try to set the route manually?

[pneron]

Nothing if I add it as line in my ROUTE file. I will double check the "syntax" tonight when I get home but here is the GUIDE for the ROUTE (will upload a clean version)

[Pat the Cat]

Trouble shooting network issues is not my speciality. All comments on having a compatible TCIP/IP stack are totally valid.

But, it does strike me that, if the networked Amiga can look at the router, and even access the admin panel for it over the network, then the network side of it isn't the issue.

I suspect it might be the browser - you can get an update to Aweb from the developers here (it's still very old, but more recent than the one you have).

One big change in the meantime was the shift from IPV4 to IPV6. And that might be where the problem lies.

http://www.amitrix.com/aweb.html

You can get a slightly easier to install, none official version here for 3.X and PPC friendly 4.0 and MorphOS;-

http://www.greyhound-data.com/gunnar/aweb/index.htm?page=downloads

EDIT: Came across this thread. Apparently, you have to add the device (hydra.device) to AmiTCP or it defaults to using the serial port rather than the network card. The line is

eth dev=devs:networks/your.device

From;-

http://eab.abime.net/showthread.php?t=55734