|
Posted by sintral on July 25, 2008, 4:33 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> sintral wrote:
>
> The below statements are what you have in place
>
> > conduit permit tcp host 68.16.146.91 eq www any
> > conduit permit tcp host 68.16.146.91 eq 444 any
> > conduit permit tcp host 68.16.146.91 eq 81 any
> > conduit permit tcp host 68.16.146.91 eq https any
> > conduit permit tcp host 68.16.146.91 eq ssh any
> > conduit permit tcp host 68.16.146.91 eq telnet any
> > conduit permit tcp host 68.16.146.91 eq ftp any
> > conduit permit tcp host 68.16.146.91 eq smtp any
> > conduit permit tcp host 68.16.146.91 eq pop3 any
> > conduit permit tcp host 68.16.146.91 eq 32000 any
>
> You already have POP access:
>
> +OK mail.fergusoncopeland.com IceWarp 9.1.0 POP3 Fri, 25 Jul 2008
> 15:41:35 -04
>
> and ftp
>
> U:\>ftp
> ftp> open
> To 68.16.146.91
> Connected to 68.16.146.91.
> 530 Connection refused, unknown IP address.
> User (68.16.146.91:(none)):
>
> To get IMAP add:
>
> conduit permit tcp host 68.16.146.91 eq 143 any
>
> =A0> 3. Very soon our website is going to be outsourced. I assume this wi=
ll
> =A0> mean two changes on our part: change the DNS entry to point to the
> =A0> third party hosting server and remove the firewall entry that routes
> =A0> traffic to 10.6.18.179.
>
> No, you only want to remove the conduit entries that equal http/https
Also, it seems like somewhere in my firewall configuration there would
need to be rules saying "accept traffic on port 21 and send it to
10.6.18.10" and "accept traffic on port 143 and send it to
10.6.18.179".
|