Inet 225 TCP/IP Internet Access Problem

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

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

[kolla]

Clicky linky. That shows a product called AmiTCP pro.

You mean EasyNet Pro?

It is one of those "spin-offs" of AmiTCP, pretty much a GUI for AmiTCP v4.x

It has working functionality. Unlike Inet225.

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!!

Roadshow is cheaper than AmiTCP Pro.

Again I suspect you confuse with EasyNet Pro.

Most people purchase on cost when functionality is not an issue.

I bought Roadshow on a whim because I was trying to help someone out and got tired of the time-outs of the demo. As it turns out, the PPP implementation was much better than anything else, so I have kept using it on the systems where I use null-modem for connectivity (which is the MIST with serial link to pi zero, and the cd32/SX32 Pro with bluetooth null-modem against a Minimac G4 running Linux). I also have it installed on one A600 and an A1200 I believe.

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.

Provided that the information given is correct!

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.

No wild goose chase - with the system described he should be perfectly able to connect to the Internet using his ethernet card. Despite everything you have written :p

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

[kolla]

Aminet sucks, because everybody hands out the POS free version.

What on earth is that supposed to mean?

[kolla]

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

The guide you should be looking in, is perhaps the one for configinet

Is Domain Name Resolution available with the AS225 software?
...
For As225r2: Yes. All variants support DNS, and gateway. These functions are turned off and on via the config files and the ConfigINet utility.

http://www.faqs.org/faqs/amiga/networking-faq/part1/

[pneron]

***still working on this*** guys . Thanks for some direction/guidance.

My hope is that I will have some new updates later this weekend once I review the docs and links

[cha05e90]

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.

Yep - usually 225 would provide it's functionality via "socket.library". There was a "bsdsocket.library" wrapper for that to enable "socket.library" unaware software like YAM 1.x. I used that a lot and it usually worked out of the box. I remember I had to hex edit this or that binary ('cos they did a version test on bsdsocket or the like...), but in general it worked.

[kolla]

From the guides, how to use and set up DNS resolvers - should be selv explanitary?





It is really no different than any other TCP stack for Amiga in this regard.

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

[pneron]

Thank Kolla...I will give this shot, appreciate the screen shots

[pneron]

still working on this issue Kolla - thanks

[pneron]

thank you for the screen shots Kolla

[kolla]

You are welcome, interesting if it works out

And if not, I recommend the Roadshow stack.

[TCMSLP]

You are welcome, interesting if it works out

And if not, I recommend the Roadshow stack.

Wow, there's a whole heap of confusion here.  I'm not familiar with INet but you seemed to have almost a working config from the outset.  You could ping local machines and the router.  You just need to make sure the default route/gateway is pointing at your router (192.168.1.1) and also confirm you're pointing at the correct DNS server (also likely 192.168.1.1).  

If you try to 'ping google.com' from the CLI, this will test if name resolution is working.  It will also confirm if you're using the correct gateway.  If that fails 'unknown host' then DNS is not configured properly, if it resolves the name to IP but the ping fails then it's likely an incorrect default route.

Steve
p.s. As others have mentioned AmiTCP, I wrote an install guide here: http://blog.netting.org.uk/2015/07/19/amitcp-and-configuration-of-cnet-device/

[kolla]

Yeah, from reading the INet manuals, I can tell that it is a little bit of an oddball compared to what we are used to these days, it is really like using a _very_ old BSD