Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 17 replies
  • Subscribers 2 subscribers
  • Views 35620 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't access device behind RED

dhd
Hi I have a site setup with the following setup

Internal>ASG120Cluster->WAN->Router serving DHCP>RED10>Cisco>Client PC's

My RED is in standard unified mode and has an interface 172.16.250.1/29 serving DHCP on 172.16.250.4-6
The RED is 172.16.250.1 the Cisco WAN side is 172.16.250.2 

The Cisco can ping external addresses on my ASG Cluster as can client PC's

however I can't ping the Cisco or client pc's from the ASG or anything inside it.  I can ping my RED address however.

Firewall rules are Trusted networks(internal etc)>any>any and RED network and client networks>ports they require(https etc)>external address of virtual webserver (server load balancing)

Any ideas?


This thread was automatically locked due to age.
Parents
  • 0
    Think I may have solved it, added a SNAT to traffic going to the Cisco and the networks beyond with the source translation as the RED address. 

    Hmmmm... that makes me suspect that the Host definition in WebAdmin for the Cisco runs afoul of what I call Rule #3:

    Never create a Host/Network definition bound to a specific interface.
    Always leave all definitions with 'Interface: >'.


    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Think I may have solved it, added a SNAT to traffic going to the Cisco and the networks beyond with the source translation as the RED address. 

    Hmmmm... that makes me suspect that the Host definition in WebAdmin for the Cisco runs afoul of what I call Rule #3:

    Never create a Host/Network definition bound to a specific interface.
    Always leave all definitions with 'Interface: >'.


    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    Hi BAlfson,
    why did you wrote this:

    Hmmmm... that makes me suspect that the Host definition in WebAdmin for the Cisco runs afoul of what I call Rule #3:

    Never create a Host/Network definition bound to a specific interface.
    Always leave all definitions with 'Interface: >'.


    Cheers - Bob



    if you have build your Network right, its never a Problem, if it makes a Problem you have to search on Layer1 to solve it.

    Firebear
Unfiltered HTML