Results 1 to 4 of 4
  1. #1
    Newbie
    Join Date
    May 2020
    Posts
    9

    Default Connect more than one VPN tunnels, just only one tunnel routing is work.

    Hi ,

    1. I want connect to Two OpenVPN Server.
    2. I using VPN tunnel to connect it.
    3. I have been try to testing each VPN tunnel connection is correct.
    4. When I Enable Two TunnelID and connect status is correct, but just one subnet routing connect is correct.
    5. I have been try to add the following rules

    Enabled > Conditionsestination Address =>192.168.1.1/24 Destination Tunnel: A_Location
    Enabled > Conditionsestination Address =>10.45.11.1/24 Destination Tunnel: B_Location

    After connect/disconnect the VPN tunnel and try to Ping 192.168.1.1 is work but ping 10.45.11.1 is not work.
    Sometime I try to change sequence to connect/disconnect the VPN tunnel and try to Ping 192.168.1.1 is not work but ping 10.45.11.1 is work.

    Anyone can tell me, what is the problem?
    Is the untangle can not support two VPN tunnels or OpenVPN setting problem?

    6. I try to remove VPN tunnel rules and turn off/on tunnel VPN.
    the Router table is

    = IPv4 Rules =
    0: from all lookup local
    100: from all fwmark 0xfe00/0xff00 lookup 1000
    32766: from all lookup main
    32767: from all lookup default
    50000: from 192.168.0.88 lookup uplink.1
    70001: from all fwmark 0x100/0xff00 lookup uplink.1
    70200: from all fwmark 0xc800/0xff00 lookup uplink.200
    70201: from all fwmark 0xc900/0xff00 lookup uplink.201
    1000000: from all lookup uplink.1

    = IPv4 Table main =
    10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.1
    10.45.11.0/24 via 172.16.146.21 dev tun201
    172.16.146.0/24 via 172.16.146.21 dev tun201
    172.16.146.21 dev tun201 scope link
    172.16.157.0/24 via 172.16.157.2 dev tun0
    172.16.157.2 dev tun0 proto kernel scope link src 172.16.157.1
    192.0.2.0/30 dev br.lxc proto kernel scope link src 192.0.2.1
    192.0.2.200/30 dev utun proto kernel scope link src 192.0.2.200
    192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.88
    192.168.0.1 dev eth0 scope link
    192.168.1.0/24 via 172.16.146.21 dev tun201
    192.168.3.0/24 via 192.168.3.33 dev tun200
    192.168.3.33 dev tun200 scope link
    192.168.10.0/24 via 172.16.146.21 dev tun201
    192.168.40.0/24 via 172.16.146.21 dev tun201

    = IPv4 Table balance =

    = IPv4 Table default =

    = IPv4 Table local =
    broadcast 10.0.0.0 dev eth1 proto kernel scope link src 10.0.0.1
    local 10.0.0.1 dev eth1 proto kernel scope host src 10.0.0.1
    broadcast 10.0.0.255 dev eth1 proto kernel scope link src 10.0.0.1
    broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
    local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1
    local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1
    broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
    local 172.16.146.22 dev tun201 proto kernel scope host src 172.16.146.22
    local 172.16.157.1 dev tun0 proto kernel scope host src 172.16.157.1
    broadcast 192.0.2.0 dev br.lxc proto kernel scope link src 192.0.2.1
    local 192.0.2.1 dev br.lxc proto kernel scope host src 192.0.2.1
    broadcast 192.0.2.3 dev br.lxc proto kernel scope link src 192.0.2.1
    local 192.0.2.200 dev utun proto kernel scope host src 192.0.2.200
    broadcast 192.0.2.200 dev utun proto kernel scope link src 192.0.2.200
    broadcast 192.0.2.203 dev utun proto kernel scope link src 192.0.2.200
    broadcast 192.168.0.0 dev eth0 proto kernel scope link src 192.168.0.88
    local 192.168.0.88 dev eth0 proto kernel scope host src 192.168.0.88
    broadcast 192.168.0.255 dev eth0 proto kernel scope link src 192.168.0.88
    local 192.168.3.34 dev tun200 proto kernel scope host src 192.168.3.34

    = IPv4 Dynamic Routing =

    = IPv4 Table uplink.1 =
    default via 192.168.0.1 dev eth0

    = IPv4 Table uplink.200 =
    default via 192.168.3.33 dev tun200

    = IPv4 Table uplink.201 =
    default via 172.16.146.21 dev tun201

    = IPv4 Route Rules =



    = IPv6 Rules =
    0: from all lookup local
    32766: from all lookup main

    = IPv6 Table main =
    fe80::/64 dev utun proto kernel metric 256 pref medium
    fe80::/64 dev br.lxc proto kernel metric 256 pref medium
    fe80::/64 dev tun0 proto kernel metric 256 pref medium
    fe80::/64 dev tun201 proto kernel metric 256 pref medium
    fe80::/64 dev tun200 proto kernel metric 256 pref medium

    = IPv6 Table default =

    = IPv6 Table local =
    local ::1 dev lo proto none metric 0 pref medium
    local fe80:: dev lo proto none metric 0 pref medium
    local fe80::167a:b47f:5b0c:74 dev lo proto none metric 0 pref medium
    local fe80::1d9f:30ef:b253:9d71 dev lo proto none metric 0 pref medium
    local fe80::88a0:54ff:fe73:8dbd dev lo proto none metric 0 pref medium
    local fe80::c317:218d:edf2:69f8 dev lo proto none metric 0 pref medium
    local fe80::e8e5:5dff:feee:78c3 dev lo proto none metric 0 pref medium
    ff00::/8 dev utun metric 256 pref medium
    ff00::/8 dev br.lxc metric 256 pref medium
    ff00::/8 dev tun0 metric 256 pref medium
    ff00::/8 dev tun201 metric 256 pref medium
    ff00::/8 dev tun200 metric 256 pref medium

    = IPv6 Table uplink.1 =

    = IPv6 Table uplink.200 =

    = IPv6 Table uplink.201 =




    = IPsec Rules =
    I have find a not correct route as below
    10.45.11.0/24 via 172.16.146.21 dev tun201
    192.168.1.0/24 via 172.16.146.21 dev tun201
    I think the normal route is
    10.45.11.0/24 via 172.16.146.21 dev tun201
    192.168.1.0/24 via 192.168.3.33 dev tun200
    Anyone can help me please?
    Last edited by choikinfat; 05-19-2020 at 09:20 AM.

  2. #2
    Newbie
    Join Date
    May 2020
    Posts
    9

    Default

    I'm using version is 15.1.0.20200520T115448.b25694768b-1buster

    Is it a bug?

    10.45.11.0/24 via 172.16.146.21 dev tun201
    192.168.1.0/24 via 172.16.146.21 dev tun201

  3. #3
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    8,741

    Default

    Post a screen capture of the rules page in http://your IP>/admin/index.do#service/tunnel-vpn/rules
    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

  4. #4
    Newbie
    Join Date
    May 2020
    Posts
    9

    Default

    Hi jcoffin,

    I have found a question.

    In the Untangle Client side:-
    When I Turn off the tunnel VPN.
    The current route is
    1.PNG

    But When I Turn ON the tunnel VPN
    The current route is
    2.PNG

    In the untangle OpenVPN Server side:
    I just enable export Networks 192.168.1.1/24, 192.168.40.1/24
    3.PNG

    Why 10.45.11.0/24 and 192.168.10.0/24 appear in my client side routing table.
    4.PNG

    I know 10.45.11.0/24 and 192.168.10.0/24 is server side Untangle openVPN (site to site network)

    How to Tunnel VPN connect to server side just add route 192.168.1.0/24 and 192.168.40.0/24?
    I don't want Tunnel VPN add other route like 10.45.11.0/24 and 192.168.10.0/24 in my router.
    It will affect my router routing table.

    How to do it?

    Thank jcoffin
    Last edited by choikinfat; Yesterday at 07:22 AM.

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