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

    Dpinger not starting

    Scheduled Pinned Locked Moved
    2.3-RC Snapshot Feedback and Issues - ARCHIVED
    6
    9
    3.7k
    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.
    • N
      NOYB
      last edited by

      Can't get dpinger to start.

      Snap1.jpg_thumb
      Snap1.jpg

      1 Reply Last reply Reply Quote 0
      • rbgargaR
        rbgarga Developer Netgate Administrator
        last edited by

        @NOYB:

        Can't get dpinger to start.

        Any information on logs? gateway.log or system.log

        Renato Botelho

        1 Reply Last reply Reply Quote 0
        • N
          NOYB
          last edited by

          No there was absolutely noting dpinger in the logs.

          Doing an upgrade instead of gitsync fixed it.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            @NOYB:

            Doing an upgrade instead of gitsync fixed it.

            Can't just gitsync when there are binary changes, dpinger wasn't there to run until post-upgrade.

            1 Reply Last reply Reply Quote 0
            • X
              xbipin
              last edited by

              im on the latest snap and also noticed in 1 wan pppoe and 1 vpn setup, on boot the wan monitoring is running but during boot the vpn doesnt come up soon enough so the vpn tunnel keeps saying unknown unless u restart dpinger, i know im not suffering dpinger not starting but it wont come up on boot if i enable monitoring for vpn only, restarting it does bring it up

              1 Reply Last reply Reply Quote 0
              • P
                phil.davis
                last edited by

                There are still calls in scripts like /etc/rc.newwanip to setup_gateways_monitor(), so it looks like it should be trying to setup dpinger again after a (virtual) WAN comes up. (Much the same process that should have been happening to restart apinger) So it is not immediately obvious what is not happening right.
                Since it comes up OK if you restart it after the virtual links are up, that means that the general code in setup_gateways_monitor() that works out which gateways have IP addresses… and starts the necessary dpinger processes is working.
                Some log output from around the time between initial boot until after the virtual link (VPN, 6RD...) comes up would help to see what the real-time sequence of events is.

                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                1 Reply Last reply Reply Quote 0
                • J
                  jwt Netgate
                  last edited by

                  until there are bugs open, it's unlikely to get fixed.

                  1 Reply Last reply Reply Quote 0
                  • X
                    xbipin
                    last edited by

                    here is the the log, nothing interesting though. Today morning i woke up and dpinger shows my pppoe wan as down but with RTT of 1.3ms  and 0% packet loss which seems strange, restarting dpinger brings it back to normal so for me its seems the issues which were with apinger still remain with dpinger, havent seen any useful improvements, probably needs some more work before its more fine tuned

                    Dec 13 12:51:47 firewall syslogd: kernel boot file is /boot/kernel/kernel
Dec 13 12:51:47 firewall kernel: Copyright (c) 1992-2015 The FreeBSD Project.
Dec 13 12:51:47 firewall kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Dec 13 12:51:47 firewall kernel: The Regents of the University of California. All rights reserved.
Dec 13 12:51:47 firewall kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Dec 13 12:51:47 firewall kernel: FreeBSD 10.2-STABLE #218 1b7c029(devel): Sat Dec 12 14:45:00 CST 2015
Dec 13 12:51:47 firewall kernel: root@pfs23-i386-builder:/usr/home/pfsense/pfsense/tmp/obj/usr/home/pfsense/pfsense/tmp/FreeBSD-src/sys/pfSense_wrap i386
Dec 13 12:51:47 firewall kernel: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Dec 13 12:51:47 firewall kernel: CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU)
Dec 13 12:51:47 firewall kernel: Origin="AuthenticAMD"  Id=0x5a2  Family=0x5  Model=0xa  Stepping=2
Dec 13 12:51:47 firewall kernel: Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>Dec 13 12:51:47 firewall kernel: AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>Dec 13 12:51:47 firewall kernel: real memory  = 268435456 (256 MB)
Dec 13 12:51:47 firewall kernel: avail memory = 226574336 (216 MB)
Dec 13 12:51:47 firewall kernel: pnpbios: Bad PnP BIOS data checksum
Dec 13 12:51:47 firewall kernel: random device not loaded; using insecure entropy
Dec 13 12:51:47 firewall kernel: wlan: mac acl policy registered
Dec 13 12:51:47 firewall kernel: K6-family MTRR support enabled (2 registers)
Dec 13 12:51:47 firewall kernel: random: <software, yarrow=""> initialized
Dec 13 12:51:47 firewall kernel: kbd0 at kbdmux0
Dec 13 12:51:47 firewall kernel: ACPI BIOS Error (bug): A valid RSDP was not found (20150515/tbxfroot-258)
Dec 13 12:51:47 firewall kernel: ACPI: Table initialisation failed: AE_NOT_FOUND
Dec 13 12:51:47 firewall kernel: ACPI: Try disabling either ACPI or apic support.
Dec 13 12:51:47 firewall kernel: cryptosoft0: <software crypto=""> on motherboard
Dec 13 12:51:47 firewall kernel: padlock0: No ACE support.
Dec 13 12:51:47 firewall kernel: pcib0 pcibus 0 on motherboard
Dec 13 12:51:47 firewall kernel: pci0: <pci bus=""> on pcib0
Dec 13 12:51:47 firewall kernel: Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007
Dec 13 12:51:47 firewall kernel: pci0: <encrypt decrypt,="" entertainment="" crypto=""> at device 1.2 (no driver attached)
Dec 13 12:51:47 firewall kernel: vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0
Dec 13 12:51:47 firewall kernel: vr0: Quirks: 0x2
Dec 13 12:51:47 firewall kernel: vr0: Revision: 0x96
Dec 13 12:51:47 firewall kernel: miibus0: <mii bus=""> on vr0
Dec 13 12:51:47 firewall kernel: ukphy0: <generic ieee="" 802.3u="" media="" interface=""> PHY 1 on miibus0
Dec 13 12:51:47 firewall kernel: ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
Dec 13 12:51:47 firewall kernel: vr0: Ethernet address: 00:0d:b9:13:47:84
Dec 13 12:51:47 firewall kernel: vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0
Dec 13 12:51:47 firewall kernel: vr1: Quirks: 0x2
Dec 13 12:51:47 firewall kernel: vr1: Revision: 0x96
Dec 13 12:51:47 firewall kernel: miibus1: <mii bus=""> on vr1
Dec 13 12:51:47 firewall kernel: ukphy1: <generic ieee="" 802.3u="" media="" interface=""> PHY 1 on miibus1
Dec 13 12:51:47 firewall kernel: ukphy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
Dec 13 12:51:47 firewall kernel: vr1: Ethernet address: 00:0d:b9:13:47:85
Dec 13 12:51:47 firewall kernel: vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 15 at device 11.0 on pci0
Dec 13 12:51:47 firewall kernel: vr2: Quirks: 0x2
Dec 13 12:51:47 firewall kernel: vr2: Revision: 0x96
Dec 13 12:51:47 firewall kernel: miibus2: <mii bus=""> on vr2
Dec 13 12:51:47 firewall kernel: ukphy2: <generic ieee="" 802.3u="" media="" interface=""> PHY 1 on miibus2
Dec 13 12:51:47 firewall kernel: ukphy2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
Dec 13 12:51:47 firewall kernel: vr2: Ethernet address: 00:0d:b9:13:47:86
Dec 13 12:51:47 firewall kernel: ath0: <atheros 5413=""> mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
Dec 13 12:51:47 firewall kernel: ath0: AR5413 mac 10.5 RF5413 phy 6.1
Dec 13 12:51:47 firewall kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0063
Dec 13 12:51:47 firewall kernel: isab0: <pci-isa bridge=""> port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0
Dec 13 12:51:47 firewall kernel: isa0: <isa bus=""> on isab0
Dec 13 12:51:47 firewall kernel: atapci0: <amd cs5536="" udma100="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0
Dec 13 12:51:47 firewall kernel: ata0: <ata channel=""> at channel 0 on atapci0
Dec 13 12:51:47 firewall kernel: ata1: <ata channel=""> at channel 1 on atapci0
Dec 13 12:51:47 firewall kernel: ohci0: <ohci (generic)="" usb="" controller=""> mem 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0
Dec 13 12:51:47 firewall kernel: usbus0 on ohci0
Dec 13 12:51:47 firewall kernel: ehci0: <amd cs5536="" (geode)="" usb="" 2.0="" controller=""> mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0
Dec 13 12:51:47 firewall kernel: usbus1: EHCI version 1.0
Dec 13 12:51:47 firewall kernel: usbus1 on ehci0
Dec 13 12:51:47 firewall kernel: cpu0 on motherboard
Dec 13 12:51:47 firewall kernel: pmtimer0 on isa0
Dec 13 12:51:47 firewall kernel: orm0: <isa option="" rom=""> at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0
Dec 13 12:51:47 firewall kernel: atrtc0: <at realtime="" clock=""> at port 0x70 irq 8 on isa0
Dec 13 12:51:47 firewall kernel: Event timer "RTC" frequency 32768 Hz quality 0
Dec 13 12:51:47 firewall kernel: attimer0: <at timer=""> at port 0x40 on isa0
Dec 13 12:51:47 firewall kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Dec 13 12:51:47 firewall kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Dec 13 12:51:47 firewall kernel: ppc0: parallel port not found.
Dec 13 12:51:47 firewall kernel: uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
Dec 13 12:51:47 firewall kernel: uart0: console (115200,n,8,1)
Dec 13 12:51:47 firewall kernel: uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
Dec 13 12:51:47 firewall kernel: Timecounters tick every 1.000 msec
Dec 13 12:51:47 firewall kernel: IPsec: Initialized Security Association Processing.
Dec 13 12:51:47 firewall kernel: usbus0: 12Mbps Full Speed USB v1.0
Dec 13 12:51:47 firewall kernel: usbus1: 480Mbps High Speed USB v2.0
Dec 13 12:51:47 firewall kernel: ugen0.1: <amd> at usbus0
Dec 13 12:51:47 firewall kernel: uhub0: <amd 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
Dec 13 12:51:47 firewall kernel: ugen1.1: <amd> at usbus1
Dec 13 12:51:47 firewall kernel: uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1
Dec 13 12:51:47 firewall kernel: ada0 at ata0 bus 0 scbus0 target 0 lun 0
Dec 13 12:51:47 firewall kernel: ada0: <cf 20110221="" 2gb=""> ATA-7 device
Dec 13 12:51:47 firewall kernel: ada0: Serial Number TSS50038141013121116
Dec 13 12:51:47 firewall kernel: ada0: 100.000MB/s transfers (UDMA5, PIO 512bytes)
Dec 13 12:51:47 firewall kernel: ada0: 1919MB (3931200 512 byte sectors)
Dec 13 12:51:47 firewall kernel: ada0: Previously was known as ad0
Dec 13 12:51:47 firewall kernel: random: unblocking device.
Dec 13 12:51:47 firewall kernel: Timecounter "TSC" frequency 498061478 Hz quality 800
Dec 13 12:51:47 firewall kernel: Root mount waiting for: usbus1 usbus0
Dec 13 12:51:47 firewall kernel: uhub0: 4 ports with 4 removable, self powered
Dec 13 12:51:47 firewall kernel: Root mount waiting for: usbus1
Dec 13 12:51:47 firewall kernel: uhub1: 4 ports with 4 removable, self powered
Dec 13 12:51:47 firewall kernel: Trying to mount root from ufs:/dev/ufs/pfsense1 [ro,sync,noatime]...
Dec 13 12:51:47 firewall kernel: stray irq7
Dec 13 12:51:47 firewall check_reload_status: Linkup starting vr1
Dec 13 12:51:47 firewall kernel: done.
Dec 13 12:51:47 firewall kernel: vr1: link state changed to DOWN
Dec 13 12:51:47 firewall ppp: Multi-link PPP daemon for FreeBSD
Dec 13 12:51:47 firewall ppp:  
Dec 13 12:51:47 firewall ppp: process 5284 started, version 5.7 (root@pfSense_master_i386_i386-pfSense_master-job-01 18:01 12-Oct-2015)
Dec 13 12:51:47 firewall ppp: web: web is not running
Dec 13 12:51:47 firewall ppp: [wan] Bundle: Interface ng0 created
Dec 13 12:51:47 firewall ppp: [wan_link0] Link: OPEN event
Dec 13 12:51:47 firewall kernel: ng0: changing name to 'pppoe0'
Dec 13 12:51:47 firewall ppp: [wan_link0] LCP: Open event
Dec 13 12:51:47 firewall ppp: [wan_link0] LCP: state change Initial --> Starting
Dec 13 12:51:47 firewall ppp: [wan_link0] LCP: LayerStart
Dec 13 12:51:47 firewall ppp: [wan_link0] PPPoE: Connecting to ''
Dec 13 12:51:49 firewall sshd[6756]: Server listening on :: port 44.
Dec 13 12:51:49 firewall sshlockout[6917]: sshlockout/webConfigurator v3.0 starting up
Dec 13 12:51:49 firewall sshd[6756]: Server listening on 0.0.0.0 port 44.
Dec 13 12:51:50 firewall check_reload_status: Linkup starting vr1
Dec 13 12:51:50 firewall kernel: vr1: link state changed to UP
Dec 13 12:51:53 firewall ppp: PPPoE: rec'd ACNAME "WC-JUB-AL301"
Dec 13 12:51:53 firewall ppp: [wan_link0] PPPoE: connection successful
Dec 13 12:51:53 firewall ppp: [wan_link0] Link: UP event
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: Up event
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: SendConfigReq #1
Dec 13 12:51:53 firewall ppp: [wan_link0]   PROTOCOMP
Dec 13 12:51:53 firewall ppp: [wan_link0]   MRU 1492
Dec 13 12:51:53 firewall ppp: [wan_link0]   MAGICNUM cd111138
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: rec'd Configure Request #148 (Req-Sent)
Dec 13 12:51:53 firewall ppp: [wan_link0]   MRU 1492
Dec 13 12:51:53 firewall ppp: [wan_link0]   AUTHPROTO PAP
Dec 13 12:51:53 firewall ppp: [wan_link0]   MAGICNUM 55c42799
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: SendConfigAck #148
Dec 13 12:51:53 firewall ppp: [wan_link0]   MRU 1492
Dec 13 12:51:53 firewall ppp: [wan_link0]   AUTHPROTO PAP
Dec 13 12:51:53 firewall ppp: [wan_link0]   MAGICNUM 55c42799
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent)
Dec 13 12:51:53 firewall ppp: [wan_link0]   PROTOCOMP
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: SendConfigReq #2
Dec 13 12:51:53 firewall ppp: [wan_link0]   MRU 1492
Dec 13 12:51:53 firewall ppp: [wan_link0]   MAGICNUM cd111138
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent)
Dec 13 12:51:53 firewall ppp: [wan_link0]   MRU 1492
Dec 13 12:51:53 firewall ppp: [wan_link0]   MAGICNUM cd111138
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Dec 13 12:51:53 firewall ppp: [wan_link0] PAP: using authname "xxxx"
Dec 13 12:51:53 firewall ppp: [wan_link0] PAP: sending REQUEST #1 len: 20
Dec 13 12:51:53 firewall ppp: [wan_link0] LCP: LayerUp
Dec 13 12:51:54 firewall ppp: [wan_link0] PAP: rec'd ACK #1 len: 13
Dec 13 12:51:54 firewall ppp: [wan_link0]   MESG: Login ok
Dec 13 12:51:54 firewall ppp: [wan_link0] LCP: authorization successful
Dec 13 12:51:54 firewall ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Dec 13 12:51:54 firewall ppp: [wan_link0] Link: Join bundle "wan"
Dec 13 12:51:54 firewall ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Dec 13 12:51:54 firewall ppp: [wan] IPCP: Open event
Dec 13 12:51:54 firewall ppp: [wan] IPCP: state change Initial --> Starting
Dec 13 12:51:54 firewall ppp: [wan] IPCP: LayerStart
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: Open event
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: state change Initial --> Starting
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: LayerStart
Dec 13 12:51:54 firewall ppp: [wan] IPCP: Up event
Dec 13 12:51:54 firewall ppp: [wan] IPCP: state change Starting --> Req-Sent
Dec 13 12:51:54 firewall ppp: [wan] IPCP: SendConfigReq #1
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 0.0.0.0
Dec 13 12:51:54 firewall ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: Up event
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: state change Starting --> Req-Sent
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: SendConfigReq #1
Dec 13 12:51:54 firewall ppp: [wan] IPCP: rec'd Configure Request #3 (Req-Sent)
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 94.59.136.1
Dec 13 12:51:54 firewall ppp: [wan]     94.59.136.1 is OK
Dec 13 12:51:54 firewall ppp: [wan] IPCP: SendConfigAck #3
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 94.59.136.1
Dec 13 12:51:54 firewall ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Dec 13 12:51:54 firewall ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
Dec 13 12:51:54 firewall ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Dec 13 12:51:54 firewall ppp: [wan] IPCP: SendConfigReq #2
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 0.0.0.0
Dec 13 12:51:54 firewall ppp: [wan_link0] LCP: rec'd Protocol Reject #149 (Opened)
Dec 13 12:51:54 firewall ppp: [wan_link0] LCP: protocol IPV6CP was rejected
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: protocol was rejected by peer
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: state change Req-Sent --> Stopped
Dec 13 12:51:54 firewall ppp: [wan] IPV6CP: LayerFinish
Dec 13 12:51:54 firewall ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 92.98.234.193
Dec 13 12:51:54 firewall ppp: [wan]     92.98.234.193 is OK
Dec 13 12:51:54 firewall ppp: [wan] IPCP: SendConfigReq #3
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 92.98.234.193
Dec 13 12:51:54 firewall ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Dec 13 12:51:54 firewall ppp: [wan]   IPADDR 92.98.234.193
Dec 13 12:51:54 firewall ppp: [wan] IPCP: state change Ack-Sent --> Opened
Dec 13 12:51:54 firewall ppp: [wan] IPCP: LayerUp
Dec 13 12:51:54 firewall ppp: [wan]   92.98.234.193 -> 94.59.136.1
Dec 13 12:51:54 firewall check_reload_status: rc.newwanip starting pppoe0
Dec 13 12:51:54 firewall ppp: [wan] IFACE: Up event
Dec 13 12:51:54 firewall ppp: [wan] IFACE: Rename interface ng0 to pppoe0
Dec 13 12:51:55 firewall php-fpm[5977]: /rc.newwanip: rc.newwanip: Info: starting on pppoe0.
Dec 13 12:51:58 firewall kernel: vr0: link state changed to DOWN
Dec 13 12:51:58 firewall check_reload_status: Linkup starting vr0
Dec 13 12:51:58 firewall php-cgi: rc.bootup: Resyncing OpenVPN instances.
Dec 13 12:51:58 firewall kernel: 
Dec 13 12:51:58 firewall kernel: tun2: changing name to 'ovpnc2'
Dec 13 12:51:58 firewall kernel: pflog0: promiscuous mode enabled
Dec 13 12:51:59 firewall kernel: .
Dec 13 12:51:59 firewall kernel: DUMMYNET 0 with IPv6 initialized (100409)
Dec 13 12:51:59 firewall kernel: load_dn_sched dn_sched FIFO loaded
Dec 13 12:51:59 firewall kernel: load_dn_sched dn_sched QFQ loaded
Dec 13 12:51:59 firewall kernel: load_dn_sched dn_sched RR loaded
Dec 13 12:51:59 firewall kernel: load_dn_sched dn_sched WF2Q+ loaded
Dec 13 12:51:59 firewall kernel: load_dn_sched dn_sched PRIO loaded
Dec 13 12:52:00 firewall kernel: ..
Dec 13 12:52:01 firewall check_reload_status: Linkup starting vr0
Dec 13 12:52:01 firewall kernel: 
Dec 13 12:52:01 firewall kernel: vr0: link state changed to UP
Dec 13 12:52:01 firewall kernel: done.
Dec 13 12:52:01 firewall php-cgi: rc.bootup: The command '/usr/sbin/pw groupdel 2000' returned exit code '65', the output was 'pw: unknown group `2000'' 
Dec 13 12:52:03 firewall kernel: done.
Dec 13 12:52:04 firewall kernel: done.
Dec 13 12:52:04 firewall php-cgi: rc.bootup: ROUTING: setting default route to 94.59.136.1
Dec 13 12:52:09 firewall kernel: 
Dec 13 12:52:09 firewall kernel: ovpnc2: link state changed to UP
Dec 13 12:52:09 firewall check_reload_status: rc.newwanip starting ovpnc2
Dec 13 12:52:11 firewall php-fpm[28981]: /rc.newwanip: rc.newwanip: Info: starting on ovpnc2.
Dec 13 12:54:19 firewall check_reload_status: Updating all dyndns
Dec 13 12:54:19 firewall kernel: done.
Dec 13 12:54:20 firewall kernel: .
Dec 13 12:54:20 firewall kernel: .
Dec 13 12:54:21 firewall kernel: ..
Dec 13 12:54:22 firewall kernel: .done.
Dec 13 12:54:23 firewall php-fpm[41745]: /rc.dyndns.update: phpDynDNS: updating cache file /conf/dyndns_wannamecheap'firewall'0.cache: 92.98.234.193
Dec 13 12:54:23 firewall php-fpm[41745]: /rc.dyndns.update: phpDynDNS: (Success) IP Address Updated Successfully!
Dec 13 12:54:26 firewall php-cgi: rc.bootup: miniupnpd: Starting service on interface: lan
Dec 13 12:54:26 firewall kernel: done.
Dec 13 12:54:26 firewall kernel: done.
Dec 13 12:54:27 firewall syslogd: exiting on signal 15
Dec 13 12:54:27 firewall syslogd: kernel boot file is /boot/kernel/kernel
Dec 13 12:54:29 firewall kernel: done.
Dec 13 12:54:29 firewall php-fpm[41745]: /rc.start_packages: Restarting/Starting all packages.
Dec 13 12:54:36 firewall kernel: done.
Dec 13 12:54:36 firewall kernel: done.
Dec 13 12:54:40 firewall getty[66086]: open /dev/ttyv0: No such file or directory
Dec 13 12:54:40 firewall sshlockout[66343]: sshlockout/webConfigurator v3.0 starting up
Dec 13 12:54:40 firewall login: login on ttyu0 as root</cf></amd></amd></amd></amd></at></at></isa></amd></ohci></ata></ata></amd></isa></pci-isa></atheros></generic></mii></via></generic></mii></via></generic></mii></via></encrypt></pci></software></software,></mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>
                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      @xbipin:

                      im on the latest snap and also noticed in 1 wan pppoe and 1 vpn setup, on boot the wan monitoring is running but during boot the vpn doesnt come up soon enough so the vpn tunnel keeps saying unknown unless u restart dpinger, i know im not suffering dpinger not starting but it wont come up on boot if i enable monitoring for vpn only, restarting it does bring it up

                      Probably the same as this.
                      https://redmine.pfsense.org/issues/4587

                      which I'll look at along with all the other open gateway monitoring bugs.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post