<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: A minor problem...
From: Robert Davidson <puttputt,AT,ebbs,DOT,com,DOT,au>
Date: Thu, 16 Aug 2001 19:14:29 +0200
In-reply-to: <Pine.LNX.4.21.0108160943460.2966-100000@raid.kaico.com>

> If you can't even ping a host on your own logical network
> (192.168.220.1/24 & 192.168.220.2/24 are on the same network) then it's
> not a routing problem.  Try flushing firewall rules.  They can screw stuff
> up sometimes.
> 
> Um... do you really have a private IP for your internet connection?  Is
> your ISP NATing you out?  Or... are you giving us bogus ip's to protect
> the innocent (which is fine too but makes it more difficult to
> troubleshoot)?
> 

Narh I'm not one to protect the innocent most of the time.  Not quite
that paranoid.

What I've got is cipcb0 on the isp side with an ip of 192.168.220.1,
and cipcb0 on my side with 192.168.220.2.  Over the VPN link I have
203.34.65.20/30 routed to me.  Cipe is using eth1 to communicate via
my cable modem to the other ISP's cable modem (cable is with
Optus@Home, but those bastards block port 25 and 80 (and some others),
so I am basically setting it up so that I can use some non-filtered
IP's for web and e-mail).

I didn't mind too much that port 25 has been blocked, but they have
blocked port 80 because of the Code Red worm.  Pitty linux users need
to suffer because of incompetent wanna-be sysadmins.  I wanted port 80
because I have a few personal websites and some other site I host for
a mate because she doesn't want to risk her internet account by
putting the website on their ISP's server (it's a dope (marijuana)
orientated website).

-- 
Regards,
Robert Davidson.
http://www.mlug.org.au/





<< | Thread Index | >> ]    [ << | Date Index | >> ]