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

FreeBSD ifconfig failed: external program exited with error status: 1

Scheduled Pinned Locked Moved OpenVPN
10 Posts 3 Posters 10.2k 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.
  • M
    mph
    last edited by May 11, 2016, 7:46 PM

    Hi, I have strange issue with openvpn and ospf. May be ospf is not reason of the trouble, but I saw it when they worked together.
    VPN interface go down and I can't understand why

    Part of log

    May 11 21:10:36 openvpn 8070 /sbin/ifconfig ovpnc2 10.44.0.10 10.44.0.9 mtu 1500 netmask 255.255.255.255 up
    May 11 21:10:36 openvpn 8070 FreeBSD ifconfig failed: external program exited with error status: 1
    May 11 21:10:36 openvpn 8070 Exiting due to fatal error


    status.jpg
    status.jpg_thumb

    1 Reply Last reply Reply Quote 0
    • H
      heper
      last edited by May 11, 2016, 9:01 PM

      Maybe the route already exists?

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by May 12, 2016, 4:04 AM

        @heper:

        Maybe the route already exists?

        Yeah a conflict of some sort is usually the reason in that case, can't add an IP that's already configured elsewhere.

        1 Reply Last reply Reply Quote 0
        • M
          mph
          last edited by May 12, 2016, 4:47 AM

          Yes, you are right. Thank you for the hint.

          I checked interfaces and routes and found that in the server part ovpn interface is in up, and ospf had distributed route for this network to other.

          ovpn interface is in a down on the client, but the route(tunneled) arrived with ospf and ovpn can't update it

          1 Reply Last reply Reply Quote 0
          • H
            heper
            last edited by May 12, 2016, 6:16 AM

            there should be a checkbox on the ospf interface page to disable the distribution of tunnel networks.

            if you are on 2.3 & quagga 1.x: https://forum.pfsense.org/index.php?topic=111108.0
            quagga 1.x doesn't seem to update routes, even after link down.

            1 Reply Last reply Reply Quote 0
            • M
              mph
              last edited by May 12, 2016, 8:50 AM

              @heper:

              there should be a checkbox on the ospf interface page to disable the distribution of tunnel networks.

              if you are on 2.3 & quagga 1.x: https://forum.pfsense.org/index.php?topic=111108.0
              quagga 1.x doesn't seem to update routes, even after link down.

              What is the checkbox?

              I use 2.3 with quagga 0.99

              1 Reply Last reply Reply Quote 0
              • H
                heper
                last edited by May 12, 2016, 12:39 PM

                quagga > interface-settings > Accept Filter

                1 Reply Last reply Reply Quote 0
                • M
                  mph
                  last edited by May 17, 2016, 8:22 AM

                  The problem has not solved. Some tunnels also go down with the same reason.

                  in the log I see this

                  /sbin/ifconfig ovpnc4 10.44.0.54 10.44.0.53 mtu 1500 netmask 255.255.255.255 up
                  FreeBSD ifconfig failed: external program exited with error status: 1

                  I was tried to do ifconfig command manually, and recieved the next result

                  [2.3-RELEASE][root@nlvz.local]/root: /sbin/ifconfig ovpnc4 10.44.0.54 10.44.0.53 mtu 1500 netmask 255.255.255.255 up
                  ifconfig: ioctl (SIOCAIFADDR): Address already in use

                  but i can't find, who and how is using this address

                  ifconfigovpnc2: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                          options=80000 <linkstate>inet6 fe80::20c:29ff:fe90:2047%ovpnc2 prefixlen 64 scopeid 0x8
                          inet 10.44.0.14 –> 10.44.0.13 netmask 0xffffffff
                          nd6 options=21 <performnud,auto_linklocal>Opened by PID 41437
                  ovpnc3: flags=8010 <pointopoint,multicast>metric 0 mtu 1500
                          options=80000 <linkstate>nd6 options=21 <performnud,auto_linklocal>ovpnc4: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                          options=80000 <linkstate>inet6 fe80::20c:29ff:fe90:2047%ovpnc4 prefixlen 64 scopeid 0xa
                          nd6 options=21 <performnud,auto_linklocal>ovpnc5: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                          options=80000 <linkstate>inet6 fe80::20c:29ff:fe90:2047%ovpnc5 prefixlen 64 scopeid 0xb
                          inet 10.44.0.74 --> 10.44.0.73 netmask 0xffffffff
                          nd6 options=21 <performnud,auto_linklocal>Opened by PID 92738</performnud,auto_linklocal></linkstate></up,pointopoint,running,multicast></performnud,auto_linklocal></linkstate></up,pointopoint,running,multicast></performnud,auto_linklocal></linkstate></pointopoint,multicast></performnud,auto_linklocal></linkstate></up,pointopoint,running,multicast>

                  1 Reply Last reply Reply Quote 0
                  • H
                    heper
                    last edited by May 19, 2016, 8:26 AM May 17, 2016, 10:15 AM

                    Check your routing table (diagnostics routing)
                    It will probably have /32 routes in there that match your tunnel network…. the same routes can be found in the ospf status screen

                    i have one site where the accept filter isn't enough.
                    there, i fill in the tunnel subnets in the quagga 'disable acceptance' list (=bottom of global settings)

                    The attached screenshot is at the SERVER end of the tunnel (hence the .1 address' )
                    On the client end its the same except it is for the .2 address'

                    hope it helps.

                    disable_acceptance.png
                    disable_acceptance.png_thumb

                    1 Reply Last reply Reply Quote 0
                    • M
                      mph
                      last edited by May 19, 2016, 5:40 AM

                      SOLVED!!!!

                      Really thanks you!!!

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