Results 1 to 2 of 2
  1. #1
    Untanglit
    Join Date
    Feb 2010
    Posts
    16

    Default Traffic from utun interface IP 192.0.2.43

    The issue of packets from IP 192.0.2.43 has been raised earlier also but I could not find any satisfactory response. The TCP listener at port 9541, 9543 and others is running on utun interface with IP 192.0.2.43. Netstat -a shows Hundreds of connections established. TCP Traffic also goes out with source IP 192.0.2.43 which is intercepted by my ASA firewall by "reverse path check" policy on inside interface and stopped..

    If this virtual interface is for internal processes of UVM then why the traffic needs to be originated to outside destination IP and too when there is no load (On weekends).

    The interface is said to be used by OpenVPN also (p-t-p) but I am not using this module also even why these outbound connections.

    Thanks

    M.K.Gupta

  2. #2
    Untangle Ninja mrunkel's Avatar
    Join Date
    Jul 2008
    Posts
    2,989

    Default

    It has nothing to do with Openvpn. it's an address used internally by the uvm. A Linux kernel bug causes them to leak outisde occasionally. They are harmless.
    m.


    Big Frickin Disclaimer:
    While I'm pretty sure, I can't guarantee that I know what I'm doing. There might be a better way to do this, and this way might actually suck. Make sure you understand the implications of what you're doing before trying to follow these directions.

    It often helps troubleshooting if you have a good network map. Look here if you want my advice on how to draw one.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

Tags for this Thread

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