• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

AWS pfSense+ Loopback interface

Scheduled Pinned Locked Moved General pfSense Questions
8 Posts 3 Posters 824 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P
    Paddy
    last edited by Paddy Jan 20, 2022, 2:26 PM Jan 20, 2022, 1:54 PM

    I am having issues with creating a ipsec config. It turns out that a IP (172.19.0.1) from the remote network is assigned to the loopback interface of the pfSense+

    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
    inet 127.0.0.1 netmask 0xff000000
    inet 172.19.0.1 netmask 0xffffff00

    It seems to have been used on the mobile clients ipsec config which we don't use.

    How can I remove this?

    J P 2 Replies Last reply Jan 20, 2022, 2:02 PM Reply Quote 0
    • J
      johnpoz LAYER 8 Global Moderator @Paddy
      last edited by Jan 20, 2022, 2:02 PM

      @paddy said in pfSense+ Loopback interface:

      mobile clients ipsec config which we don't use.

      Then why do you have it setup?

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      P 1 Reply Last reply Jan 20, 2022, 2:07 PM Reply Quote 0
      • P
        Paddy @johnpoz
        last edited by Jan 20, 2022, 2:07 PM

        @johnpoz It was default config on the AWS pfSenese+ AMI

        J 1 Reply Last reply Jan 20, 2022, 2:13 PM Reply Quote 0
        • J
          johnpoz LAYER 8 Global Moderator @Paddy
          last edited by Jan 20, 2022, 2:13 PM

          @paddy said in pfSense+ Loopback interface:

          on the AWS pfSenese+ AMI

          I have never set that up.. So have no idea what would be from default setup, etc.

          Did you run through the wizard?

          https://docs.netgate.com/pfsense/en/latest/packages/aws-vpc-wizard/index.html

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.8, 24.11

          P 1 Reply Last reply Jan 20, 2022, 2:19 PM Reply Quote 0
          • P
            Paddy @johnpoz
            last edited by Jan 20, 2022, 2:19 PM

            @johnpoz I did go through the wizard but don't remember IPSEC questions. How can I change the title of this topic to add AWS?

            J 1 Reply Last reply Jan 20, 2022, 2:22 PM Reply Quote 0
            • J
              johnpoz LAYER 8 Global Moderator @Paddy
              last edited by Jan 20, 2022, 2:22 PM

              @paddy if you edit your first post, you can edit the subject..

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 1
              • P
                Paddy @Paddy
                last edited by Jan 20, 2022, 4:37 PM

                @paddy said in AWS pfSense+ Loopback interface:

                I am having issues with creating a ipsec config. It turns out that a IP (172.19.0.1) from the remote network is assigned to the loopback interface of the pfSense+

                lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
                options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
                inet6 ::1 prefixlen 128
                inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
                inet 127.0.0.1 netmask 0xff000000
                inet 172.19.0.1 netmask 0xffffff00

                It seems to have been used on the mobile clients ipsec config which we don't use.

                How can I remove this?

                Found it. It was configured as a Virtual IP

                1 Reply Last reply Reply Quote 1
                • S
                  stephenw10 Netgate Administrator
                  last edited by Jan 20, 2022, 6:36 PM

                  Yes, the AWS AMI deploys with mobile IPSec configured but disabled. It has that VIP set to allow mobile IPSec clients to use it for DNS.

                  Steve

                  1 Reply Last reply Reply Quote 1
                  8 out of 8
                  • First post
                    8/8
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received