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

Remote syslog Source IP

skm
I want to configure remote syslog, but syslog messages source IP is taken on every Firewall from WLAN Interface or public interface. How can I change this behaviour? Syslog server resides in HQ and HQ doesnt have any idea about WLAN networks on spoke Firewalls, so it must me LAN Network address from spoke Firewall.


This thread was automatically locked due to age.
Parents
  • 0
    If I understand correctly, your topology is as follows, and there's no masquerading of WLAN traffic to HQ, nor has the WLAN subnet been added to the VPN tunnel: 

    Syslog server in HQ  Branch UTM  Spoke UTM --- WLAN-1


    If so, then the easiest solution would be a NAT rule in the Spoke UTM:

    SNAT : WLAN-1 (Network) -> SYSLOG -> {Syslog Server in HQ} : from External (Address)


    Did I understand the situation?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    If I understand correctly, your topology is as follows, and there's no masquerading of WLAN traffic to HQ, nor has the WLAN subnet been added to the VPN tunnel: 

    Syslog server in HQ  Branch UTM  Spoke UTM --- WLAN-1


    If so, then the easiest solution would be a NAT rule in the Spoke UTM:

    SNAT : WLAN-1 (Network) -> SYSLOG -> {Syslog Server in HQ} : from External (Address)


    Did I understand the situation?

    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