Good news and new questions! :-D
Still with Modem -> Amiga I went through a fresh setup ( power down modem and all ).
Went through Miami Init, and all went about the same. Didn't know DNS, so I supplied it manually.
Got online and went to shell and I was able to ping domain names with no problem, like google.com and amiga.org . Anything at all.
Ah ha! I said, this stack is fully happy and probably was with the router scenario as well. There is something that the browsers I've tried don't like or 'know' as they are all unbearably out of date.
I found some evidence to support my crap browser theory. I found one page I could connect to:
http://www.cucug.org/I looked at the code you know, and it was just plain old HTML, starting off with tag and no . A few of the other pages there would load too, like the meetings page. They too were just straight HTML.
Most anything contemporary would not load. So my thought is the browsers don't like something in the code like you have so regularly these days, like amiga.org (would not load):
So, what say you? I was using Ibrowse 1.12, Voyager 1.0 and Ibrowse 2.4 (demo - could not change any settings). I think a newer or different browser could do better? Aweb any better? What do people use now?
DNS is solved but loading web pages is not... Thanks for your comments