We Have two PC's here, so 3 interfaces (please excuse the crude
Representation
Linux Router
This machine can connect now right?
it can ping metalab.unc.edu?
so you need to enable IPchains so that it acts as a gateway to the internal
network
Try using this (direct from IP Masq HOWTO)
Well aparently Metalab is down at the molment, or my proxy here is being
silly again, but the command your looking for will be sitting in the IP MASQ
HOWTO it's good reading anyway! :)
Linux Workstation
also will need the resolv.conf set up for nameservers
route add default -gw 1.2.3.4 metric 1 (the Local IP address for the
Router goes here)
> -----Original Message-----
> From: Chris Job [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, January 25, 2000 2:10 PM
> To: 'Ray Olszewski'
> Cc: [EMAIL PROTECTED]
> Subject: RE: Can't surf the web
>
> Thanks Ray
> You were on the mark with your info. I called my ISP and asked what I
> would need to surf the web. He said that two (primary and secondary) IP
> addresses he gave me (I added these to my /etc/resolv.conf) was all I
> needed. That as much as he could help me with.
>
> Question: In the "route add default ..." command you gave me, should I
> replace the 1.2.3.4 with one of the 2 IP addresses the ISP gave me?
>
> Thanks
>
> -----Original Message-----
> From: Ray Olszewski [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 25, 2000 1:34 PM
> To: Chris Job
> Cc: [EMAIL PROTECTED]
> Subject: Re: Can't surf the web
>
>
> I've added linux-newbie back to this exchange; these queries really
> belong
> on the list, not private.
>
> Once again, you don't give us much to work with, so all I really can do
> is
> guess. See if I have the next part right.
>
> 1. You send outgoing mail via SMTP to a smarthost relay run by your ISP.
>
> 2. You receive e-mail via POP3 or IMAP (probably using fetchmail on
> Linux),
> again from a host at your ISP.
>
> 3. Your DNS is also provided by your ISP, anf you have its nameservers
> in
> /etc/resolv.conf .
>
> These three things share one common feature: they all require access
> ONLY to
> your ISP's internal network. Web access, however, requires you to be
> able to
> connect to sites outside your ISP's internal network. Based on that,
> I'll
> guess that you don't have your ISP's default route (gateway) in your
> routing
> table.
>
> I assume the ISP gave you the IP address of its default gateway. (If
> not, it
> might be coming in as part of a dhcp lease.) Check your routing table
> with
> "route -n" and see if it is included. If not, add it with the line
>
> route add default -gw 1.2.3.4 metric 1
>
> replacing 1.2.3.4 with the actual IP address.
>
> If I've guessed wrong ... sorry. Chris, I'm sure it seems tiresome to
> have
> to include your setup information every time you post, but please
> consider
> it from my (and probably Richard's) perspective. I reply to a lot of
> questions (on this list and others), and all the setups blur in my mind.
> If
> you don't remind me of your specifics, I can't pick them out from the
> dozen
> or so other sets of specifics I've read in the past few days.
>
>
>
> At 01:27 PM 1/25/00 -0500, Chris Job wrote:
> >hanks guys!!
> >I got my email working again!! If only I could figure out web I can
> not
> >surf the web I'll be okay.... When I enter a URL I comes back with the
> >message: no response server could be down. Try later.
> >Any idea on how I should proceed?
> >
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
