Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 2 subscribers
  • Views 2665 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

ASG With 2 WAN Links; Flush RED Device through 2nd WAN

mrwebguy
The title essentially describes what I need to configure.  We have a second WAN connection that I'd like to connect to a free eth port on an ASG120.  It happens to be on the same subnet as a the RED device but it's across the street from our main location.  I currently have the RED configured and working as a Static IP but connecting to the main WAN connection on the ASG (2 separate network providers; lots of hops between).  

I need some assistance in setting up the ASG's second WAN connection and then allowing it to handle the RED traffic through this connection instead.  Being on the same subnet should save some latency so this can only benefit the connection.  

Any input from the expert pool would be wonderful!

Thanks,
Joe


This thread was automatically locked due to age.
Parents
  • 0
    Neither of those rules would work - you can't use an interface object as the destination in the traffic selector - you can't create a multipath rule in Astaro to tell the remote device what IP to send to.[:)]  In any case, the RED should only be calling WAN2.

    For the second one, I assume that "AstaroRED" is a service TCP/UDP 3400.  Then, if things don't work without it, I think it should be:

    2. Any→AstaroRED→Any→Bound to WAN2 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
    Neither of those rules would work - you can't use an interface object as the destination in the traffic selector - you can't create a multipath rule in Astaro to tell the remote device what IP to send to.[:)]  In any case, the RED should only be calling WAN2.

    For the second one, I assume that "AstaroRED" is a service TCP/UDP 3400.  Then, if things don't work without it, I think it should be:

    2. Any→AstaroRED→Any→Bound to WAN2 Interface

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML