Inet 225 TCP/IP Internet Access Problem

[pneron]

Yes my router is pointing to DNS...will look at OpenDNS. thanks

[kolla]

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

[pneron]

Will check....

[pneron]

so far no Kolla...I am going through the docs and examples provided with Inet but do not see such a file?

[kolla]

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

[pneron]

will continue to look tonight when I am back home

Thanks

[pneron]

Hi Kolla

I can try and ZIP over the the original I-Net 225 sample DOCs (Amiga Guide Format) for your review if you think that will help?

Thanks

Philippe

[kolla]

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

[pneron]

Thanks...I will check for that...hopefully we are getting closer

[Pat the Cat]

Think I found something.

Amiga Side

On the Amiga side, using Amiga Explorer in TCP/IP  mode requires the original bsdsocket.library, or a compatible TCP/IP  library. The libraries provided by AmiTCP/IP version 4.x (released in  1994, and which became the reference for Amiga bsdsocket.library  functionality) or newer, Miami and WinUAE, for example, work fine. There  is a known issue in relation with the TCP/IP stack which was part of  the "Enlan-DFS" and "Inet-225" products, which, by design, included  limited compatibility with the bsdsocket.library, specifically to  support certain programs such as AmiPhone, but not to offer full  compatibility with the original library having the same name. Important  features used by Amiga Explorer, such as asynchronous socket events, are  missing in this library. Under these circumstances Amiga Explorer may  issue a "TCP/IP library cannot be opened" message and not function.

From;-


http://www.amigaforever.com/kb/14-109


Known TCP/IP stack problem with the inet-225, apparently. Library is borked to give any sort of functionality with that distro of AmiTCP. Looks like it was more configured for dialup internet direct from an Amiga than network internet connection via remote network gateway.

AmTCP 4.1 or later recommened if you want full functionality. A3.X isn't that hot, apparently. Earlier AmiTCP that is. Other TCP-IP stacks don't have this issue, or just better compatibility with a genuine bsdsocket,library.

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

[kolla]

Ah yes, I recall now that the major reason to run INet 225 was a certain piece of software not available for AmiTCP - namely NFSd - network file server daemon. This was also why we at the computer club asked the university to sponsor it, they were sold as 5 node licenses.

http://allanswers.org/hardware/amiga/networking-faq/part2-2.htm

Not something you would ever want to use over dial up

[Pat the Cat]

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



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

Yes, it works with ethernet, but it bugs out at the SANA-II stage, and doesn't work very well with browsers accessing the internet over a remote network gateway, it would seem.

Hence the use of a server daemon to get a result (and I wasn't too sure what was / is available for the Amiga in that respect, I must admit). An Amiga would not be my first choice for a server these days, but I was sure it was theoretically doable.

This is why AmiTCP today comes in a "Pro" version, I suppose. Proper license for bsdsocket.library, not some half ass hacked up library that barfs with proper protocols.

So, either use a different TCP-IP stack that is compatible, or pay up for a license. Or try and get the daemon working with the current setup (last one not what I would do, but...)

http://amigakit.leamancomputing.com/catalog/product_info.php?products_id=1183

[kolla]

How to say this... what you are writing makes very little sense to me

What do you mean "bugs out at the SANA-II stage", and "doesn't work very well with browsers" - first of all, we are not at a point yet where "browsers" are a thing, we are still just trying to get two basics working - default gateway and DNS.

What is this "server daemon" you speak of?

And no, your understanding of AmiTCP "Pro" and bsdsocket.library, "half ass hacked up library" etc is just bogus, sorry.

EDIT: ok - if there really is a bsdsocket.device in INet 225  (I can not recall that there is), then it most likely is "half ass hacked up". When you are using INet-225, you must in general use programs built for AS225/INet225, and not programs built for AmiTCP.

[Pat the Cat]

How to say this... what you are writing makes very little sense to me

What do you mean "bugs out at the SANA-II stage", and "doesn't work very well with browsers" - first of all, we are not at a point yet where "browsers" are a thing, we are still just trying to get two basics working - default gateway and DNS.

What is this "server daemon" you speak of?

What you just posted about - nfsd.

Ah yes, I recall now that the major reason to run  INet 225 was a certain piece of software not available for AmiTCP -  namely NFSd - network file server daemon. This was also why we at the  computer club asked the university to sponsor it,...

EDIT: ok - if there really is a bsdsocket.device in INet 225  (I can not recall that there is), then it most likely is "half ass hacked up". When you are using INet-225, you must in general use programs built for AS225/INet225, and not programs built for AmiTCP.

Aha, realization has dawned. AS225 is a working distro, in the sense of uncompromised, but isn't really guaranteed working with different network cards. Inet225 is a distinctly dodgy distro, from a network compatibility and remote gateway point of view. AmiTCP Pro is a real solution, but it's not the only possible solution and a bit of slog to get going.

What was that Roadthingy new release? Roadshow, sounds cheaper and more functional than AmiTCP Pro. And your original answer, so I guess we've just gone round in a big circle to come back to your first response.

[kolla]

What you just posted about - nfsd.

It was just a piece of software that wasn't available for AmiTCP, it came with the commercially available INet 225 - not that any _sane_ person would want to run NFS server on Amiga, for "inter-amiga" filesystems there was netfs, and for NFS client on Amiga there was ch_nfs. Later came Samba and SMBFS which Olsen still maintains today.

Aha, penny dropped. AS225 is a working distro, in the sense of uncompromised, but isn't really guaranteed working with different network cards.

Well, yes, but AS225r2 supports SANA-II, and works well with a whole range of cards, as well as you can expect a TCP stack from that time to work.

Inet225 is a distinctly dodgy distro, from a network compatibility and remote gateway point of view.

What? What are you basing this assumption on??

AmiTCP Pro is a real solution, but it's not the only possible solution and a bit of slog to get going.

There is and never was anything called "AmiTCP Pro", the name was "AmiTCP/IP v4.x" where "x" was a number between 0 and 2, and it was commercial after the guys who were working on AmiTCP, the so called "AmiTCP Group", mostly some guys from Finland, decided the work they put into it was too much to do it for free - it was a big hoopla at the time, going from GPL to commercial closed source, was considered... treason, by many. In the process I think bsdsocket.library also was updated to support more BSD 4.2 functionality.

What was that Roadthingy new release? Roadshow, sounds cheaper and more functional than AmiTCP Pro. And your original answer, so I guess we've just gone round in a big circle to come back to your first response.

Yeah. RoadShow 1.2 is supported and updated to this day, by the guy you see here posting under the name "olsen", who is a living legend in our community, and probably one of the nicest guys you will ever encounter here It is the TCP stack of OS4.1 as well.

For someone who appears to be living under a rock, you for sure produce a lot of text :laughing: