Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 31 replies
  • Subscribers 7 subscribers
  • Views 9913 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

Sophos UTM - IPv4/IPv6 Issue - IPSec

Sophos User438

Hi guys,

I have searched myself silly and dont get anywhere, so I come before you.

 

A little preface:

We are a small group of companies (headquarter/main company and 2 daughtercompanies/branches). There are 2 IPSec Site-2-Site tunnels established between the two branches and the headquarter (we, the HQ, are on respond since the branches dont have static IP's yet) - they work on a RDS/Terminalserver in our infrastructure.

We have just the worst WAN connection (Vodafone cable) - atrocious. Its on and off again - major disruptions etc. We are so remote that we dont have any alternatives like fiber (the DSL connection is solely for our VPN connection to the hosted cloud VoIP PBX of Deutsche Telekom), so we are stuck with Vodafone. It wasnt always as bad as now, but I have to provide redundancies now since 3 companies are affected.

I asked our mobile provider for a data plan and they can offer me a LTE data plan with a static, public IPv6 address. According to the sales rep I spoke to, it will allow incoming connections as well, but I need to verify with one of their technicians directly - lets assume it is.


I planned something like this:

 

I really dont want to establish a full blown IPv6 network in parallel to the IPv4. I saw here and there some blog posts and comments on the net (and Sophos forum) explaining the translation of IPv6 traffic to IPv4 and vice versa. 

How would I realise that on the UTM? With a DNAT rule?

Im eternally grateful for any input.

Thanks!



This thread was automatically locked due to age.
Parents
  • 0

    Hallo and welcome to the UTM Community!

    I'm not familiar with the Mikrotik - can it do IPv6-to-IPv4?  Do you have UTMs in the branches, or are these other brands?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hi Bob!

    Thanks for the reply - almost lost hope :)

     

    Sorry, should have been more clear on that:

     

    Main office: SG135 UTM

    Branch1: SG125 UTM

    Branch2: SG115 UTM

     

    The Mikrotik antenna has the so called "routerOS", but I activated the passthrough mode (similar to the bridge mode on a router), so the Mikrotik only uses the built-in LTE modem to forward the public IP - this has been tested and confirmed by me.

     

    Thanks and best regards

     

    Constantin

  • 0 in reply to Sophos User438

    We're getting closer, Constantin...

    If either endpoint is behind a NAT, that could cause the problem.  If not, we need a new extract from the IPsec log.  Do the following:

    1. Confirm that Debug is not enabled.
    2. Disable the IPsec Connection.
    3. Start the IPsec Live Log and wait for it to begin to populate.
    4. Enable the IPsec Connection.
    5. Show us about 60 lines from enabling through the error.  Or through the line containing "IPsec SA established."

    Also, please show pictures of the Edits of the IPsec Connection and Remote Gateway for both sides.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hey Bob,

    thanks for the reply. Bob you are scaring me with the NAT idea :). I specifically asked the sales rep that he forwards my question, if they allow IPSec connections through their LTE network, to their technicians and they confirmed. If there is something in the way from their side, Im going to be extremely disappointed.

    I gathered everything you wanted. I deactivated the other IPSec tunnels as well and purged the logs. Then I started up the IPv6 tunnel for clean results. But first the configurations:

     

    Branch Office:

     

     

    Headquarters:

     

    Log from Branch 1:

     

    2020:07:18-09:34:57 fw pluto[10315]: shutting down
2020:07:18-09:34:57 fw pluto[10315]: forgetting secrets
2020:07:18-09:34:57 fw pluto[10315]: "S_REF_IpsSitSim_3": deleting connection
2020:07:18-09:34:57 fw pluto[10315]: "S_REF_IpsSitSim_2": deleting connection
2020:07:18-09:34:57 fw pluto[10315]: "S_REF_IpsSitSim_1": deleting connection
2020:07:18-09:34:57 fw pluto[10315]: "S_REF_IpsSitSim_0": deleting connection
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface lo/lo ::1
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface ppp0/ppp0 2003:a:17f:XXXXXXX:855b
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface lo/lo 127.0.0.1
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface lo/lo 127.0.0.1
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface eth3/eth3 10.2.2.254
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface eth3/eth3 10.2.2.254
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface eth0/eth0 10.2.1.254
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface eth0/eth0 10.2.1.254
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface ppp0/ppp0 XXX.XXX.XXX.148
2020:07:18-09:34:57 fw pluto[10315]: shutting down interface ppp0/ppp0 XXX.XXX.XXX.148
2020:07:18-09:34:57 fw ipsec_starter[10308]: pluto stopped after 20 ms
2020:07:18-09:34:57 fw ipsec_starter[10308]: ipsec starter stopped
2020:07:18-09:52:54 fw ipsec_starter[16478]: Starting strongSwan 4.4.1git20100610 IPsec [starter]...
2020:07:18-09:52:54 fw pluto[16491]: Starting IKEv1 pluto daemon (strongSwan 4.4.1git20100610) THREADS VENDORID CISCO_QUIRKS
2020:07:18-09:52:54 fw ipsec_starter[16484]: pluto (16491) started after 20 ms
2020:07:18-09:52:54 fw pluto[16491]: loaded plugins: curl ldap aes des blowfish serpent twofish sha1 sha2 md5 random x509 pubkey pkcs1 pgp dnskey pem sqlite hmac gmp xauth attr attr-sql resolve 
2020:07:18-09:52:54 fw pluto[16491]:   including NAT-Traversal patch (Version 0.6c)
2020:07:18-09:52:54 fw pluto[16491]: Using Linux 2.6 IPsec interface code
2020:07:18-09:52:54 fw pluto[16491]: loading ca certificates from '/etc/ipsec.d/cacerts'
2020:07:18-09:52:54 fw pluto[16491]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaSigVpnSigniCa.pem'
2020:07:18-09:52:54 fw pluto[16491]: loading aa certificates from '/etc/ipsec.d/aacerts'
2020:07:18-09:52:54 fw pluto[16491]: loading ocsp certificates from '/etc/ipsec.d/ocspcerts'
2020:07:18-09:52:54 fw pluto[16491]: Changing to directory '/etc/ipsec.d/crls'
2020:07:18-09:52:54 fw pluto[16491]: loading attribute certificates from '/etc/ipsec.d/acerts'
2020:07:18-09:52:54 fw pluto[16491]: adding interface ppp0/ppp0 XXX.XXX.XXX.148:500
2020:07:18-09:52:54 fw pluto[16491]: adding interface ppp0/ppp0 XXX.XXX.XXX.148:4500
2020:07:18-09:52:54 fw pluto[16491]: adding interface eth0/eth0 10.2.1.254:500
2020:07:18-09:52:54 fw pluto[16491]: adding interface eth0/eth0 10.2.1.254:4500
2020:07:18-09:52:54 fw pluto[16491]: adding interface eth3/eth3 10.2.2.254:500
2020:07:18-09:52:54 fw pluto[16491]: adding interface eth3/eth3 10.2.2.254:4500
2020:07:18-09:52:54 fw pluto[16491]: adding interface lo/lo 127.0.0.1:500
2020:07:18-09:52:54 fw pluto[16491]: adding interface lo/lo 127.0.0.1:4500
2020:07:18-09:52:54 fw pluto[16491]: adding interface ppp0/ppp0 2003:a:17fXXXXXXXXXXXXX:855b:500
2020:07:18-09:52:54 fw pluto[16491]: adding interface lo/lo ::1:500
2020:07:18-09:52:54 fw pluto[16491]: loading secrets from "/etc/ipsec.secrets"
2020:07:18-09:52:54 fw pluto[16491]: listening for IKE messages
2020:07:18-09:52:54 fw pluto[16491]: added connection description "S_REF_IpsSitSim6_0"
2020:07:18-09:52:54 fw pluto[16491]: added connection description "S_REF_IpsSitSim6_1"
2020:07:18-09:52:54 fw pluto[16491]: added connection description "S_REF_IpsSitSim6_2"
2020:07:18-09:52:54 fw pluto[16491]: added connection description "S_REF_IpsSitSim6_3"

     

    Logs Headquarters:

    2020:07:18-09:52:57 fw-2 ipsec_starter[9373]: Starting strongSwan 4.4.1git20100610 IPsec [starter]...
2020:07:18-09:52:57 fw-2 pluto[9386]: Starting IKEv1 pluto daemon (strongSwan 4.4.1git20100610) THREADS VENDORID CISCO_QUIRKS
2020:07:18-09:52:57 fw-2 ipsec_starter[9379]: pluto (9386) started after 20 ms
2020:07:18-09:52:57 fw-1 ipsec_starter[20927]: Starting strongSwan 4.4.1git20100610 IPsec [starter]...
2020:07:18-09:52:57 fw-1 ipsec_starter[20927]: no default route - cannot cope with %defaultroute!!!
2020:07:18-09:52:57 fw-1 pluto[20940]: Starting IKEv1 pluto daemon (strongSwan 4.4.1git20100610) THREADS VENDORID CISCO_QUIRKS
2020:07:18-09:52:57 fw-1 ipsec_starter[20933]: pluto (20940) started after 20 ms
2020:07:18-09:52:58 fw-2 pluto[9386]: loaded plugins: curl ldap aes des blowfish serpent twofish sha1 sha2 md5 random x509 pubkey pkcs1 pgp dnskey pem sqlite hmac gmp xauth attr attr-sql resolve 
2020:07:18-09:52:58 fw-2 pluto[9386]:   including NAT-Traversal patch (Version 0.6c)
2020:07:18-09:52:58 fw-2 pluto[9386]: Using Linux 2.6 IPsec interface code
2020:07:18-09:52:58 fw-1 pluto[20940]: loaded plugins: curl ldap aes des blowfish serpent twofish sha1 sha2 md5 random x509 pubkey pkcs1 pgp dnskey pem sqlite hmac gmp xauth attr attr-sql resolve 
2020:07:18-09:52:58 fw-1 pluto[20940]:   including NAT-Traversal patch (Version 0.6c)
2020:07:18-09:52:58 fw-1 pluto[20940]: Using Linux 2.6 IPsec interface code
2020:07:18-09:52:58 fw-2 pluto[9386]: HA system enabled and listening on interface eth6
2020:07:18-09:52:58 fw-2 pluto[9386]: Initial HA switch to master mode
2020:07:18-09:52:58 fw-2 pluto[9386]: loading ca certificates from '/etc/ipsec.d/cacerts'
2020:07:18-09:52:58 fw-2 pluto[9386]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaVerVpnSigniCaThu.pem'
2020:07:18-09:52:58 fw-2 pluto[9386]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaVerVpnSigniCaThu2.pem'
2020:07:18-09:52:58 fw-2 pluto[9386]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaSigVpnSigniCa.pem'
2020:07:18-09:52:58 fw-2 pluto[9386]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaVerNextcVerifCa.pem'
2020:07:18-09:52:58 fw-2 pluto[9386]: loading aa certificates from '/etc/ipsec.d/aacerts'
2020:07:18-09:52:58 fw-2 pluto[9386]: loading ocsp certificates from '/etc/ipsec.d/ocspcerts'
2020:07:18-09:52:58 fw-2 pluto[9386]: Changing to directory '/etc/ipsec.d/crls'
2020:07:18-09:52:58 fw-2 pluto[9386]: loading attribute certificates from '/etc/ipsec.d/acerts'
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface tun0/tun0 10.1.16.1:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface tun0/tun0 10.1.16.1:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.112/lag0.112 10.1.12.1:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.112/lag0.112 10.1.12.1:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.114/lag0.114 10.1.14.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.114/lag0.114 10.1.14.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.113/lag0.113 10.1.13.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.113/lag0.113 10.1.13.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.102/lag0.102 10.1.2.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.102/lag0.102 10.1.2.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.105/lag0.105 10.1.5.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.105/lag0.105 10.1.5.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.104/lag0.104 10.1.4.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.104/lag0.104 10.1.4.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.106/lag0.106 10.1.6.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.106/lag0.106 10.1.6.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.103/lag0.103 10.1.3.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.103/lag0.103 10.1.3.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.110/lag0.110 10.1.10.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.110/lag0.110 10.1.10.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.111/lag0.111 10.1.11.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.111/lag0.111 10.1.11.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.140/lag0.140 192.168.40.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.140/lag0.140 192.168.40.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.101/lag0.101 10.1.1.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0.101/lag0.101 10.1.1.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0/lag0 10.1.99.254:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lag0/lag0 10.1.99.254:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth6/eth6 198.19.250.2:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth6/eth6 198.19.250.2:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth5/eth5 10.1.21.1:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth5/eth5 10.1.21.1:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth4/eth4 XXX.XXX.XXX.57:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth4/eth4 XXX.XXX.XXX.57:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lo/lo 127.0.0.1:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lo/lo 127.0.0.1:4500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface eth7/eth7 2a01:598:XXXXXXXXXXXXXXf0:4007:500
2020:07:18-09:52:58 fw-2 pluto[9386]: adding interface lo/lo ::1:500
2020:07:18-09:52:58 fw-2 pluto[9386]: loading secrets from "/etc/ipsec.secrets"
2020:07:18-09:52:58 fw-2 pluto[9386]: listening for IKE messages
2020:07:18-09:52:58 fw-2 pluto[9386]: added connection description "S_REF_IpsSitKh6_0"
2020:07:18-09:52:58 fw-2 pluto[9386]: "S_REF_IpsSitKh6_0" #1: initiating Main Mode
2020:07:18-09:52:58 fw-2 pluto[9386]: ERROR: "S_REF_IpsSitKh6_0" #1: sendto on eth7 to 2003:a:17f:XXXXXXXXXXXXX:855b:500 failed in main_outI1. Errno 1: Operation not permitted
2020:07:18-09:52:58 fw-2 pluto[9386]: added connection description "S_REF_IpsSitKh6_1"
2020:07:18-09:52:58 fw-2 pluto[9386]: added connection description "S_REF_IpsSitKh6_2"
2020:07:18-09:52:58 fw-2 pluto[9386]: added connection description "S_REF_IpsSitKh6_3"
2020:07:18-09:52:58 fw-2 pluto[9386]: HA System: pluto already is in master mode
2020:07:18-09:52:58 fw-1 pluto[20940]: HA system enabled and listening on interface eth6
2020:07:18-09:52:58 fw-1 pluto[20940]: loading ca certificates from '/etc/ipsec.d/cacerts'
2020:07:18-09:52:58 fw-1 pluto[20940]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaVerNextcVerifCa.pem'
2020:07:18-09:52:58 fw-1 pluto[20940]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaVerVpnSigniCaThu.pem'
2020:07:18-09:52:58 fw-1 pluto[20940]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaSigVpnSigniCa.pem'
2020:07:18-09:52:58 fw-1 pluto[20940]:   loaded ca certificate from '/etc/ipsec.d/cacerts/REF_CaVerVpnSigniCaThu2.pem'
2020:07:18-09:52:58 fw-1 pluto[20940]: loading aa certificates from '/etc/ipsec.d/aacerts'
2020:07:18-09:52:58 fw-1 pluto[20940]: loading ocsp certificates from '/etc/ipsec.d/ocspcerts'
2020:07:18-09:52:58 fw-1 pluto[20940]: Changing to directory '/etc/ipsec.d/crls'
2020:07:18-09:52:58 fw-1 pluto[20940]: loading attribute certificates from '/etc/ipsec.d/acerts'
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.112/lag0.112 10.1.12.1:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.112/lag0.112 10.1.12.1:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.114/lag0.114 10.1.14.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.114/lag0.114 10.1.14.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.113/lag0.113 10.1.13.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.113/lag0.113 10.1.13.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.102/lag0.102 10.1.2.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.102/lag0.102 10.1.2.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.105/lag0.105 10.1.5.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.105/lag0.105 10.1.5.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.104/lag0.104 10.1.4.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.104/lag0.104 10.1.4.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.106/lag0.106 10.1.6.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.106/lag0.106 10.1.6.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.103/lag0.103 10.1.3.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.103/lag0.103 10.1.3.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.110/lag0.110 10.1.10.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.110/lag0.110 10.1.10.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.111/lag0.111 10.1.11.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.111/lag0.111 10.1.11.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.140/lag0.140 192.168.40.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.140/lag0.140 192.168.40.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.101/lag0.101 10.1.1.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0.101/lag0.101 10.1.1.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0/lag0 10.1.99.254:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lag0/lag0 10.1.99.254:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface eth6/eth6 198.19.250.1:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface eth6/eth6 198.19.250.1:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface eth5/eth5 10.1.21.1:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface eth5/eth5 10.1.21.1:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface eth4/eth4 XXX.XXX.XXX.57:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface eth4/eth4 XXX.XXX.XXX.57:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lo/lo 127.0.0.1:500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lo/lo 127.0.0.1:4500
2020:07:18-09:52:58 fw-1 pluto[20940]: adding interface lo/lo ::1:500
2020:07:18-09:52:58 fw-1 pluto[20940]: loading secrets from "/etc/ipsec.secrets"
2020:07:18-09:52:58 fw-1 pluto[20940]: HA System: not master, won't listen for IKE messages
2020:07:18-09:52:58 fw-1 pluto[20940]: added connection description "S_REF_IpsSitKh6_0"
2020:07:18-09:52:58 fw-1 pluto[20940]: added connection description "S_REF_IpsSitKh6_1"
2020:07:18-09:52:58 fw-1 pluto[20940]: added connection description "S_REF_IpsSitKh6_2"
2020:07:18-09:52:58 fw-1 pluto[20940]: added connection description "S_REF_IpsSitKh6_3"
2020:07:18-09:52:58 fw-1 pluto[20940]: Pluto is now in slave mode

     

    Again I see the "Operation not permitted", but not the default route error from yesterday - probably something to do with not having the other tunnels active?

    Anyway - can you make something out of it? Ohh, Im getting a sinking feeling...

     

    Thanks and best regards,

    Constantin

  • 0 in reply to Sophos User438

    What happens if you de-select 'Bind tunnel to interface' in the headquarters IPsec Connection definition?  Selecting that requires you to provide routing manually.  That should only be necessary if you want to have both tunnels established by following the Tutorial [DE] that I linked to above.

    Ich drucke mir die Daumen, Constantin !

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hey Bob,

    this is strange - I didnt get any notification that you replied, otherwise I would have answered asap. Since this has grown into a full blown obsession, I played around with all the settings on the weekend and...

     

    Now comes the strange part - this only works with the following conditions:

     

    Branch1 -      Initiate
    Branch1 -      PresharedKey
    Branch1 -      VPN ID type / IP Address

    HQ - Respond 
    HQ - PresharedKey
    HQ - VPN ID Type / IP Address

    Any other constellation (RSA key, switched initiate/respond, VPN ID type hostname) will not work.

    While Im SO relieved that the sales rep wasnt lying (:D) and it is working, Im a little confused why it works only with the aforementioned settings. Dont get me wrong - Im glad it does, but I would rather use RSA than PSK.

    Im also observing the subnets taking an usual long time to establish. I suspect the LTE connection (the antenna is inside my office, as mentioned before) - quick ping test from UTM to UTM:

    5 packets transmitted, 2 received, 60% packet loss, time 4022ms

    While the connection itself is established (why only this way needs to be investigated further by me, but that can wait a little), I cant ping through the tunnel. Two questions for you Bob:

    - How can I streamline the performance of the tunnel? Adjusting MTU etc.?
    - Could performance of the tunnel be so bad that I dont get anywhere with Ping tests through the tunnel (If I do tracert from both sides, there is only timeout after the first gateway.)? Im still afraid I have to deploy some kind of routing here, since Branch1 is a dualstack DSL etc. - I have no idea.

    Thanks and best regards,

    Constantin

  • 0 in reply to Sophos User438

    Almost there, Constantin...

    Do you have 'Support path MTU discovery' selected in the 'Advanced' section of the Remote Gateways?  Are pings then faster?

    I'm glad you found a combination to make it work.  Is either UTM behind a NATting router?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to Sophos User438

    Hi Constantin,

    just curious: why do you use LTE on both ends?

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to BAlfson

    Hey Bob.

    No, before I started to the deploy the tunnels etc. I went to Branch1 and put their Zyxel 5501 into Bridgemode, letting the UTM PPPoE connect. On our side is the Mikrotik LHG LTE6 antenna also in bridgemode, which gives eth7 ("LTE_Backup" interface) the IPv6 address through DHCP.

    The MTU discovery feature was not activated on both ends - I will test today and post my results.

     

    @Philipp

    Hi. The LTE connection is only on our side as a backup, if and when that damn Vodafone cable connection fails again. On the branch side we have a regular DSL (dualstack) connection.

     

    Best regards,

    Constantin

  • 0 in reply to BAlfson

    Hey Bob,

    I activated the Path MTU Discovery on the Remote Gateways in both UTMs. It did not help at all. When the IPv6 tunnel is up, no pings are going through - I just get timeouts. I thought it might be something with the packetfilter, but the automatic firewall rules are activated on both sides. I did create the IPv6 tunnel the same way than its IPv4 counterpart and the working RDP connection is proof that there is nothing in the way.

    How could I zero in on this problem? Do we have to tcpdump on eth7? Im not sure what else I could check. 

    Thanks and best regards,

    Constantin

  • 0 in reply to Sophos User438

    Hint: maybe it would be much more simple/reliable when not using LTE on BOTH ends?

    What was the reason for doing it like this?

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to PhilippRusch

    Hi Philipp,

    did you not read my earlier reply? Only on our end (headquarters) is the LTE antenna. In Branch1 one is, as I said before, a regular DSL connection.

     

    Best regards,

    Constantin

Reply Children
  • 0 in reply to Sophos User438

    OK - I see!

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to Sophos User438

    Did you check the firewall log, Constantin, to see if pings are blocked there?  If they are, see #2 in Rulz (last updated 2019-04-17).

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hey Bob,

    I observed on both sides the Live Log of the firewall and there are no drops of any kind when I try to ping (I also turned off IPS and ATP), only timout:

     

     

    Not sure what else we could do. Can we listen "inside" the tunnel with tcpdump? So we know that the ping at least went into the tunnel?

    Thanks and best regards,

    Constantin

     

  • 0 in reply to Sophos User438

    First, we need the REF_ of the tunnel.  If "Branch 1" is the name of the IPsec Connection, which we can find with:

    cc get_object_by_name ipsec_connection site_to_site 'Branch 1'|grep \'ref

    That will return something like REF_IpsSitBranch1.

    To watch the traffic in the tunnel:

    espdump -n --conn REF_IpsSitBranch1 -vv

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hey Bob,

    now Im really confused. The ping clearly goes into the tunnel and is even noticed on the other side.

     

     

    Branch1:

     

    HQ:

    Not sure what else to do here. I checked all the logs - firewall, IPS, ATP - in the end I turned off intrusion prevenion and atp but that didnt help in any way.

    Do you have another approach?

    Thanks and best regards,

    Constantin

Unfiltered HTML