Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26
  1. #11
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    9,013

    Default

    Make sure it is online and press refresh on the license page.
    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

  2. #12
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,231

    Default

    Still unlicensed. Added to command center and tried again. Still not licensed.

    Heading for the back country.

  3. #13
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,231

    Default

    Any ideas?

  4. #14
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    9,013

    Default

    Quote Originally Posted by donhwyo View Post
    Any ideas?
    We are looking into it.
    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

  5. #15
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,231

    Default

    Thanks

  6. #16
    Untangler
    Join Date
    May 2018
    Posts
    58

    Default

    >>During 1.2 i've found ALL traffic regardless if using VPN or not has high latency on new sessions, is this still the case?
    Are you still finding this issue with the 1.3 beta?

    No plans for Asus routers at this time, but we appreciate the feedback and the ask. Each hardware appliance requires a specific build for SD-WAN Router, so the builds are not as portable as with NG Firewall.
    Heather P
    Untangle Product Team

  7. #17
    Untanglit
    Join Date
    Mar 2020
    Posts
    20

    Default

    Are you still finding this issue with the 1.3 beta?
    Yes, can confirm the issue is still present with 1.3 beta
    when i ping <ip or domain>
    the first ping will be very high and the remaining 3 pings will be normal

    Code:
    C:\Users\Admin>ping 1.1.1.1
    
    
    Pinging 1.1.1.1 with 32 bytes of data:
    Reply from 1.1.1.1: bytes=32 time=845ms TTL=251
    Reply from 1.1.1.1: bytes=32 time=5ms TTL=251
    Reply from 1.1.1.1: bytes=32 time=5ms TTL=251
    Reply from 1.1.1.1: bytes=32 time=4ms TTL=251
    
    
    Ping statistics for 1.1.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 4ms, Maximum = 845ms, Average = 214ms
    
    
    C:\Users\Admin>ping 1.1.1.1
    
    
    Pinging 1.1.1.1 with 32 bytes of data:
    Reply from 1.1.1.1: bytes=32 time=4ms TTL=251
    Reply from 1.1.1.1: bytes=32 time=5ms TTL=251
    Reply from 1.1.1.1: bytes=32 time=4ms TTL=251
    Reply from 1.1.1.1: bytes=32 time=5ms TTL=251
    
    
    Ping statistics for 1.1.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 4ms, Maximum = 5ms, Average = 4ms
    as you can see the first session on creation is really high, the following are all normal, did another ping 1 minute later and its still normal.
    websites are also very slow upon visiting them at first, once the session is created the site feels snappy.

    I disabled all DHCP IPv6, Specific WAN was used directly to my ISP, no balancing or VPN's were used, just a straight connection to my ISP.
    1.2 ISP WAN = delay, VPN = no delay
    1.3 ISP WAN = delay, VPN = delay

    I also can confirm along with donhwyo when i try to license using VMware ESXi it doesn't license, but when I tried out the VirtualBox on Windows10, it was able to license SDWAN to "Unlimited", which was a surprise since i assumed you guys crippled it to 100Mbps on VM's(i really wish you didn't )

    Lastly when i create a OpenVPN WAN and bind it to a single manual WAN instead of "Any WAN", it wont connect, soon as i set it to "Any WAN" it will connect.

    Question: how do i go about using the VPN's DNS?, its clearly "addressed" in the IPv4 column under "Interfaces", but I can't figure out how to get clients to use OpenVPN connected DNS
    Last edited by sifu; 07-01-2020 at 04:41 AM.
    donhwyo likes this.

  8. #18
    Untangler
    Join Date
    May 2018
    Posts
    58

    Default

    We've refreshed our beta with some fixes.


    Resolved Issues:
    - There is high latency on new sessions over VPN tunnels with NAT off
    - QoS setting issues with Linksys and VirtualBox

    Download links:
    Untangle SD-WAN Router e3 download
    Untangle SD-WAN Router e6 download
    VMWare download
    Linksys WRT1900ACS download
    Linksys WRT3200ACM download
    Linksys WRT32X download
    Oracle VirtualBox download


    Please also see this new Knowledge Base article Routing Traffic via VPN Tunnels, which will help with configuring VPN interfaces and how to route traffic over them.
    Last edited by hpaunet; 07-07-2020 at 07:50 PM.
    Heather P
    Untangle Product Team

  9. #19
    Untanglit
    Join Date
    Mar 2020
    Posts
    20

    Default

    Can you confirm any of my above points?


    • High latency non-vpn traffic?
    • VMware/Virtualbox WAN speed 10Mbps
    • OpenVPN creation bug, if setting != "Any WAN" then connection failed.
    • use of the VPN's DNS? regardless if full VPN tunnel or not, the ISP's DNS is always used.

  10. #20
    Untangler
    Join Date
    May 2018
    Posts
    58

    Default

    Quote Originally Posted by sifu View Post
    Can you confirm any of my above points?
    Some comments inline here that cover the first three ...

    High latency non-vpn traffic?
    We were seeing some latency issues in general with the first beta, but not with the latest one (posted today).

    VMware/Virtualbox WAN speed 10Mbps
    VMware will have limited WAN speed if not licensed, so the 10 Mbps is probably coming from that. Virtualbox is only supported as a 'beta' version and is not limited at all.

    OpenVPN creation bug, if setting != "Any WAN" then connection failed.
    We helped troubleshoot some of our customers that were not getting traffic flowing over their VPN interfaces, which led to us create this documentation. A WAN Policy and at least one WAN rule needs to be created to route traffic over a VPN tunnel.
    Heather P
    Untangle Product Team

Page 2 of 3 FirstFirst 123 LastLast

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