nina wrote:Thank you all for replying.
Please ignore my reference to smxi- it's only where I want to go. Sorry for that red herring.
So. In pure console, not having started x; as root, from root directory:
I did: ping google.com
and lines displayed at intervals, ad infinitem, which began:
64 bytes from gw-in-f100.google.com (74.125.67.100);
And control-c let me back to my root prompt.
This means that you are able to send packets from your desktop through your router all the way to google and get replies from google again, so your Internet access looks like it's working. DNS lookups are also working. It is, of course, possible that there is a firewall that prevents you from talking to web servers on port 80 and that you have to use a proxy server. This firewall could potentially be at your ISP, but I think that's unlikely. It could also be on your router, but then you should probably know it's there 
Do you use a proxy server from your GUI browser? If so, put the same settings into elinks.
If you have netcat installed on your desktop machine, you could try:
echo -en "HEAD / HTTP/1.0\r\nHost: www.google.com\r\n\r\n" | nc www.google.com 80
to see if you can connect to Google's web site. That should output something like:
HTTP/1.0 200 OK
Cache-Control: private, max-age=0
Date: Thu, 28 May 2009 14:49:48 GMT
Expires: -1
Content-Type: text/html; charset=ISO-8859-1
Set-Cookie: PREF=ID=bcd1f930d8472cde:TM=1243522188:LM=1243522188:S=9f4L1222btBLc-Uj; expires=Sat, 28-May-2011 14:49:48 GMT; path=/; domain=.google.com
Server: gws
I it takes a long time and then prints out a "Connection timed out" message, then there's definitely something blocking port 80.
nina wrote:I then did: man elinks Yes, man elinks is there.
q put me back to root prompt. I then did: elinks It displayed.
I fed elinks the URL HTTP:/www.google.com , pressed enter, and a new screen displayed, showing only "Making connection" And nothing else happens.
Just in case that wasn't a typo, make sure you use a lowercase "http" and two slashes. i.e. http://www.google.com
nina wrote:At the top of the screen one can access menus: File, View, Link, etc.
But the connection isn't made.
I offered another URL: same result.
So to put this as politely as I can: why am I not connecting if not because my router's not letting me out because I'm not logged on?
Let me ask my question again
You don't need to log on to the router in order to browse from a GUI browser, right? So why should you when you try from the console?
nina wrote:Sidux (my OS) frowns on users going online as root. I haven't asked, but could there perhaps be a built-in prevention which one has to explicitely over-ride?
It's possible, I think, but highly improbable. You'd have to ask on the Sidux mailing lists/forums.
nina wrote:Thanks, all. Any patience left for further suggestions? This is all rocket surgery to me.
nina
My first guess, given what you've said in this message, is that you need to configure the proxy settings in elinks.