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

Subject: Re: A minor problem...
From: ewheeler,AT,kaico,DOT,com
Date: Thu, 16 Aug 2001 21:13:38 +0200
In-reply-to: <3B7BFD88.8373152A@ebbs.com.au>

Robert --
  What are your eth0,1,2,... ip's?  Which is the internet side one?

what are cipcb0 local & remote's ip and ptp ip's?  

--Eric

On Fri, 17 Aug 2001, Robert Davidson wrote:

> 
> > 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).
> 
> 





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