FW: [sclug] TCP/IP I think

[tim]

I already have the connection working under Windows, and it has automatic
allocation of the required DNS. The Distro I am using is Mandrake 9,
previous versions of Red Hat and Mandrake I have had no problems with. I
seem to recall that I had the same problem with this Mandrake in the UK when
I had broadband, which I guess implies a setting I have misconfigured on the
Linux itself.

This is the netstat output on Windows if it helps

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    elysia:3067            baym-cs142.msgr.hotmail.com:1863
ESTABLISHED
  TCP    elysia:3100            64.14.122.242:http     CLOSE_WAIT
  TCP    elysia:3102            rad.msn.com:http       CLOSE_WAIT
  TCP    elysia:3103            unknown.Level3.net:http  CLOSE_WAIT
  TCP    elysia:3119            host-213-131-64-229.link.net:pop3  TIME_WAIT
  TCP    elysia:3121            host-213-131-64-229.link.net:pop3  TIME_WAIT
  TCP    elysia:3006            localhost:3118         TIME_WAIT
  TCP    elysia:3006            localhost:3120         TIME_WAIT
  TCP    elysia:3013            localhost:3306         ESTABLISHED
  TCP    elysia:3306            localhost:3013         ESTABLISHED

-----Original Message-----
From: sclug-bounces at sclug.org.uk [mailto:sclug-bounces at sclug.org.uk]On
Behalf Of Alex Butcher
Sent: 27 July 2004 02:13
Cc: sclug at sclug.org.uk
Subject: Re: FW: [sclug] TCP/IP I think


On Mon, 26 Jul 2004, Simon Huggins wrote:

> On Mon, Jul 26, 2004 at 09:52:41PM +0100, Alex Butcher wrote:
> > On Mon, 26 Jul 2004, tim wrote:
> > > Pinging the other end of the P-t-P connection gives me responses
> > > varying from 139ms to 159ms.
> > > Pinging the 193 address gives me Destination Host Unreachable.
> > OK, so it's almost certainly just DNS that's the problem. What distro
> > are you using?
>
> Not really.  Whilst DNS isn't working, it looks like pings to the
> outside world are blocked in any case.

So? Plenty of opportunity for firewalls...

> 172.18.30.whatever it was is part of the private non-routable IP space
> 172.16/12 too so there may be some magical gateway/proxy gubbins
> somewhere.

...especially seeing as the clients are being handed out RFC1918 addresses
(indicating that NAT or proxying is probably being done by the ISP - perhaps
to comply with local Egyptian censorship laws).

The more I think about this, Tim, the more I think you'll be best off
getting dialup working under Windows first and then using the same settings
for Linux (or looking for some local docs that detail how to get Linux
working with your ISP).