[Ma-linux] Using only the local "network"

DonJr djr1952 at hotpop.com
Sun Aug 26 15:48:40 EDT 2007


On Sun, 2007-08-26 at 14:50 -0400, Theodore Ruegsegger wrote:
> Donjr asks:
> > EXPLAIN more
> > Are you saying that:
> >    $ x-www-browser http://127.0.0.1/
> > doesn't work?
> 
> What I said was that attempting to open, in either firefox or
> konqueror, an http or https link to localhost didn't work. Now that
> you've taught me that I can do that from the command line using
> x-www-browser, I can add that that doesn't work either. It does open
> konqueror, which then times out with the same error.
> 
> > What is the ERROR message?
> 
>     An error occurred while loading http://127.0.0.1/:
>     Timeout on server
>     Connection was to 127.0.0.1 at port 80
> 
> > What happend when you try:
> >    $ x-www-browser http://127.0.0.1:631/
> >  {-: that's the http interface to CUPS. :-}
> 
> It opened a second konqueror window, saying:
> 
>     An error occurred while loading http://127.0.0.1:631/:
>     Timeout on server
>     Connection was to 127.0.0.1 at port 631

Something is broke about your "loopback" network

> > What do the following command return:
> >    $ netstat -tap

> It hangs until I add the n option:

What is in the file /etc/hosts ?

It should be something like:

 127.0.0.1       localhost.localdomain   localhost       lo

 # The following lines are desirable for IPv6 capable hosts
 ::1     ip6-localhost ip6-loopback
 fe00::0 ip6-localnet
 ff00::0 ip6-mcastprefix
 ff02::1 ip6-allnodes
 ff02::2 ip6-allrouters
 ff02::3 ip6-allhosts

> $ netstat -tapn
> (Not all processes could be identified, non-owned process info
>  will not be shown, you would have to be root to see it all.)
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State  
>     PID/Program name
> tcp        0      0 127.0.0.1:2208          0.0.0.0:*               LISTEN 
>     -
> tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN 

Something is listing to port 80 the web-server port

> tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN 

Something is also listing to port 631 the ipp port {print server}

> tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN 
>     -
> tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN 
>     -
> tcp        0      0 127.0.0.1:2207          0.0.0.0:*               LISTEN 
>     -
> tcp        0   1894 192.168.1.100:2677      72.14.205.19:80 
> ESTABLISHED11428/firefox-bin

Firefox is running and looking at http://72.14.205.19:80/* 
                                  { aka Google } 

> tcp        0      0 192.168.1.100:3659      20.137.248.23:1352 
> ESTABLISHED11403/c:\program fi
> tcp        0      0 192.168.1.100:5185      20.137.248.23:1352 
> ESTABLISHED11403/c:\program fi

What is "c:\program fi"?
I thought you was running Linux?

>tcp6       0      0 :::22                   :::*
LISTEN 

> 
> > Do you have a "Web Server" installed?
> 
> As I said, Apache2. Works fine when I have a network connection.
> 
> >  Is it RUNNING and configured to accept "local" connection?
> 
> Since the web server doesn't seem to be responding, I guess that's the
> crux. I couldn't find anything in the config files relating to "local"
> connections; if I've overlooked a setting, please advise! In any case,
> when I'm connected to a network, addressing it as localhost works
> fine. When I'm not, it fails as above.
> 
> When I plug the LAN cable back in and run "sudo /etc/init.d/networking
> restart", your two examples above work just fine, displaying the
> default page and the CUPS home page, respectively.

Interesting as "/etc/init.d/networking restart" should have no effect on
the loopback(127.0.0.1) interface. As it even filter out {or at least
tries to} any effect on that interface.

The command to RESTART the loopback interface is:
sudo  /etc/init.d/loopback stop && sudo  /etc/init.d/loopback start

{ The "restart" option/parameter is a do nothing "exit 0". 
  As it's not something you would normally ever really do. }

> Does any of that get us any further?
> 
> Hopefully, Ted

All of the above causes me to ask:
  What are the contents of /etc/network/interfaces ?

Mine is:
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
auto eth0

# The primary network interface
iface eth0 inet dhcp

------------------------------
What is in the file /etc/host.conf ?
mine is:
$ cat /etc/host.conf
order hosts,bind
multi on
----------------

In other words something LOW-LEVEL is mis-configured.

--  
-- 
 Don E. Groves, Jr. 

$ /usr/games/fortune : 
All I know is what the words know, and dead things, and that makes a
handsome little sum, with a beginning and a middle and an end, as in the
well-built phrase and the long sonata of the dead.
  -- Samuel Beckett




More information about the Ma-linux mailing list