[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: woody browsers not working

This one time, at band camp, john gennard said:
> I'm still having problems with my woody installations.
> I've been trying to network three boxes at home, and think I may be making 
> progress. However, when I configure ppp and try to use Lynx or KDE's 
> Conqueror, neither will work. Previously these have worked 'out of the box'
> (i.e. with no intervention from me), now they just appear to try connecting 
> but do nothing.
> There has been a recent thread about similar problems, but apparently
> when using the 2.4 kernel (I'm using 2.2.20 at this stage).
> If I use wvdial, the logging shows:-
> -------------------
> [snip]
> --> Looks like a password prompt.
> --> Sending: (password)
> Auth successful[7f][03]@![01][01] [18][01][04][05]j[02][06]    
> [05][06][0e]e[14[12][07][02][08][02]~[7f]}#@!}!}"} }8}!}$}%j}"}&} } } } 
> }%}&[0e]e}4}2}'}"}(}"U=--> PPP negotiation detected.
> --> Starting pppd at Mon Sep  2 16:07:12 2002
> --> pid of pppd: 426
> ------------------
> ifconfig shows:-
> -----------------
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:  P-t-P:  Mask:
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10
>           RX bytes:217 (217.0 b)  TX bytes:208
> ----------------
> so I assume the ppp config is good and I am connected to my ISP
> (the 'clock' is definitely running).
> Why cannot I browse? I've looked at 'path' and 'permissions' and things
> seem correct. I can't find '/dev/ppp0', but that is the same on the boxes 
> still running Potato, so I assume it's normal.
> Obviously something is wrong, but I've no idea what - can someone please help 
> me out.

It sounds like you have a different issue than they did.  It appears
that ppp is actually working for you, but that either DNS or routing is

I am going to operate on the assumption (correct me if I'm wrong) That
what you have are three boxes, each with a NIC, connected to each other
through a hub or router, and one of them has a modem and gets an
internet connection which it then shares with the other two.

I'm probably going to cover some ground that you already have, but maybe
you'll get something new out of it.

Box 1 has the modem, Box 2 and 3 don't.  Box 2 and 3 should have
/etc/netwrok.interfaces something like:

auto eth0
iface eth0 inet static

Box 1 should have:

auto eth0
iface eth0 inet static

That sets up boxes 2 and 3 to use box 1 as their gateway, but doesn't
provide box 1 with a gateway.  ppp should take care of that on it's own,
so long as the gateway option is used in the config file (don't have a
box with a modem in front of me and can't remeber the exact file or
option name, sorry)  Once all that is done, try route -n on all three
machines.  On box 2 and 3, you should see something like:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface   U     0      0        0
eth0         UG    0      0        0

On box 1 you should see something like:

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface   U     0      0        0
eth1   U     0      0        0
ppp0  UG    0      0        0

If you don't, routing is not being set up - you may have to include a
'route add' command to ppp - man route for details and google for
examples, there are plenty.  

If you get something similar, try browsers on box 1 - do they work?  If
so, good, routing and DNS is taken care of.  If not, try ping (that's www.debian.org) - if that works, but name
resolution doesn't, it's a dns issues, and you have to look at
/etc/resolv.conf .  Once box 1 is set up for the outside, try pinging
the internal boxes, by IP address at first.  Hopefully that works -
otherwise you probably have cabling/router/NIC issues.  You can then add
their names and addresses to /etc/hosts so that you can communicate with
them by name.

Finally, go back to boxes 2 and 3.  They'll probably need manually
edited /etc/resolv.conf's, as they don't get updated by box 1's
dial-outs.  Try the above route command, and ping both by name and IP
address.  Does either work?  If the name fails, but the IP address
works, it's a DNS failure.  If both fail, but you can ping box 1, it's
a forwarding problem on box 1.  If you can't ping box 1, hardware.

Sorry to be so verbose and HTH,
A journey of a thousand miles starts under one's feet.
		-- Lao Tsu

Attachment: pgpMX5dtRig0G.pgp
Description: PGP signature

Reply to: