Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14
  1. #11
    Untanglit
    Join Date
    Nov 2009
    Posts
    24

    Default

    Thanks a lot for the explanation. At the moment the Cisco default route is to forward to EXT_IF so that explains why everything is working with just adding forwarding rules on Untangle.

    The port is indeed 514, so I added a rule to forward that port to 192.168.158.100. I'm now getting messages from my switch (192.168.158.60) which must have been configured to an invalid host, been getting sent to the gateway by the default route, and is now getting hoovered-up by that rule and sent back to the Syslog server. But nothing from the router, should it be working at this point? I've checked the router and it's pointing at 192.168.158.100 port 514 UDP.

    And thank you for all your help so far on troubleshooting this!

  2. #12
    Untangle Ninja raditude's Avatar
    Join Date
    Jan 2009
    Location
    Eugene, OR
    Posts
    1,143

    Default

    Your router should be pointed at your UT EXT_IF (so something like 192.168.1.2 based on your diagram), then your port forward rule should kick in from there. Your cisco router can not see 192.168.158.100 because of UT.

  3. #13
    Untanglit
    Join Date
    Nov 2009
    Posts
    24

    Default

    Sending it to 192.168.1.2 works!

    Thank you so much for your help, I might finally be able to find out why the router hangs at 5am every morning now

  4. #14
    Untangle Ninja raditude's Avatar
    Join Date
    Jan 2009
    Location
    Eugene, OR
    Posts
    1,143

    Default

    No problem, glad we got it working in your environment.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2