Great Circle Associates Firewalls
(June 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: gauntlet firewalls (opnav)
From: MANVILLET @ N4 . OPNAV . NAVY . MIL (MANVILLE_TIM)
Date: Mon, 23 Jun 1997 07:58:12 -0400
To: firewalls @ greatcircle . com

     I'm new to the world of firewalls so please indulge me as I try to 
     sort something out.
     
     We have a TIS Gauntlet firewall.  I would like to build a plug gateway 
     to process lotus notes.  I understand that notes uses port 1352.  As I 
     monitor traffic I have noticed that, inside the firewall the source 
     port could be anything but the destination port is 1352.  The 
     destination port at this time is the address of the firewall.  If I 
     monitor traffic outside the firewall the response to a session 
     initiated inside the f/w being responded to by an outside machine with 
     have a random source port but a destination port (once again this 
     appears to be the firewall) of 1352.  Currently we have built packet 
     forwarding rules to allow notes traffic to pass through the firewall.  
     However if we built a plug gateway to listen on port 1352, I think we 
     would be able to do all that packet forwarding does and monitor the 
     traffic.
     
     Any comments on this would be greatly appreciated.
     
     Tim Manville
     manvillet @
 n4 .
 opnav .
 navy .
 mil


Follow-Ups:
Indexed By Date Previous: Re: Monitor unused ports
From: Julio Sanchez <jsanchez @ esegi . es>
Next: Re[2]: Class B Address
From: Karl Janice <"KJanice @ NYPP (Karl Janice)%NYPP"@mcimail.com>
Indexed By Thread Previous: Re: Monitor unused ports
From: Miguel Armas <kuko @ cic . teleco . ulpgc . es>
Next: Re: gauntlet firewalls (opnav)
From: "Gary D. Long" <kindred @ sound . net>

Google
 
Search Internet Search www.greatcircle.com