Re: woody browsers not working
On Monday 02 September 2002 17:23, Stephen Gran wrote:
[snip]
> > 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 failing.
>
> 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 think your detailed response shows me where I have gone wrong.
However, things are more complicated than you assume and I now
wonder if I will be able to accomplish all I want to do.
Briefly, I'm in my 70's and have medical problems, so originally I
had one box in the bedroom (complete with modem, printer, CDRW and
so forth) and another in the lounge also with modem, printer etc.
giving me 'full facilities' wherever I was. Following upgrades I
built a third box intending to use this for a firewall (I even have
a modem for that).
I obtained a hub, cabling, NIC cards etc intending to have a 'cosy'
little network. A neighbour, living in the flat above saw the bits
and pieces and said he had ADSL which I was welcome to use (ideal for
heavy downloads eg kernels) so I cabled to his network (box and
laptop).
Initially he ran Windows, so I installed W98 and we exchange photo
editing, music data etc and also have a networked printer. I use the
ADSL when beneficial. He has now been converted to include Linux, he
won't go yet to Debian, but Mandrake will do for a start.
So far I've put Woody on only two boxes (bedroom and lounge), and I
wanted each to have modem access to my ISP and in due course to be
able to access the ADSL. This way I don't always have to bring the
network up if I'm likely to be restricted to one room. In this case,
I assume I'll need more than one gateway.
Paul Condon suggested using 192.168.1.x - this is what I have planned
(I've laid out my scheme to use .4, .5 and .6 for the three boxes -
I'd like to suggest I was being clever, but it was just so that I
could leave 192.168.0.x for my neighbour).
Routing for both boxes excludes the ppp0 entry, so this must be the
problem taking each box in isolation. I shall try to get one working
tomorrow. Then I shall have to see how to proceed from there.
If you have any advice overall on what I said above, I shall be very
grateful. What you have communicated so far has been a very great
help in understanding. Very many thanks and regards, john.
> 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
> address 192.168.0.2
> netmask 255.255.255.0
> gateway 192.168.0.1
>
> Box 1 should have:
>
> auto eth0
> iface eth0 inet static
> address 192.168.0.1
> netmask 255.255.255.0
> network 192.168.0.0
> broadcast 192.168.0.255
>
> 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
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
> 0 eth0
>
> On box 1 you should see something like:
>
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth1
> 217.158.116.89 0.0.0.0 255.255.255.0 U 0 0
> 0 ppp0
> 0.0.0.0 0.0.0.0 217.158.114.40 UG 0 0
> 0 ppp0
>
>
> 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 192.25.206.10 (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,
> Steve
Reply to: