Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 812 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

How to forward one LAN IP address to another?

Brian Christensen

I am a sysadmin with 20+ years experience, but I am brand new to Sophos in general, and the XG firewall in particular, so this may be an easy question:

Long story as to *why*, but how can I take traffic from any LAN IP address sent to a *specific* LAN IP address, and forward that traffic to a *different* LAN IP address (in the same LAN IP range)?

Thank you in advance for any assistance!



This thread was automatically locked due to age.
Parents
  • 0

    Thank you for your reply!  It turns out I didn't end up needing this functionality (like I thought I would).  However, it would still be good for myself (and perhaps others who end up here via an Internet search in the future) to understand if what I was asking for, is even possible....indeed, it may not be possible!

    Specifically, I was asking if I had the LAN IP of 172.16.100.1, but I wanted all traffic headed for that LAN IP address to instead be sent to the *same* port number, but different LAN IP address of 172.16.100.200.......is that even possible, and if so, how?

    This may be a bad analogy, but the thinking here would be like an email *alias* (on an email server), where email is sent to an alias type email address, but actually ends up at a different email address......just like that, but for LAN IP addresses on the same Sophos port number.

    Again, maybe this isn't even possible......maybe this is even a pretty dumb question (my apologies in advance if so!).  On the other hand, maybe the KB article that you already provided details exactly how to do just what I was asking about?  I am not sure if so, because in your example below, you mentioned *different* port numbers, which isn't involved with what I was thinking.  Therefore, maybe that KB article is not applicable to what I was asking?

    Regardless, thank you again for your reply!!

  • 0 in reply to Brian Christensen

    Hello 

    In simple network scenario. the setup will look like.

    LAN machines >> LAN Switch >> Firewall(Gateway device)

    Source User machine IP = 172.16.100.10

    Actual LAN IP = 172.16.100.1

    TGT LAN IP = 172.16.100.200

    XG firewall interface IP = 172.16.100.254

    Here whenever you try to reach from one LAN IP(172.16.100.10) to another LAN IP(172.16.100.1), traffic will get routed through switch and will not reach to firewall.

    For example, if user with IP 172.16.100.10 tries to reach 172.16.100.1 then packet flow will be,

    User machine(172.16.100.10) >> Switch >> destination(172.16.100.1)

    Due to this, traffic will never hit on XG firewall and can not be forwarded to TGT LAN IP = 172.16.100.200

Reply
  • 0 in reply to Brian Christensen

    Hello 

    In simple network scenario. the setup will look like.

    LAN machines >> LAN Switch >> Firewall(Gateway device)

    Source User machine IP = 172.16.100.10

    Actual LAN IP = 172.16.100.1

    TGT LAN IP = 172.16.100.200

    XG firewall interface IP = 172.16.100.254

    Here whenever you try to reach from one LAN IP(172.16.100.10) to another LAN IP(172.16.100.1), traffic will get routed through switch and will not reach to firewall.

    For example, if user with IP 172.16.100.10 tries to reach 172.16.100.1 then packet flow will be,

    User machine(172.16.100.10) >> Switch >> destination(172.16.100.1)

    Due to this, traffic will never hit on XG firewall and can not be forwarded to TGT LAN IP = 172.16.100.200

Children
No Data