"Scott C. Best" wrote:
> Shea:
>
> So...just to be sure:
>
> > > ipchains -I 1 input -s 0.0.0.0/0 -d $IP_EXT/32 5900 -p tcp -j ACCEPT
> >
> > I tried adding the commands right after the FTP section of the firewall
> > script. Then I restarted the firewall. I then started the vncserver o
Shea:
Heya. Good progress. :) Some thoughts:
> I have vnc running successfully. I start the vncserver on box B, and
> then can log in w/ xvncviewer on B as well. I logged into my
> Firewall/Masq box and entered the last two commands. I tried to vnc
> to my ip C, today at work, but I di
"Scott C. Best" wrote:
> Shea:
> Heya. Fortunately, getting VNC running on your workstation
> is the difficult part. :)
> I wrote the echowall.lrp package for the LRP Linux distro,
> a firewall configuration script. Here are the commands you need to
> add to your firewall setup to
Shea:
Heya. Fortunately, getting VNC running on your workstation
is the difficult part. :)
I wrote the echowall.lrp package for the LRP Linux distro,
a firewall configuration script. Here are the commands you need to
add to your firewall setup to get VNC to work:
ipchains -A input
I would like to be able to vnc into my workstation with ip 'B'. The problem is that
my cable modem is connected to my other, old linux box, which is set up as a firewall
and ip-masq (running 2.2.18),
with internal ip 'A', and external ip of 'C'. My workstation then uses the old box as
a gate
