Wow. I didn't even know Crapintoshes could do NAT... But more to the point, can't you just block all outsiders from ports 5800-5999? Those are the ports VNC uses. Oh, and if you're on a Mac you can only use display 0 which would only use ports 5800(for the web service) and 5900(for the meat & potatoes)
On 25 Nov 2001 23:12:16 -0800, Isaac Wingfield wrote: > I'm running ChromiVNC on a Mac which is serving as a dual-NIC firewall -- > cable modem on one NIC, local network on the other, with IPNetRouter in > between. > > It is necessary for the "external" IP to be on the built-in NIC, and the > internal LAN on the other. Open Transport and IPNR require it that way. > > VNC persists in finding the internal NIC, and so the exposed IP and using > it. While that works alright, I do not want to risk the exposure of VNC to > the internet, but I cannot figure out how to tell it to use the "inside" > IP, which is in the 192.168.x.x space. > > thanks, Isaac > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
