3 Leg configuration issue.

Hello,



Can someone assist me with my configuration please. I am trying to run a 3
leg configuration with 2 Nic cards external interface behind an internal and
externally connected Pix. My 3 network segments are: Internal network (Nic
#2) 192.168.6.0/24 isolated DMZ segment, Perimeter Network 10.0.0.0/16
(internal production IP range no physical Nic) and DMZ (Nic#1) addresses
192.168.3.0/24. The DMZ Nic #1 configuration is 192.168.3.10 mask
255.255.255.0 DFGW 192.168.3.253. The Nic #2 interface 192.168.6.1 mask
255.255.255.0 no gateway 192.168.6.10 for DNS. The network range defined
as "Internal" is the 192.168.6.0/24 network. I can connect from any device
behind Nic # 2 to the perimeter or external networks. Devices from the
10.0.0.0 network "Can Not" access resources behind the ISA server Nic #2 the
192.168.6.x network. That is my issue. How do I or can I create a rule or
network set to allow source IP of 10.x.x.x to hit the External interface and
route through to objects on the 192.168.6.x network? To make this work will
I need a 3rd Nic and connect it to the 10.x.x.x network?



Regards,



Trevor.........


.

Relevant Pages

  • 3 leg configuration
    ... leg configuration with 2 Nic cards external interface behind an internal and ... My 3 network segments are: ... The network range defined as ...
    (microsoft.public.isa)
  • Re: Approaches of interprocess communication
    ... | Inter-process TCP/IP communication between two processes on the same | host invariably uses the loopback interface (network 127.0.0.0). ... | The transmit driver for the loopback interface receives a datagram from | the local network layer and immediately announces its reception back to ... However on Solaris I have observed local connections to an external interface actually increasing the packet count on the loopback, but I can't confirm whether those connections were to services specifically bound only to the external interface. ... Certainly on Windows XP there is a host-specific route via 127.0.0.1 to the external interfaces as well as the network route via the external interface. ...
    (comp.lang.python)
  • Re: IP Forwarding: Att: Mike Burger
    ... > I did the 'ip addr' command. ... The network topology goes like this: ... Note that my external interface, eth0 in my case, has 3 IPs. ...
    (RedHat)
  • Configuring VLAN in 6500 Switch
    ... IP address of the external interface. ... I would like to set up a "routable" VLAN... ... The network my external interface is on ... things this way as opposed to just configuring static NATs? ...
    (comp.dcom.sys.cisco)
  • Re: 5 interfaces, 2 gateways - routing issues
    ... just took over the task to administrate a corporate network and seems ... external interface, default gate ... (everything with non local destination gets nat and routed via fxp0) ... external interface (sis3) ...
    (comp.unix.bsd.openbsd.misc)
Loading