LinkBack Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #7  
Old 29-May-2009, 11:28 AM
Senior Member
 
Join Date: Aug 2008
Posts: 1,634
phxazcraig 0 reputation points
Default Re: filter problem

Personally, I would have done it this way:

VNC Cust1:
tcp
source: 1024-65535
dest. 9040
stateful/ack: none

VNC Cust1 resp
tcp
source: 9040
dest: 1024-65535
ack: enabled

Then I would have used VNC cust1 from private to public, adding either
source or destination IP addresses if I wanted to tie the traffic to
specific hosts.

Next I would use vnc cuts1 resp from public to private, usually not
tying to specific hosts (since the outbound was already doing that).

For inbound, I would add another pair, but in the reverse direction for
public/private and the IP addresses.

What you did should have worked though. I would carefully use filter
debug or pktscan to track down the problem traffic getting filtered to
see what is wrong. Offhand I'd say there must be another port involved.


Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***



Reply With Quote
 

Tags
filter, vnc

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -6. The time now is 04:39 AM.


© 2007 Novell, Inc. All Rights Reserved.

Search Engine Friendly URLs by vBSEO 3.3.0 RC2