Inet 225 TCP/IP Internet Access Problem

[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"?

[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.

[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.

[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?

[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?

[kolla]

Also you seem to confuse the string ">0" as an input, with "a value greater than 0", so you end up with a lot of files named "0", containing the output from the command.

Inet:c/Route add net 192.168.1.1 >0

I suggest looking for those files named "0", located in whatever directory you run the command from, and delete them.

count - An integer that indicates whether the gateway is a remote
host or the local host. If the route leads to a destination via a remote
gateway, count should be a number greater than 0. If the route leads to
destination and the gateway is the local host, count should be 0. The
default for count is zero. The result is not defined if count is negative.

See? "count" can not be the string ">0", but it can foor example be the number 3.


As suggested above, the command to set default gw should be:

Inet:c/route add default 192.168.1.1

[kolla]

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.

No, your assumption is wrong, it is quite normal to be able to access the router on a LAN even when the route out is not configured, and especially so when NAT is attempted.

With IPv6 things happens much more automatically. For example, my provider in Norway (Canal Digital) provides (if I recall correctly) 3 /64 networks to my router which these days is just an Apple Airport Extreme. The Airport Extreme automatically sets up all the native IPv6 routing, using the 3 networks for 2 wireless networks and one for wire. I configured it from my phone and it works flawlessly out of the box. By setting up a NAT64 router and a bind9 installation with DNS64 enabled, I no longer need IPv4 and NAT on my LAN. For each legacy IPv4-only system (everything Amiga), things get more complicated. I must use 464XLAT, which enables them to connect to IPv4 services on Internet across my IPv6-only network. There is of yet no good generic solution for legacy IPv4-only clients to access IPv6-only services, though for web there are simple proxy options.

[kolla]

Yes,

And I would assume your NAT router also functions as DNS resolver, so setting nameserver to 192.168.1.1 should also work. I don't recall where Inet-225 sets this, but maybe it has a resolv.conf file somewhere? If so, setting "nameserver 192.168.1.1" in it should do the trick.

[kolla]

The only thing that strikes me as a bit odd in that routing output is

192.168.1.76 127.0.0.1 UH 0 0 lo0

[kolla]

If I was in this situation, at this stage, I would just change the settings marked 192.168.1.75 or similar to 192.168.1.1 , in the settings area listed in the file marked MISC.

That MISC is not a file, it is just the prompt of his shell, he appears to be standing in a volume called MISC: which corresponds to his DH1: device

What you see is the output of the command "netstat -rn" - netcat being a tool to show various.. network status, -r is "route" and "-n" is "do not resolve ip addresses and ports".

Because 192.168.1.1 is the local IP address for the machine that routes to the outside internet. 127.0.0.1 is the Amigas IP address, from the Amigas point of view.

That is correct. And 192.168.1.76 is the address of the amiga.

What the routing table shows seems quite normal:

127.0.0.1 127.0.0.1 UH 0 0 lo0

The localhost IP-address is routet to the loopback interface lo0

192.168.1.76 127.0.0.1 UH 0 0 lo0

This one is odd, I would have expected a

192.168.1.76 192.168.1.76 U 0 0 s0

But - back in the days, the TCP-stacks did a lot of weird things

The issue is, how? That should let the browser use the TCP/IP stack to access the internet, and the web.

Sure, but on still need DNS to know what addresses to connect to.

[kolla]

Does Inet-225 have a file named resolv.conf?

[kolla]

Surely there is some information on where you specify what nameserver to use?

[kolla]

Should be something about it in any of the prefs guides. Look for name server, or resolver, DNS...

[kolla]

Looks like it was more configured for dialup internet direct from an Amiga than network internet connection via remote network gateway.

Nothing in what you quote suggest that, and dial-up also requires routing tables, you know.

A little history lesson... once upon a time there was AS225, the official TCP stack from Commodore, which they made to use with the A2060 ARCNET card and the A2065 ethernet card. Not so much dialup. (ARCNET was at the time a standard competing with ethernet) In version 2 of AS225, AS225-r2, the concept of SANA2 was introduced - Standard Amiga Network Architecture 2 - meaning that the TCP stack did not need to support hardware directly, but could use device drivers, such as a2605.device etc. When CBM folded, AS225 was continued as INet-225 by a company called Interworks, to be sold with the Surfer pack provided by Amiga Technologies.

AS225 and INet 225 if I remember correctly uses "socket.library"
AmiTCP, Miami and Roadshow uses "bsdsocket.library"

This difference means that software has to be compiled against either one or the other, and if you look on Aminet, you will find that most software from the 90ies exists in two versions, one for AS225/INet225, and one for AmiTCP (the rest).

I know for a fact that I have used AS225 with A2065 card in A3000.
I know for a fact that I have used INet 225 with ICard PCMCIA ethernet card from IAM on A1200.
I also remember we (university computer club) inquired the university to sponsor a 10 node license for INet 225 at some point, which of course was rejected.

In the end, AmiTCP by became the standard, AmiTCP 3.0 beta 2 (http://aminet.net/package/comm/net/AmiTCP-bin-30b2), which was free (and AFAIK the basis of TCP stacks in AROS), and the commercial AmiTCP 4 (http://aminet.net/package/comm/tcp/AmiTCP-demo-40 that often was hacked) by our Finnish friends NSDi, which was later basis for Genesi and others, though with dubious licenses/copyright infringements. AmiTCP made it to version 4.2 (http://us4.aminet.net/aminet/docs/rview/AmiTCP4.2.txt)

Luckily there was also Holger Kruse, who in addition to making quite a few nifty software such as AmiWin (http://aminet.net/package/misc/x11/AmiWin222d) (an X11 implementation that totally rocked after the sources of black&white DaggeX (http://aminet.net/search?query=DaggeX) got lost in one infamous disk crash), made Miami and Miami Deluxe (Miami with support for multiple interface - use your Amiga as a router). He introduced an improved interface standard for Amiga networking hardware, called MNI - Miami Network Interface - which supported "modern things" that SANA2 does not, such as multicast, promiscuous mode (for tcpdump etc) and more. Sadly Miami was such a success that it was hacked and pirated to a point that Holges said bye-bye and left Amiga to persue happiness working with Carl Sassenrath on REBOL.

In addition to TCP/IP, there was also Envoy (http://de4.aminet.net/docs/rview/Envoy.txt), which would the equivalent of netbios or appletalk for Amiga, an "office" type networking protocol for sharing resources like disk and printers on a LAN. Later Envoy (3 and up) supported running along with a, or even on top of, a TCP stack.

Anyways, long story short (hehe), INet-225 should certainly work with ethernet.

AmTCP 4.1 or later recommened if you want full functionality. A3.X isn't that hot, apparently.

The big difference between 3 and 4 is the licensing model, AmiTCP 3 was GPL, 4 was commercial.