Static routes not applied after booting



  • 2.0-RC3 (i386)  built on Thu Jul 14 01:23:35 EDT 2011

    After booting i got this:

    Internet:
    Destination        Gateway            Flags    Refs      Use  Netif Expire
    default            yyy.zzz.6.1         UGS         0    24139    em0
    10.0.0.0/8         192.168.165.254    UGS         0    25452    em4
    xxx.yyy.43.62        00:0f:c9:04:db:6a  UHS         0      362    em0
    xxx.zzz.72.177      link#11            UHS         0        0    lo0
    yyy.zzz.6.0/23      link#1             U           0    13164    em0
    yyy.zzz.7.184       link#1             UHS         0        0    lo0
    yyy.zzz.62.62       00:0f:c9:04:db:6a  UHS         0        0    em0
    127.0.0.1          link#7             UH          0      131    lo0
    172.16.0.0/12      192.168.165.254    UGS         0   230613    em4
    zzz.zzz.161.164     yyy.zzz.6.1         UGHS        0     3383    em0
    192.168.0.0/16     192.168.165.254    UGS         0   107414    em4
    192.168.165.0/24   link#5             U           0   642374    em4
    192.168.165.253    link#5             UHS         0        0    lo0
    xxx.xxx.224.24/29  link#6             U           0    13164    em5
    xxx.xxx.224.26     link#6             UHS         0        0    lo0
    zzz.xxx.98.10        link#11            UH          0    13158 pppoe0
    zzz.yyy.149.205    zzz.xxx.98.10        UGHS        0        0 pppoe0
    zzz.yyy.151.51     zzz.xxx.98.10        UGHS        0        0 pppoe0
    

    If i apply the static routes again i got this:

    Internet:
    Destination        Gateway            Flags    Refs      Use  Netif Expire
    default            yyy.zzz.6.1         UGS         0    24923    em0
    10.0.0.0/8         192.168.165.254    UGS         1    25964    em4
    xxx.yyy.43.62        00:0f:c9:04:db:6a  UHS         0      362    em0
    xxx.zzz.72.177      link#11            UHS         0        0    lo0
    yyy.zzz.6.0/23      link#1             U           0    13297    em0
    yyy.zzz.7.184       link#1             UHS         0        0    lo0
    yyy.zzz.62.62       00:0f:c9:04:db:6a  UHS         0        0    em0
    vvv.vvv.71.134/32   xxx.xxx.224.25     UGS         0       20    em5
    vvv.vvv.245.6/32    xxx.xxx.224.25     UGS         0      488    em5
    127.0.0.1          link#7             UH          0      131    lo0
    172.16.0.0/12      192.168.165.254    UGS         0   232337    em4
    zzz.zzz.161.164     yyy.zzz.6.1         UGHS        0     4125    em0
    192.168.0.0/16     192.168.165.254    UGS         0   107944    em4
    192.168.165.0/24   link#5             U           0   646838    em4
    192.168.165.253    link#5             UHS         0        0    lo0
    yyy.yyy.39.1/32    xxx.xxx.224.25     UGS         0        3    em5
    xxx.xxx.224.24/29  link#6             U           0    13297    em5
    xxx.xxx.224.26     link#6             UHS         0        0    lo0
    yyy.xxx.120.106/32 xxx.xxx.224.25     UGS         0      728    em5
    zzz.xxx.98.10        link#11            UH          0    13291 pppoe0
    zzz.yyy.149.205    zzz.xxx.98.10        UGHS        0        0 pppoe0
    zzz.yyy.151.51     zzz.xxx.98.10        UGHS        0        0 pppoe0
    

    The static routes on LAN are allways there:

    10.0.0.0/8         192.168.165.254    UGS         0    25452    em4
    172.16.0.0/12      192.168.165.254    UGS         0   230613    em4
    192.168.0.0/16     192.168.165.254    UGS         0   107414    em4
    

    But the static routes on WAN are missing:

    vvv.vvv.71.134/32   xxx.xxx.224.25     UGS         0       20    em5
    vvv.vvv.245.6/32    xxx.xxx.224.25     UGS         0      488    em5
    yyy.yyy.39.1/32    xxx.xxx.224.25     UGS         0        3    em5
    yyy.xxx.120.106/32 xxx.xxx.224.25     UGS         0      728    em5
    


  • I have a NSA with 6 LAN ports.
    em4 is LAN with static IP.
    em5 is WAN1 with static IP. The gateway is configured and set on WAN1 Interface Tab as gateway.
    em0 is WAN2 with IP from DHCP.
    WAN3 is pppoe0 at interface em1.
    em2 and em3 not used.

    Gateway on interface WAN2 (em0) is set as default gateway.
    I have static rules for interface em4 and em5.

    After booting the rules for em4 are applied, but the rules for em5 are not.
    In webconfig the rules are still there. After opening and saving one, all rules are applied.



  • 2.0-RC3 (i386) built on Wed Jul 27 20:13:48 EDT 2011

    I still have this problem. What info could I give?

    Meanwhile i have a gateway group with gateway rule on LAN.
    The only info I have is:

    Jul 28 09:48:37 pfsense apinger: ALARM: GW_TDSL(217.5.98.11)  *** down ***
    Jul 28 09:48:38 pfsense php: : Resyncing OpenVPN instances for interface TDSL.
    Jul 28 09:48:39 pfsense kernel: WARNING: pseudo-random number generator used for IPsec processing
    Jul 28 09:48:41 pfsense check_reload_status: Reloading filter
    Jul 28 09:48:45 pfsense php: : MONITOR: GW_TDSL is down, removing from routing group
    Jul 28 09:48:47 pfsense check_reload_status: Reloading filter
    Jul 28 09:48:50 pfsense php: : MONITOR: GW_TDSL is down, removing from routing group
    

    This is because the gateway of TDSL don't respond on ping.



  • Please put screenshots of all this.
    Still is not clear to me what does not work.



  • #1
















  • #2


















  • #3

    [2.0-RC3][root@pfsense.rad-sh.local]/var/log(35): netstat -rn
    Routing tables

    Internet:
    Destination        Gateway            Flags    Refs      Use  Netif Expire
    default            195.243.224.25    UGS        1  817068    em5
    8.8.8.8            195.243.224.25    UGHS        0      860    em5
    10.0.0.0/8        192.168.165.254    UGS        0    8349    em4
    16.16.16.16        82.212.6.1        UGHS        0        0    em0
    80.153.72.177      link#11            UHS        0        0    lo0
    82.212.6.0/23      link#1            U          0    5293    em0
    82.212.7.184      link#1            UHS        0        0    lo0
    95.89.190.47      82.212.6.1        UGHS        0    15686    em0
    127.0.0.1          link#7            UH          0      131    lo0
    172.16.0.0/12      192.168.165.254    UGS        0  464874    em4
    192.168.0.0/16    192.168.165.254    UGS        0  209035    em4
    192.168.165.0/24  link#5            U          0  1194020    em4
    192.168.165.253    link#5            UHS        0        0    lo0
    195.243.224.24/29  link#6            U          0    5293    em5
    195.243.224.26    link#6            UHS        0        0    lo0
    217.5.98.11        link#11            UH          0    5288 pppoe0
















  • If the pfsense does proper function, the GW_CABLE should be the default gateway.
    GW_WAN is for IPSEC.



  • Anything on the system logs?

    If the pfsense does proper function, the GW_CABLE should be the default gateway.
    GW_WAN is for IPSEC.

    What does this mean?



  • That's only for info and should describe the planed operation of the pfsense.
    Normally the default gateway should be GW_Cable. As long as the static routes (to IPSEC peers) not applied the IPSEC packages leave the wrong interface and IPSEC didn't work. Until this is fixed I have to use GW_WAN as default gateway.

    Sorry for the confusion, but my german writing is much more detailed and exact.



  • Here is the system.log

    Jul 28 09:48:18 pfsense syslogd: kernel boot file is /boot/kernel/kernel
    Jul 28 09:48:18 pfsense kernel: Copyright (c) 1992-2010 The FreeBSD Project.
    Jul 28 09:48:18 pfsense kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    Jul 28 09:48:18 pfsense kernel: The Regents of the University of California. All rights reserved.
    Jul 28 09:48:18 pfsense kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
    Jul 28 09:48:18 pfsense kernel: FreeBSD 8.1-RELEASE-p4 #1: Wed Jul 27 20:13:02 EDT 2011
    Jul 28 09:48:18 pfsense kernel: sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 i386
    Jul 28 09:48:18 pfsense kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
    Jul 28 09:48:18 pfsense kernel: CPU: Intel(R) Atom(TM) CPU N270   @ 1.60GHz (1596.02-MHz 686-class CPU)
    Jul 28 09:48:18 pfsense kernel: Origin = "GenuineIntel"  Id = 0x106c2  Family = 6  Model = 1c  Stepping = 2
    Jul 28 09:48:18 pfsense kernel: Features=0xbfe9fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Jul 28 09:48:18 pfsense kernel: Features2=0x40c39d <sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,xtpr,pdcm,movbe>Jul 28 09:48:18 pfsense kernel: AMD Features=0x100000 <nx>Jul 28 09:48:18 pfsense kernel: AMD Features2=0x1 <lahf>Jul 28 09:48:18 pfsense kernel: TSC: P-state invariant
    Jul 28 09:48:18 pfsense kernel: real memory  = 1073741824 (1024 MB)
    Jul 28 09:48:18 pfsense kernel: avail memory = 1018265600 (971 MB)
    Jul 28 09:48:18 pfsense kernel: ACPI APIC Table: <intelr awrdacpi="">
    Jul 28 09:48:18 pfsense kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    Jul 28 09:48:18 pfsense kernel: FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads
    Jul 28 09:48:18 pfsense kernel: cpu0 (BSP): APIC ID:  0
    Jul 28 09:48:18 pfsense kernel: cpu1 (AP/HT): APIC ID:  1
    Jul 28 09:48:18 pfsense kernel: ioapic0: Changing APIC ID to 2
    Jul 28 09:48:18 pfsense kernel: ioapic0 <version 2.0=""> irqs 0-23 on motherboard
    Jul 28 09:48:18 pfsense kernel: netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling
    Jul 28 09:48:18 pfsense kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
    Jul 28 09:48:18 pfsense kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
    Jul 28 09:48:18 pfsense kernel: module_register_init: MOD_LOAD (wpi_fw, 0xc098b9d0, 0) error 1
    Jul 28 09:48:18 pfsense kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Jul 28 09:48:18 pfsense kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Jul 28 09:48:18 pfsense kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xc078c200, 0) error 1
    Jul 28 09:48:18 pfsense kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Jul 28 09:48:18 pfsense kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Jul 28 09:48:18 pfsense kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc078c2a0, 0) error 1
    Jul 28 09:48:18 pfsense kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Jul 28 09:48:18 pfsense kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Jul 28 09:48:18 pfsense kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc078c340, 0) error 1
    Jul 28 09:48:18 pfsense kernel: wlan: mac acl policy registered
    Jul 28 09:48:18 pfsense kernel: kbd1 at kbdmux0
    Jul 28 09:48:18 pfsense kernel: cryptosoft0: <software crypto=""> on motherboard
    Jul 28 09:48:18 pfsense kernel: padlock0: No ACE support.
    Jul 28 09:48:18 pfsense kernel: acpi0: <intelr awrdacpi=""> on motherboard
    Jul 28 09:48:18 pfsense kernel: acpi0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: acpi0: Power Button (fixed)
    Jul 28 09:48:18 pfsense kernel: acpi0: reservation of 0, a0000 (3) failed
    Jul 28 09:48:18 pfsense kernel: acpi0: reservation of 100000, 3f5e0000 (3) failed
    Jul 28 09:48:18 pfsense kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    Jul 28 09:48:18 pfsense kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
    Jul 28 09:48:18 pfsense kernel: cpu0: <acpi cpu=""> on acpi0
    Jul 28 09:48:18 pfsense kernel: cpu1: <acpi cpu=""> on acpi0
    Jul 28 09:48:18 pfsense kernel: acpi_button0: <power button=""> on acpi0
    Jul 28 09:48:18 pfsense kernel: pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0
    Jul 28 09:48:18 pfsense kernel: pci0: <acpi pci="" bus=""> on pcib0
    Jul 28 09:48:18 pfsense kernel: vgapci0: <vga-compatible display=""> port 0xff00-0xff07 mem 0xfdf00000-0xfdf7ffff,0xd0000000-0xdfffffff,0xfdf80000-0xfdfbffff irq 16 at device 2.0 on pci0
    Jul 28 09:48:18 pfsense kernel: agp0: <intel 945gme="" svga="" controller=""> on vgapci0
    Jul 28 09:48:18 pfsense kernel: agp0: detected 7932k stolen memory
    Jul 28 09:48:18 pfsense kernel: agp0: aperture size is 256M
    Jul 28 09:48:18 pfsense kernel: vgapci1: <vga-compatible display=""> mem 0xfde80000-0xfdefffff at device 2.1 on pci0
    Jul 28 09:48:18 pfsense kernel: pcib1: <acpi pci-pci="" bridge=""> irq 16 at device 28.0 on pci0
    Jul 28 09:48:18 pfsense kernel: pci1: <acpi pci="" bus=""> on pcib1
    Jul 28 09:48:18 pfsense kernel: em0: <intel(r) 1000="" pro="" network="" connection="" 7.2.3=""> port 0x9f00-0x9f1f mem 0xfd9c0000-0xfd9dffff,0xfd9fc000-0xfd9fffff irq 16 at device 0.0 on pci1
    Jul 28 09:48:18 pfsense kernel: em0: Using MSIX interrupts with 3 vectors
    Jul 28 09:48:18 pfsense kernel: em0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: em0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: em0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: pcib2: <acpi pci-pci="" bridge=""> irq 17 at device 28.1 on pci0
    Jul 28 09:48:18 pfsense kernel: pci2: <acpi pci="" bus=""> on pcib2
    Jul 28 09:48:18 pfsense kernel: em1: <intel(r) 1000="" pro="" network="" connection="" 7.2.3=""> port 0xdf00-0xdf1f mem 0xfd5c0000-0xfd5dffff,0xfd5fc000-0xfd5fffff irq 17 at device 0.0 on pci2
    Jul 28 09:48:18 pfsense kernel: em1: Using MSIX interrupts with 3 vectors
    Jul 28 09:48:18 pfsense kernel: em1: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: em1: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: em1: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: pcib3: <acpi pci-pci="" bridge=""> irq 18 at device 28.2 on pci0
    Jul 28 09:48:18 pfsense kernel: pci3: <acpi pci="" bus=""> on pcib3
    Jul 28 09:48:18 pfsense kernel: em2: <intel(r) 1000="" pro="" network="" connection="" 7.2.3=""> port 0xcf00-0xcf1f mem 0xfddc0000-0xfdddffff,0xfddfc000-0xfddfffff irq 18 at device 0.0 on pci3
    Jul 28 09:48:18 pfsense kernel: em2: Using MSIX interrupts with 3 vectors
    Jul 28 09:48:18 pfsense kernel: em2: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: em2: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: em2: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: pcib4: <acpi pci-pci="" bridge=""> irq 19 at device 28.3 on pci0
    Jul 28 09:48:18 pfsense kernel: pci4: <acpi pci="" bus=""> on pcib4
    Jul 28 09:48:18 pfsense kernel: em3: <intel(r) 1000="" pro="" network="" connection="" 7.2.3=""> port 0xbf00-0xbf1f mem 0xfdbe0000-0xfdbfffff,0xfdbc0000-0xfdbdffff irq 19 at device 0.0 on pci4
    Jul 28 09:48:18 pfsense kernel: em3: Using an MSI interrupt
    Jul 28 09:48:18 pfsense kernel: em3: [FILTER]
    Jul 28 09:48:18 pfsense kernel: uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a=""> port 0xfe00-0xfe1f irq 23 at device 29.0 on pci0
    Jul 28 09:48:18 pfsense kernel: uhci0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: uhci0: LegSup = 0x3000
    Jul 28 09:48:18 pfsense kernel: usbus0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a=""> on uhci0
    Jul 28 09:48:18 pfsense kernel: uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b=""> port 0xfd00-0xfd1f irq 19 at device 29.1 on pci0
    Jul 28 09:48:18 pfsense kernel: uhci1: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: usbus1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b=""> on uhci1
    Jul 28 09:48:18 pfsense kernel: uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c=""> port 0xfc00-0xfc1f irq 18 at device 29.2 on pci0
    Jul 28 09:48:18 pfsense kernel: uhci2: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: usbus2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c=""> on uhci2
    Jul 28 09:48:18 pfsense kernel: uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d=""> port 0xfb00-0xfb1f irq 16 at device 29.3 on pci0
    Jul 28 09:48:18 pfsense kernel: uhci3: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: usbus3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d=""> on uhci3
    Jul 28 09:48:18 pfsense kernel: ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller=""> mem 0xfdfff000-0xfdfff3ff irq 23 at device 29.7 on pci0
    Jul 28 09:48:18 pfsense kernel: ehci0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: usbus4: EHCI version 1.0
    Jul 28 09:48:18 pfsense kernel: usbus4: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller=""> on ehci0
    Jul 28 09:48:18 pfsense kernel: pcib5: <acpi pci-pci="" bridge=""> at device 30.0 on pci0
    Jul 28 09:48:18 pfsense kernel: pci5: <acpi pci="" bus=""> on pcib5
    Jul 28 09:48:18 pfsense kernel: em4: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3=""> port 0xaf00-0xaf3f mem 0xfd8e0000-0xfd8fffff irq 19 at device 10.0 on pci5
    Jul 28 09:48:18 pfsense kernel: em4: [FILTER]
    Jul 28 09:48:18 pfsense kernel: em5: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3=""> port 0xae00-0xae3f mem 0xfd8c0000-0xfd8dffff irq 18 at device 11.0 on pci5
    Jul 28 09:48:18 pfsense kernel: em5: [FILTER]
    Jul 28 09:48:18 pfsense kernel: isab0: <pci-isa bridge=""> at device 31.0 on pci0
    Jul 28 09:48:18 pfsense kernel: isa0: <isa bus=""> on isab0
    Jul 28 09:48:18 pfsense kernel: atapci0: <intel ich7="" udma100="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf800-0xf80f at device 31.1 on pci0
    Jul 28 09:48:18 pfsense kernel: ata0: <ata 0="" channel=""> on atapci0
    Jul 28 09:48:18 pfsense kernel: ata0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: atapci1: <intel ich7m="" sata150="" controller=""> port 0xf700-0xf707,0xf600-0xf603,0xf500-0xf507,0xf400-0xf403,0xf300-0xf30f mem 0xfdffc000-0xfdffc3ff irq 19 at device 31.2 on pci0
    Jul 28 09:48:18 pfsense kernel: atapci1: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: atapci1: AHCI called from vendor specific driver
    Jul 28 09:48:18 pfsense kernel: atapci1: AHCI v1.10 controller with 4 1.5Gbps ports, PM not supported
    Jul 28 09:48:18 pfsense kernel: ata2: <ata 0="" channel=""> on atapci1
    Jul 28 09:48:18 pfsense kernel: ata2: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: ata3: <ata 2="" channel=""> on atapci1
    Jul 28 09:48:18 pfsense kernel: ata3: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: pci0: <serial bus,="" smbus=""> at device 31.3 (no driver attached)
    Jul 28 09:48:18 pfsense kernel: acpi_tz0: <thermal zone=""> on acpi0
    Jul 28 09:48:18 pfsense kernel: atrtc0: <at realtime="" clock=""> port 0x70-0x73 irq 8 on acpi0
    Jul 28 09:48:18 pfsense kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    Jul 28 09:48:18 pfsense kernel: uart0: [FILTER]
    Jul 28 09:48:18 pfsense kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
    Jul 28 09:48:18 pfsense kernel: uart1: [FILTER]
    Jul 28 09:48:18 pfsense kernel: pmtimer0 on isa0
    Jul 28 09:48:18 pfsense kernel: orm0: <isa option="" rom=""> at iomem 0xef000-0xeffff pnpid ORM0000 on isa0
    Jul 28 09:48:18 pfsense kernel: sc0: <system console=""> at flags 0x100 on isa0
    Jul 28 09:48:18 pfsense kernel: sc0: VGA <16 virtual consoles, flags=0x300>
    Jul 28 09:48:18 pfsense kernel: vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    Jul 28 09:48:18 pfsense kernel: atkbdc0: <keyboard controller="" (i8042)=""> at port 0x60,0x64 on isa0
    Jul 28 09:48:18 pfsense kernel: atkbd0: <at keyboard=""> irq 1 on atkbdc0
    Jul 28 09:48:18 pfsense kernel: kbd0 at atkbd0
    Jul 28 09:48:18 pfsense kernel: atkbd0: [GIANT-LOCKED]
    Jul 28 09:48:18 pfsense kernel: atkbd0: [ITHREAD]
    Jul 28 09:48:18 pfsense kernel: ppc0: parallel port not found.
    Jul 28 09:48:18 pfsense kernel: est0: <enhanced speedstep="" frequency="" control=""> on cpu0
    Jul 28 09:48:18 pfsense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
    Jul 28 09:48:18 pfsense kernel: est: cpu_vendor GenuineIntel, msr 60f0c1e0600060f
    Jul 28 09:48:18 pfsense kernel: device_attach: est0 attach returned 6
    Jul 28 09:48:18 pfsense kernel: p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0
    Jul 28 09:48:18 pfsense kernel: est1: <enhanced speedstep="" frequency="" control=""> on cpu1
    Jul 28 09:48:18 pfsense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
    Jul 28 09:48:18 pfsense kernel: est: cpu_vendor GenuineIntel, msr 60f0c1e0600060f
    Jul 28 09:48:18 pfsense kernel: device_attach: est1 attach returned 6
    Jul 28 09:48:18 pfsense kernel: p4tcc1: <cpu frequency="" thermal="" control=""> on cpu1
    Jul 28 09:48:18 pfsense kernel: Timecounters tick every 1.000 msec
    Jul 28 09:48:18 pfsense kernel: IPsec: Initialized Security Association Processing.
    Jul 28 09:48:18 pfsense kernel: usbus0: 12Mbps Full Speed USB v1.0
    Jul 28 09:48:18 pfsense kernel: usbus1: 12Mbps Full Speed USB v1.0
    Jul 28 09:48:18 pfsense kernel: usbus2: 12Mbps Full Speed USB v1.0
    Jul 28 09:48:18 pfsense kernel: usbus3: 12Mbps Full Speed USB v1.0
    Jul 28 09:48:18 pfsense kernel: usbus4: 480Mbps High Speed USB v2.0
    Jul 28 09:48:18 pfsense kernel: ugen0.1: <intel> at usbus0
    Jul 28 09:48:18 pfsense kernel: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
    Jul 28 09:48:18 pfsense kernel: ugen1.1: <intel> at usbus1
    Jul 28 09:48:18 pfsense kernel: uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus1
    Jul 28 09:48:18 pfsense kernel: ugen2.1: <intel> at usbus2
    Jul 28 09:48:18 pfsense kernel: uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus2
    Jul 28 09:48:18 pfsense kernel: ugen3.1: <intel> at usbus3
    Jul 28 09:48:18 pfsense kernel: uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus3
    Jul 28 09:48:18 pfsense kernel: ugen4.1: <intel> at usbus4
    Jul 28 09:48:18 pfsense kernel: uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus4
    Jul 28 09:48:18 pfsense kernel: ad4: 152627MB <st160lt015 1ae141="" 0001sdm1=""> at ata2-master UDMA100 SATA 1.5Gb/s
    Jul 28 09:48:18 pfsense kernel: SMP: AP CPU #1 Launched!
    Jul 28 09:48:18 pfsense kernel: uhub0: 2 ports with 2 removable, self powered
    Jul 28 09:48:18 pfsense kernel: uhub1: 2 ports with 2 removable, self powered
    Jul 28 09:48:18 pfsense kernel: uhub2: 2 ports with 2 removable, self powered
    Jul 28 09:48:18 pfsense kernel: uhub3: 2 ports with 2 removable, self powered
    Jul 28 09:48:18 pfsense kernel: Root mount waiting for: usbus4
    Jul 28 09:48:18 pfsense kernel: Root mount waiting for: usbus4
    Jul 28 09:48:18 pfsense kernel: Root mount waiting for: usbus4
    Jul 28 09:48:18 pfsense kernel: uhub4: 8 ports with 8 removable, self powered
    Jul 28 09:48:18 pfsense kernel: Trying to mount root from ufs:/dev/ad4s1a
    Jul 28 09:48:18 pfsense kernel: ugen2.2: <aten> at usbus2
    Jul 28 09:48:18 pfsense kernel: ukbd0: <aten 0="" 2="" aten ="" cs-1716="" 08="" 04,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr=""> on usbus2
    Jul 28 09:48:18 pfsense kernel: kbd2 at ukbd0
    Jul 28 09:48:18 pfsense kernel: ums0: <aten 0="" 2="" aten ="" cs-1716="" 08="" 04,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr=""> on usbus2
    Jul 28 09:48:18 pfsense kernel: ums0: error reading report description
    Jul 28 09:48:18 pfsense kernel: device_attach: ums0 attach returned 12
    Jul 28 09:48:18 pfsense kernel: ums0: <aten 0="" 2="" aten ="" cs-1716="" 08="" 04,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr=""> on usbus2
    Jul 28 09:48:18 pfsense kernel: ums0: error reading report description
    Jul 28 09:48:18 pfsense kernel: device_attach: ums0 attach returned 12
    Jul 28 09:48:18 pfsense kernel: pflog0: promiscuous mode enabled
    Jul 28 09:48:19 pfsense check_reload_status: Linkup starting em1
    Jul 28 09:48:19 pfsense kernel: em1: link state changed to UP
    Jul 28 09:48:20 pfsense ppp: PPPoE: rec'd ACNAME "MANX52-erx"
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] PPPoE: connection successful
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] Link: UP event
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: Up event
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: state change Starting --> Req-Sent
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: SendConfigReq #1
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   PROTOCOMP
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MRU 1492
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MAGICNUM 2fe8df8c
    Jul 28 09:48:20 pfsense php: : rc.newwanip: Informational is starting em0.
    Jul 28 09:48:20 pfsense php: : rc.newwanip: on (IP address: 82.212.7.184) (interface: opt1) (real interface: em0).
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: rec'd Configure Request #163 (Req-Sent)
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MRU 1492
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   AUTHPROTO PAP
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MAGICNUM 7ac80b15
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: SendConfigAck #163
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MRU 1492
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   AUTHPROTO PAP
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MAGICNUM 7ac80b15
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: state change Req-Sent --> Ack-Sent
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: rec'd Configure Ack #1 (Ack-Sent)
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   PROTOCOMP
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MRU 1492
    Jul 28 09:48:20 pfsense ppp: [opt5_link0]   MAGICNUM 2fe8df8c
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: state change Ack-Sent --> Opened
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: auth: peer wants PAP, I want nothing
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] PAP: using authname "feste-ip5/7TBLJ84SUX1S@t-online-com.de"
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] PAP: sending REQUEST #1 len: 52
    Jul 28 09:48:20 pfsense ppp: [opt5_link0] LCP: LayerUp
    Jul 28 09:48:21 pfsense ppp: [opt5_link0] PAP: rec'd ACK #1 len: 5
    Jul 28 09:48:21 pfsense ppp: [opt5_link0] LCP: authorization successful
    Jul 28 09:48:21 pfsense ppp: [opt5_link0] Link: Matched action 'bundle "opt5" ""'
    Jul 28 09:48:21 pfsense ppp: [opt5_link0] Link: Join bundle "opt5"
    Jul 28 09:48:21 pfsense ppp: [opt5] Bundle: Status update: up 1 link, total bandwidth 64000 bps
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: Open event
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: state change Initial --> Starting
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: LayerStart
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: Up event
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: state change Starting --> Req-Sent
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: SendConfigReq #1
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 0.0.0.0
    Jul 28 09:48:21 pfsense ppp: [opt5]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: rec'd Configure Reject #1 (Req-Sent)
    Jul 28 09:48:21 pfsense ppp: [opt5]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: SendConfigReq #2
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 0.0.0.0
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: rec'd Configure Request #151 (Req-Sent)
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 217.5.98.11
    Jul 28 09:48:21 pfsense ppp: [opt5]     217.5.98.11 is OK
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: SendConfigAck #151
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 217.5.98.11
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: state change Req-Sent --> Ack-Sent
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: rec'd Configure Nak #2 (Ack-Sent)
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 80.153.72.177
    Jul 28 09:48:21 pfsense ppp: [opt5]     80.153.72.177 is OK
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: SendConfigReq #3
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 80.153.72.177
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: rec'd Configure Ack #3 (Ack-Sent)
    Jul 28 09:48:21 pfsense ppp: [opt5]   IPADDR 80.153.72.177
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: state change Ack-Sent --> Opened
    Jul 28 09:48:21 pfsense ppp: [opt5] IPCP: LayerUp
    Jul 28 09:48:21 pfsense ppp: [opt5]   80.153.72.177 -> 217.5.98.11
    Jul 28 09:48:21 pfsense apinger: Starting Alarm Pinger, apinger(43891)
    Jul 28 09:48:21 pfsense check_reload_status: Reloading filter
    Jul 28 09:48:21 pfsense check_reload_status: rc.newwanip starting pppoe0
    Jul 28 09:48:21 pfsense ppp: [opt5] IFACE: Up event
    Jul 28 09:48:23 pfsense php: : ROUTING: setting default route to 195.243.224.25
    Jul 28 09:48:24 pfsense php: : OpenNTPD is starting up.
    Jul 28 09:48:24 pfsense check_reload_status: Updating all dyndns
    Jul 28 09:48:25 pfsense php: : rc.newwanip: Informational is starting pppoe0.
    Jul 28 09:48:25 pfsense php: : rc.newwanip: on (IP address: 80.153.72.177) (interface: opt5) (real interface: pppoe0).
    Jul 28 09:48:26 pfsense apinger: Exiting on signal 15.
    Jul 28 09:48:27 pfsense check_reload_status: Reloading filter
    Jul 28 09:48:27 pfsense apinger: Starting Alarm Pinger, apinger(30741)
    Jul 28 09:48:27 pfsense php: : DynDns: updatedns() starting
    Jul 28 09:48:27 pfsense php: : DynDns debug information: 82.212.7.184 extracted from local system.
    Jul 28 09:48:27 pfsense php: : Gateways status could not be determined, considering all as up/active.
    Jul 28 09:48:27 pfsense php: : DynDns: Current WAN IP: 82.212.7.184 Cached IP: 82.212.7.184
    Jul 28 09:48:27 pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
    Jul 28 09:48:30 pfsense check_reload_status: Restarting ipsec tunnels
    Jul 28 09:48:30 pfsense php: : Gateways status could not be determined, considering all as up/active.
    Jul 28 09:48:32 pfsense php: : Forcefully reloading IPsec racoon daemon
    Jul 28 09:48:33 pfsense php: : Creating rrd update script
    Jul 28 09:48:35 pfsense php: : Restarting/Starting all packages.
    Jul 28 09:48:35 pfsense php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
    Jul 28 09:48:37 pfsense apinger: ALARM: GW_TDSL(217.5.98.11)  *** down ***
    Jul 28 09:48:38 pfsense php: : Resyncing OpenVPN instances for interface TDSL.
    Jul 28 09:48:39 pfsense kernel: WARNING: pseudo-random number generator used for IPsec processing
    Jul 28 09:48:41 pfsense check_reload_status: Reloading filter
    Jul 28 09:48:45 pfsense php: : MONITOR: GW_TDSL is down, removing from routing group
    Jul 28 09:48:47 pfsense check_reload_status: Reloading filter
    Jul 28 09:48:50 pfsense php: : MONITOR: GW_TDSL is down, removing from routing group
    Jul 28 09:49:27 pfsense apinger: Error while feeding rrdtool: Broken pipe
    Jul 28 09:49:27 pfsense apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Jul 28 09:50:01 pfsense sshd[51553]: error: PAM: authentication error for root from 46.165.143.97
    Jul 28 09:50:01 pfsense sshd[51553]: error: PAM: authentication error for root from 46.165.143.97
    Jul 28 09:50:01 pfsense sshlockout[2208]: sshlockout/webConfigurator v3.0 starting up
    Jul 28 09:50:06 pfsense sshd[51553]: Accepted keyboard-interactive/pam for root from 46.165.143.97 port 54146 ssh2</aten></aten></aten></aten></st160lt015></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></isa></at></thermal></serial></ata></ata></intel></ata></intel></isa></pci-isa></intel(r)></intel(r)></acpi></acpi></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></vga-compatible></intel></vga-compatible></acpi></acpi></power></acpi></acpi></intelr></software></version></intelr></lahf></nx></sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,xtpr,pdcm,movbe></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>
    


  • I forgot that the WAN interface is running on 100 MBit half duplex.
    Could it be that the interface is blinking while coming up and the route got lost or never set?

    Where can I put a sleep command for testing this?


Locked