Inet 225 TCP/IP Internet Access Problem

[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

[Pat the Cat]

Can I ask a stupid question please?

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.

5.MISC{150-DH1}:> netstat -rn
Routing tables
Destination      Gateway            Flags     Refs     Use  Interface
127.0.0.1        127.0.0.1          UH          0        0  lo0
192.168.1.76     127.0.0.1          UH          0        0  lo0
default          192.168.1.1        UG          0        0  s0
default          192.168.1.76       U           0        0  s0
192.168.1        192.168.1.76       U           0        0  s0
5.MISC{150-DH1}:>    

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.

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

The stupid question is, am I on the right lines or completely off the mark? I did say I'm not very good with networks.

[Pat the Cat]

Thanks Kolla. I get it now. Something is a little odd with the netstat report, it's just a question of finding the right tool to change it.

is this an entry in my Host file or do I need to setup a DNS server ?

My guess is, you change it in the host file, as indicated by Kolla? You ARE already in the proces of trying to set up a DNS server?

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

[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

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

[Pat the Cat]

There is and never was anything called "AmiTCP Pro"

Clicky linky. That shows a product called AmiTCP pro. It has working functionality. Unlike Inet225. I appreciate it costs money. So does Roadshow. Roadshow is cheaper than AmiTCP Pro. Most people purchase on cost when functionality is not an issue.

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

Not as much text as an infinite number of monkeys, and one idea is, once you have identified a known issue, it is added to a pooled resource, and people can search for it.

Strikes me this forum depends on people being able to use Google, do all their own fault finding, never ask questions, and never, ever, use the Search button. Any Amiga issues, you're on your own to find the solution. Or at least, encouraged to find your own solution.

Looks like the OP was sent on a wild good chase. Ho hum. Nobodies fault really, and it's not like the thread was left hanging with zero attempt at helping.

Too many cooks maybe.

[Pat the Cat]

You seem to live under the false assumption that INet 225 does not work - newsflash: it works! Even on ethernet it works! I have used it! Have you? There is a lot of software for it too, that software also works. Amazing feces!!

Hey Pneron, you got this POS Inet 225 working or have you thrown it in the trash already?

Aminet sucks, because everybody hands out the POS free version. Come to that, Easynet sucks. For the same reason.

Does anybody else see a pattern here? No? Well, I'll give up. Hand over to the "experts" who "know what they're doing".

:laughing::laughing::laughing::laughing::laughing::laughing::laughing::laughing::laughing:

[Pat the Cat]

Thanks Kolla, I got it now, I think. Some Amiga TCP stacks use static addressing only, so they need to be told where to look for addresses "outside" the local network, like the internet.

Otherwise they just dumbly use the same default settings for accessing IP addresses off of the local network that the default settings use. You HAVE to tell them where to look such places up, one way or the other. Otherwise they just won't work as you expect.

Am I right? Or at least on the right lines here? This is where Roadshow clicks with people, because it prompts for the person setting up, about setting where the TCP stack needs to be set to lookup addresses, I guess. Manually configuring it will work with ANY AmiTCP stack, but if you assume dynamic addressing, you are in a world of pain with some Amiga TCP/IP distributions. Age is no guarantee of fitness for purpose for noob network engineers like me.  Even if the do have a GUI, most solutions don't guide you and prompt you to put in the right answers in the right places. They just assume you know about networks enough to give the TCP stack the right network routing to navigate to places, on local networks, or remote networks.