The pfSense Store

Author Topic: constant PPPoE disconnection  (Read 2429 times)

0 Members and 1 Guest are viewing this topic.

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
constant PPPoE disconnection
« on: March 28, 2011, 07:26:57 am »
is it possible to disable gateway monitoring in a single WAN setup ? ??? with the gateway monitoring on, my PPPoE connection drops every 8 minutes without fail. :( my pfsense 2.0 RC1 64bit is installed as a VM under ESXi4.1, got open-vm-tools installed as well..
« Last Edit: March 30, 2011, 08:40:55 am by calvinz »

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: disable gateway monitoring
« Reply #1 on: March 29, 2011, 02:28:11 am »
I did further testing on the WAN link by doing a endless ping to the same monitoring IP ( 8.8.8.8 ) and it is still running after a day.  ??? I just have no idea why the WAN keeps dropping every 8 minutes on pfSense 2.0 RC1, system logs shows apinger alerting about the gateway being down and all .

Offline ermal

  • Administrator
  • Hero Member
  • *****
  • Posts: 3352
    • View Profile
Re: constant PPPoE disconnection
« Reply #2 on: March 29, 2011, 02:30:27 am »
Well can you show system log?!
Also you can disable state resetting under system->advanced which is the same as disabling monitoring.
If you disable state clearing you will just get notifications that a gateway is down in a single WAN setup.

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #3 on: March 29, 2011, 03:19:53 am »
Well can you show system log?!
Also you can disable state resetting under system->advanced which is the same as disabling monitoring.
If you disable state clearing you will just get notifications that a gateway is down in a single WAN setup.

I will reproduce the error and get the system logs here.

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #4 on: March 29, 2011, 09:11:12 am »
I have reinstalled a fresh pfSense 2.0 RC1 x64 VM according to the following steps :-

Step 1 : Installed using pfSense-2.0-RC1-amd64-20110226-1807.iso.gz
Step 2 : Configured 2 NICs (1 for WAN, 1 for LAN)
Step 3 : Configured to not use VLAN on initial setup
Step 4 : Specified em0 for WAN and em1 for LAN
Step 5 : Configured internal IP, DHCP, and revert back to HTTP webconfig on console
Step 6 : Configured hostname, time zone on General Settings
Step 7 : Configured WAN interface to dial PPPoE connection

Everything works fine until the last step. However if I rebooted the VM, the PPPoE connection drops every 8 minutes or so. Pretty sure from the above steps that the pfSense box is at a very clean state.  ???
« Last Edit: March 29, 2011, 09:13:14 pm by calvinz »

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #5 on: March 29, 2011, 09:19:47 am »
Code: [Select]
Mar 29 22:27:32 php: : Resyncing OpenVPN instances for interface WAN.
Mar 29 22:27:27 apinger: Starting Alarm Pinger, apinger(14843)
Mar 29 22:27:27 check_reload_status: reloading filter
Mar 29 22:27:26 apinger: Exiting on signal 15.
Mar 29 22:27:26 php: : ROUTING: change default route to 219.93.218.177
Mar 29 22:27:25 check_reload_status: Rewriting resolv.conf
Mar 29 22:27:20 check_reload_status: Rewriting resolv.conf
Mar 29 22:25:38 check_reload_status: reloading filter
Mar 29 22:25:28 apinger: ALARM: WAN(219.93.218.177) *** down ***
Mar 29 22:17:53 php: : Resyncing OpenVPN instances for interface WAN.
Mar 29 22:17:48 apinger: Starting Alarm Pinger, apinger(29535)
Mar 29 22:17:48 check_reload_status: reloading filter
Mar 29 22:17:47 apinger: Exiting on signal 15.
Mar 29 22:17:47 php: : ROUTING: change default route to 219.93.218.177
Mar 29 22:17:46 check_reload_status: Rewriting resolv.conf
Mar 29 22:17:39 check_reload_status: Rewriting resolv.conf
Mar 29 22:15:57 check_reload_status: reloading filter
Mar 29 22:15:47 apinger: ALARM: WAN(219.93.218.177) *** down ***
Mar 29 22:08:21 syslogd: kernel boot file is /boot/kernel/kernel
Mar 29 22:08:21 syslogd: exiting on signal 15
Mar 29 22:08:12 php: : Resyncing OpenVPN instances for interface WAN.
Mar 29 22:08:07 apinger: Starting Alarm Pinger, apinger(31234)
Mar 29 22:08:07 check_reload_status: reloading filter
Mar 29 22:08:06 apinger: Exiting on signal 15.
Mar 29 22:08:06 php: : ROUTING: change default route to 219.93.218.177
Mar 29 22:08:06 sshlockout[21122]: sshlockout/webConfigurator v3.0 starting up
Mar 29 22:08:06 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.85.111
Mar 29 22:08:06 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.85.111
Mar 29 22:08:05 check_reload_status: Rewriting resolv.conf
Mar 29 22:07:59 check_reload_status: Rewriting resolv.conf
Mar 29 22:06:16 check_reload_status: reloading filter
Mar 29 22:06:06 apinger: ALARM: WAN(219.93.218.177) *** down ***
Mar 29 21:58:38 check_reload_status: reloading filter
Mar 29 21:59:07 kernel: VMware memory control driver initialized
Mar 29 21:59:07 php: : The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was '[1301407147] unbound[28839:0] error: bind: address already in use [1301407147] unbound[28839:0] fatal error: could not open ports'
Mar 29 21:59:07 php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Mar 29 21:59:04 php: : Resyncing OpenVPN instances for interface WAN.
Mar 29 21:59:04 php: : Resyncing configuration for all packages.
Mar 29 21:59:04 miniupnpd[63143]: Listening for NAT-PMP traffic on port 5351
Mar 29 21:59:04 miniupnpd[63143]: Listening for NAT-PMP traffic on port 5351
Mar 29 21:59:04 miniupnpd[63143]: HTTP listening on port 2189
Mar 29 21:59:04 miniupnpd[63143]: HTTP listening on port 2189
Mar 29 21:59:04 php: miniupnpd: Starting service on interface: lan
Mar 29 21:59:04 php: : Creating rrd update script
Mar 29 21:58:59 apinger: Starting Alarm Pinger, apinger(43283)
Mar 29 21:58:27 check_reload_status: reloading filter
Mar 29 21:58:27 check_reload_status: updating all dyndns
Mar 29 21:58:27 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 29 21:58:27 dhcpd: All rights reserved.
Mar 29 21:58:27 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 29 21:58:27 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 29 21:58:26 php: : ROUTING: change default route to 219.93.218.177
Mar 29 21:58:26 php: : ROUTING: change default route to 219.93.218.177
Mar 29 21:58:25 apinger: No usable targets found, exiting
Mar 29 21:58:25 apinger: Starting Alarm Pinger, apinger(22569)
Mar 29 21:58:24 check_reload_status: Rewriting resolv.conf
Mar 29 21:58:23 kernel: pflog0: promiscuous mode enabled
Mar 29 21:58:23 kernel: Trying to mount root from ufs:/dev/da0s1a
Mar 29 21:58:23 kernel: da0: 10240MB (20971520 512 byte sectors: 255H 63S/T 1305C)
Mar 29 21:58:23 kernel: da0: Command Queueing enabled
Mar 29 21:58:23 kernel: da0: 300.000MB/s transfers
Mar 29 21:58:23 kernel: da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
Mar 29 21:58:23 kernel: da0 at mpt0 bus 0 scbus0 target 0 lun 0
Mar 29 21:58:23 kernel: acd0: DVDR <VMware Virtual IDE CDROM Drive/00000001> at ata1-master UDMA33
Mar 29 21:58:23 kernel: IPsec: Initialized Security Association Processing.
Mar 29 21:58:23 kernel: Timecounters tick every 10.000 msec
Mar 29 21:58:23 kernel: Timecounter "TSC" frequency 2832618174 Hz quality 800
Mar 29 21:58:23 kernel: acpi_throttle0: <ACPI CPU Throttling> on cpu0
Mar 29 21:58:23 kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Mar 29 21:58:23 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Mar 29 21:58:23 kernel: sc0: <System console> at flags 0x100 on isa0
Mar 29 21:58:23 kernel: orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xc9fff,0xdc000-0xdffff,0xe0000-0xe3fff on isa0
Mar 29 21:58:23 kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Mar 29 21:58:23 kernel: fdc0: [FILTER]
Mar 29 21:58:23 kernel: fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
Mar 29 21:58:23 kernel: uart1: [FILTER]
Mar 29 21:58:23 kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Mar 29 21:58:23 kernel: uart0: [FILTER]
Mar 29 21:58:23 kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Mar 29 21:58:23 kernel: ppi0: <Parallel I/O> on ppbus0
Mar 29 21:58:23 kernel: lpt0: Interrupt-driven port
Mar 29 21:58:23 kernel: lpt0: [ITHREAD]
Mar 29 21:58:23 kernel: lpt0: <Printer> on ppbus0
Mar 29 21:58:23 kernel: plip0: [ITHREAD]
Mar 29 21:58:23 kernel: plip0: <PLIP network interface> on ppbus0
Mar 29 21:58:23 kernel: ppbus0: <Parallel port bus> on ppc0
Mar 29 21:58:23 kernel: ppc0: [ITHREAD]
Mar 29 21:58:23 kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
Mar 29 21:58:23 kernel: ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
Mar 29 21:58:23 kernel: psm0: model IntelliMouse, device ID 3
Mar 29 21:58:23 kernel: psm0: [ITHREAD]
Mar 29 21:58:23 kernel: psm0: [GIANT-LOCKED]
Mar 29 21:58:23 kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
Mar 29 21:58:23 kernel: atkbd0: [ITHREAD]
Mar 29 21:58:23 kernel: atkbd0: [GIANT-LOCKED]
Mar 29 21:58:23 kernel: kbd0 at atkbd0
Mar 29 21:58:23 kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Mar 29 21:58:23 kernel: atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
Mar 29 21:58:23 kernel: atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Mar 29 21:58:23 kernel: acpi_acad0: <AC Adapter> on acpi0
Mar 29 21:58:23 kernel: pci34: <ACPI PCI bus> on pcib34
Mar 29 21:58:23 kernel: pcib34: <ACPI PCI-PCI bridge> at device 24.7 on pci0
Mar 29 21:58:23 kernel: pci33: <ACPI PCI bus> on pcib33
Mar 29 21:58:23 kernel: pcib33: <ACPI PCI-PCI bridge> at device 24.6 on pci0
Mar 29 21:58:23 kernel: pci32: <ACPI PCI bus> on pcib32
Mar 29 21:58:23 kernel: pcib32: <ACPI PCI-PCI bridge> at device 24.5 on pci0
Mar 29 21:58:23 kernel: pci31: <ACPI PCI bus> on pcib31
Mar 29 21:58:23 kernel: pcib31: <ACPI PCI-PCI bridge> at device 24.4 on pci0
Mar 29 21:58:23 kernel: pci30: <ACPI PCI bus> on pcib30
Mar 29 21:58:23 kernel: pcib30: <ACPI PCI-PCI bridge> at device 24.3 on pci0
Mar 29 21:58:23 kernel: pci29: <ACPI PCI bus> on pcib29
Mar 29 21:58:23 kernel: pcib29: <ACPI PCI-PCI bridge> at device 24.2 on pci0
Mar 29 21:58:23 kernel: pci28: <ACPI PCI bus> on pcib28
Mar 29 21:58:23 kernel: pcib28: <ACPI PCI-PCI bridge> at device 24.1 on pci0
Mar 29 21:58:23 kernel: pci27: <ACPI PCI bus> on pcib27
Mar 29 21:58:23 kernel: pcib27: <ACPI PCI-PCI bridge> at device 24.0 on pci0
Mar 29 21:58:23 kernel: pci26: <ACPI PCI bus> on pcib26
Mar 29 21:58:23 kernel: pcib26: <ACPI PCI-PCI bridge> at device 23.7 on pci0
Mar 29 21:58:23 kernel: pci25: <ACPI PCI bus> on pcib25
Mar 29 21:58:23 kernel: pcib25: <ACPI PCI-PCI bridge> at device 23.6 on pci0
Mar 29 21:58:23 kernel: pci24: <ACPI PCI bus> on pcib24
Mar 29 21:58:23 kernel: pcib24: <ACPI PCI-PCI bridge> at device 23.5 on pci0
Mar 29 21:58:23 kernel: pci23: <ACPI PCI bus> on pcib23
Mar 29 21:58:23 kernel: pcib23: <ACPI PCI-PCI bridge> at device 23.4 on pci0
Mar 29 21:58:23 kernel: pci22: <ACPI PCI bus> on pcib22
Mar 29 21:58:23 kernel: pcib22: <ACPI PCI-PCI bridge> at device 23.3 on pci0
Mar 29 21:58:23 kernel: pci21: <ACPI PCI bus> on pcib21
Mar 29 21:58:23 kernel: pcib21: <ACPI PCI-PCI bridge> at device 23.2 on pci0
Mar 29 21:58:23 kernel: pci20: <ACPI PCI bus> on pcib20
Mar 29 21:58:23 kernel: pcib20: <ACPI PCI-PCI bridge> at device 23.1 on pci0
Mar 29 21:58:23 kernel: pci19: <ACPI PCI bus> on pcib19
Mar 29 21:58:23 kernel: pcib19: <ACPI PCI-PCI bridge> at device 23.0 on pci0
Mar 29 21:58:23 kernel: pci18: <ACPI PCI bus> on pcib18
Mar 29 21:58:23 kernel: pcib18: <ACPI PCI-PCI bridge> at device 22.7 on pci0
Mar 29 21:58:23 kernel: pci17: <ACPI PCI bus> on pcib17
Mar 29 21:58:23 kernel: pcib17: <ACPI PCI-PCI bridge> at device 22.6 on pci0
Mar 29 21:58:23 kernel: pci16: <ACPI PCI bus> on pcib16
Mar 29 21:58:23 kernel: pcib16: <ACPI PCI-PCI bridge> at device 22.5 on pci0
Mar 29 21:58:23 kernel: pci15: <ACPI PCI bus> on pcib15
Mar 29 21:58:23 kernel: pcib15: <ACPI PCI-PCI bridge> at device 22.4 on pci0
Mar 29 21:58:23 kernel: pci14: <ACPI PCI bus> on pcib14
Mar 29 21:58:23 kernel: pcib14: <ACPI PCI-PCI bridge> at device 22.3 on pci0
Mar 29 21:58:23 kernel: pci13: <ACPI PCI bus> on pcib13
Mar 29 21:58:23 kernel: pcib13: <ACPI PCI-PCI bridge> at device 22.2 on pci0
Mar 29 21:58:23 kernel: pci12: <ACPI PCI bus> on pcib12
Mar 29 21:58:23 kernel: pcib12: <ACPI PCI-PCI bridge> at device 22.1 on pci0
Mar 29 21:58:23 kernel: pci11: <ACPI PCI bus> on pcib11
Mar 29 21:58:23 kernel: pcib11: <ACPI PCI-PCI bridge> at device 22.0 on pci0
Mar 29 21:58:23 kernel: pci10: <ACPI PCI bus> on pcib10
Mar 29 21:58:23 kernel: pcib10: <ACPI PCI-PCI bridge> at device 21.7 on pci0
Mar 29 21:58:23 kernel: pci9: <ACPI PCI bus> on pcib9
Mar 29 21:58:23 kernel: pcib9: <ACPI PCI-PCI bridge> at device 21.6 on pci0
Mar 29 21:58:23 kernel: pci8: <ACPI PCI bus> on pcib8
Mar 29 21:58:23 kernel: pcib8: <ACPI PCI-PCI bridge> at device 21.5 on pci0
Mar 29 21:58:23 kernel: pci7: <ACPI PCI bus> on pcib7
Mar 29 21:58:23 kernel: pcib7: <ACPI PCI-PCI bridge> at device 21.4 on pci0
Mar 29 21:58:23 kernel: pci6: <ACPI PCI bus> on pcib6
Mar 29 21:58:23 kernel: pcib6: <ACPI PCI-PCI bridge> at device 21.3 on pci0
Mar 29 21:58:23 kernel: pci5: <ACPI PCI bus> on pcib5
Mar 29 21:58:23 kernel: pcib5: <ACPI PCI-PCI bridge> at device 21.2 on pci0
Mar 29 21:58:23 kernel: pci4: <ACPI PCI bus> on pcib4
Mar 29 21:58:23 kernel: pcib4: <ACPI PCI-PCI bridge> at device 21.1 on pci0
Mar 29 21:58:23 kernel: mpt0: MPI Version=1.5.0.0
Mar 29 21:58:23 kernel: mpt0: [ITHREAD]
Mar 29 21:58:23 kernel: mpt0: <LSILogic SAS/SATA Adapter> port 0x4000-0x40ff mem 0xd9c04000-0xd9c07fff,0xd9c10000-0xd9c1ffff irq 18 at device 0.0 on pci3
Mar 29 21:58:23 kernel: pci3: <ACPI PCI bus> on pcib3
Mar 29 21:58:23 kernel: pcib3: <ACPI PCI-PCI bridge> at device 21.0 on pci0
Mar 29 21:58:23 kernel: em1: [FILTER]
Mar 29 21:58:23 kernel: em1: Memory Access and/or Bus Master bits were not set!
Mar 29 21:58:23 kernel: em1: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0x2040-0x207f mem 0xd8840000-0xd885ffff,0xd8810000-0xd881ffff irq 19 at device 1.0 on pci2
Mar 29 21:58:23 kernel: em0: [FILTER]
Mar 29 21:58:23 kernel: em0: Memory Access and/or Bus Master bits were not set!
Mar 29 21:58:23 kernel: em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0x2000-0x203f mem 0xd8820000-0xd883ffff,0xd8800000-0xd880ffff irq 18 at device 0.0 on pci2
Mar 29 21:58:23 kernel: pci2: <ACPI PCI bus> on pcib2
Mar 29 21:58:23 kernel: pcib2: <ACPI PCI-PCI bridge> at device 17.0 on pci0
Mar 29 21:58:23 kernel: vgapci0: <VGA-compatible display> port 0x10d0-0x10df mem 0xd4000000-0xd7ffffff,0xd8000000-0xd87fffff irq 16 at device 15.0 on pci0
Mar 29 21:58:23 kernel: pci0: <base peripheral> at device 7.7 (no driver attached)
Mar 29 21:58:23 kernel: pci0: <bridge> at device 7.3 (no driver attached)
Mar 29 21:58:23 kernel: ata1: [ITHREAD]
Mar 29 21:58:23 kernel: ata1: <ATA channel 1> on atapci0
Mar 29 21:58:23 kernel: ata0: [ITHREAD]
Mar 29 21:58:23 kernel: ata0: <ATA channel 0> on atapci0
Mar 29 21:58:23 kernel: atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x10c0-0x10cf at device 7.1 on pci0
Mar 29 21:58:23 kernel: isa0: <ISA bus> on isab0
Mar 29 21:58:23 kernel: isab0: <PCI-ISA bridge> at device 7.0 on pci0
Mar 29 21:58:23 kernel: pci1: <ACPI PCI bus> on pcib1
Mar 29 21:58:23 kernel: pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
Mar 29 21:58:23 kernel: pci0: <ACPI PCI bus> on pcib0
Mar 29 21:58:23 kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Mar 29 21:58:23 kernel: cpu0: <ACPI CPU> on acpi0
Mar 29 21:58:23 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
Mar 29 21:58:23 kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
Mar 29 21:58:23 kernel: acpi0: Power Button (fixed)
Mar 29 21:58:23 kernel: acpi0: [ITHREAD]
Mar 29 21:58:23 kernel: acpi0: <INTEL 440BX> on motherboard
Mar 29 21:58:23 kernel: padlock0: No ACE support.
Mar 29 21:58:23 kernel: cryptosoft0: <software crypto> on motherboard
Mar 29 21:58:23 kernel: kbd1 at kbdmux0
Mar 29 21:58:23 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80469700, 0) error 1
Mar 29 21:58:23 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Mar 29 21:58:23 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Mar 29 21:58:23 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80469660, 0) error 1
Mar 29 21:58:23 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Mar 29 21:58:23 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Mar 29 21:58:23 kernel: module_register_init: MOD_LOAD (wpi_fw, 0xffffffff8064d130, 0) error 1
Mar 29 21:58:23 kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
Mar 29 21:58:23 kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
Mar 29 21:58:23 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff804697a0, 0) error 1
Mar 29 21:58:23 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Mar 29 21:58:23 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Mar 29 21:58:23 kernel: wlan: mac acl policy registered
Mar 29 21:58:23 kernel: ioapic0 <Version 1.1> irqs 0-23 on motherboard
Mar 29 21:58:23 kernel: MADT: Forcing active-low polarity and level trigger for SCI
Mar 29 21:58:23 kernel: ACPI APIC Table: <PTLTD APIC >
Mar 29 21:58:23 kernel: avail memory = 1012514816 (965 MB)
Mar 29 21:58:23 kernel: real memory = 1073741824 (1024 MB)
Mar 29 21:58:23 kernel: TSC: P-state invariant
Mar 29 21:58:23 kernel: AMD Features2=0x1<LAHF>
Mar 29 21:58:23 kernel: AMD Features=0x20100800<SYSCALL,NX,LM>
Mar 29 21:58:23 kernel: Features2=0x80082201<SSE3,SSSE3,CX16,SSE4.1,<b31>>
Mar 29 21:58:23 kernel: Features=0xfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS>
Mar 29 21:58:23 kernel: Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Stepping = 10
Mar 29 21:58:23 kernel: CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (2832.62-MHz K8-class CPU)
Mar 29 21:58:23 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Mar 29 21:58:23 kernel: root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 amd64
Mar 29 21:58:23 kernel: FreeBSD 8.1-RELEASE-p2 #0: Sat Feb 26 17:29:13 EST 2011
Mar 29 21:58:23 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Mar 29 21:58:23 kernel: The Regents of the University of California. All rights reserved.
Mar 29 21:58:23 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Mar 29 21:58:23 kernel: Copyright (c) 1992-2010 The FreeBSD Project.
Mar 29 21:58:23 kernel: Rebooting...
Mar 29 21:58:23 kernel: Uptime: 13m21s
Mar 29 21:58:23 kernel: All buffers synced.
Mar 29 21:58:23 kernel: Syncing disks, vnodes remaining...0 0 done
Mar 29 21:58:23 kernel: Waiting (max 60 seconds) for system process `syncer' to stop...
Mar 29 21:58:23 kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Mar 29 21:58:23 kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done
Mar 29 21:58:23 kernel: pflog0: promiscuous mode disabled
Mar 29 21:58:23 syslogd: kernel boot file is /boot/kernel/kernel

as you can see.. it is disconnecting itself at a consistent rate of 8mins

Code: [Select]
Mar 29 22:27:26 ppp: [wan] IFACE: Up event
Mar 29 22:27:25 ppp: [wan] 175.139.30.21 -> 219.93.218.177
Mar 29 22:27:25 ppp: [wan] IPCP: LayerUp
Mar 29 22:27:25 ppp: [wan] IPCP: state change Ack-Rcvd --> Opened
Mar 29 22:27:25 ppp: [wan] IPADDR 219.93.218.177
Mar 29 22:27:25 ppp: [wan] IPCP: SendConfigAck #138
Mar 29 22:27:25 ppp: [wan] 219.93.218.177 is OK
Mar 29 22:27:25 ppp: [wan] IPADDR 219.93.218.177
Mar 29 22:27:25 ppp: [wan] IPCP: rec'd Configure Request #138 (Ack-Rcvd)
Mar 29 22:27:25 ppp: [wan] IPCP: state change Req-Sent --> Ack-Rcvd
Mar 29 22:27:25 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:27:25 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:27:25 ppp: [wan] IPADDR 175.139.30.21
Mar 29 22:27:25 ppp: [wan] IPCP: rec'd Configure Ack #15 (Req-Sent)
Mar 29 22:27:25 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:27:25 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:27:25 ppp: [wan] IPADDR 175.139.30.21
Mar 29 22:27:25 ppp: [wan] IPCP: SendConfigReq #15
Mar 29 22:27:25 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:27:25 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:27:25 ppp: [wan] 175.139.30.21 is OK
Mar 29 22:27:25 ppp: [wan] IPADDR 175.139.30.21
Mar 29 22:27:25 ppp: [wan] IPCP: rec'd Configure Nak #14 (Req-Sent)
Mar 29 22:27:25 ppp: [wan] SECDNS 0.0.0.0
Mar 29 22:27:25 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 22:27:25 ppp: [wan] IPADDR 0.0.0.0
Mar 29 22:27:25 ppp: [wan] IPCP: SendConfigReq #14
Mar 29 22:27:25 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 22:27:25 ppp: [wan] IPCP: rec'd Configure Reject #13 (Req-Sent)
Mar 29 22:27:25 ppp: [wan] SECDNS 0.0.0.0
Mar 29 22:27:25 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 22:27:25 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 22:27:25 ppp: [wan] IPADDR 0.0.0.0
Mar 29 22:27:25 ppp: [wan] IPCP: SendConfigReq #13
Mar 29 22:27:25 ppp: [wan] IPCP: state change Starting --> Req-Sent
Mar 29 22:27:25 ppp: [wan] IPCP: Up event
Mar 29 22:27:25 ppp: [wan] IPCP: LayerStart
Mar 29 22:27:25 ppp: [wan] IPCP: state change Initial --> Starting
Mar 29 22:27:25 ppp: [wan] IPCP: Open event
Mar 29 22:27:25 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Mar 29 22:27:25 ppp: [wan_link0] Link: Join bundle "wan"
Mar 29 22:27:25 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Mar 29 22:27:25 ppp: [wan_link0] LCP: authorization successful
Mar 29 22:27:25 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
Mar 29 22:27:25 ppp: [wan_link0] LCP: LayerUp
Mar 29 22:27:25 ppp: [wan_link0] PAP: sending REQUEST #1 len: 34
Mar 29 22:27:25 ppp: [wan_link0] PAP: using authname "hiddenusername@unifi"
Mar 29 22:27:25 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Mar 29 22:27:25 ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Mar 29 22:27:25 ppp: [wan_link0] MAGICNUM b9bc94e0
Mar 29 22:27:25 ppp: [wan_link0] MRU 1492
Mar 29 22:27:25 ppp: [wan_link0] PROTOCOMP
Mar 29 22:27:25 ppp: [wan_link0] LCP: rec'd Configure Ack #7 (Ack-Sent)
Mar 29 22:27:25 ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Mar 29 22:27:25 ppp: [wan_link0] MAGICNUM 0a8c0325
Mar 29 22:27:25 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 22:27:25 ppp: [wan_link0] MRU 1492
Mar 29 22:27:25 ppp: [wan_link0] LCP: SendConfigAck #236
Mar 29 22:27:25 ppp: [wan_link0] MAGICNUM 0a8c0325
Mar 29 22:27:25 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 22:27:25 ppp: [wan_link0] MRU 1492
Mar 29 22:27:25 ppp: [wan_link0] LCP: rec'd Configure Request #236 (Req-Sent)
Mar 29 22:27:24 ppp: [wan_link0] MAGICNUM b9bc94e0
Mar 29 22:27:24 ppp: [wan_link0] MRU 1492
Mar 29 22:27:24 ppp: [wan_link0] PROTOCOMP
Mar 29 22:27:24 ppp: [wan_link0] LCP: SendConfigReq #7
Mar 29 22:27:24 ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Mar 29 22:27:24 ppp: [wan_link0] LCP: Up event
Mar 29 22:27:24 ppp: [wan_link0] Link: UP event
Mar 29 22:27:24 ppp: [wan_link0] PPPoE: connection successful
Mar 29 22:27:24 ppp: PPPoE: rec'd ACNAME "ERXKLJ22"
Mar 29 22:27:24 ppp: [wan_link0] PPPoE: Connecting to '*'
Mar 29 22:27:24 ppp: [wan_link0] Link: reconnection attempt 1
Mar 29 22:27:22 ppp: [wan_link0] Link: reconnection attempt 1 in 2 seconds
Mar 29 22:27:22 ppp: [wan_link0] LCP: LayerStart
Mar 29 22:27:22 ppp: [wan_link0] LCP: state change Stopped --> Starting
Mar 29 22:27:22 ppp: [wan_link0] LCP: Down event
Mar 29 22:27:22 ppp: [wan_link0] Link: DOWN event
Mar 29 22:27:22 ppp: [wan_link0] PPPoE: connection closed
Mar 29 22:27:22 ppp: [wan_link0] LCP: LayerFinish
Mar 29 22:27:22 ppp: [wan_link0] LCP: state change Stopping --> Stopped
Mar 29 22:27:20 ppp: [wan_link0] LCP: LayerDown
Mar 29 22:27:20 ppp: [wan_link0] LCP: SendTerminateAck #6
Mar 29 22:27:20 ppp: [wan] IPCP: state change Closing --> Initial
Mar 29 22:27:20 ppp: [wan] Bundle: No NCPs left. Closing links...
Mar 29 22:27:20 ppp: [wan] IPCP: LayerFinish
Mar 29 22:27:20 ppp: [wan] IPCP: Down event
Mar 29 22:27:20 ppp: [wan] IFACE: Down event
Mar 29 22:27:20 ppp: [wan] IPCP: LayerDown
Mar 29 22:27:20 ppp: [wan] IPCP: SendTerminateReq #12
Mar 29 22:27:20 ppp: [wan] IPCP: state change Opened --> Closing
Mar 29 22:27:20 ppp: [wan] IPCP: Close event
Mar 29 22:27:20 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Mar 29 22:27:20 ppp: [wan_link0] Link: Leave bundle "wan"
Mar 29 22:27:20 ppp: [wan_link0] LCP: state change Opened --> Stopping
Mar 29 22:27:20 ppp: [wan_link0] LCP: rec'd Terminate Request #244 (Opened)
Mar 29 22:17:47 ppp: [wan] IFACE: Up event
Mar 29 22:17:46 ppp: [wan] 175.136.186.104 -> 219.93.218.177
Mar 29 22:17:46 ppp: [wan] IPCP: LayerUp
Mar 29 22:17:46 ppp: [wan] IPCP: state change Ack-Sent --> Opened
Mar 29 22:17:46 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:17:46 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:17:46 ppp: [wan] IPADDR 175.136.186.104
Mar 29 22:17:46 ppp: [wan] IPCP: rec'd Configure Ack #11 (Ack-Sent)
Mar 29 22:17:46 ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Mar 29 22:17:46 ppp: [wan] IPADDR 219.93.218.177
Mar 29 22:17:46 ppp: [wan] IPCP: SendConfigAck #171
Mar 29 22:17:46 ppp: [wan] 219.93.218.177 is OK
Mar 29 22:17:46 ppp: [wan] IPADDR 219.93.218.177
Mar 29 22:17:46 ppp: [wan] IPCP: rec'd Configure Request #171 (Req-Sent)
Mar 29 22:17:46 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:17:46 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:17:46 ppp: [wan] IPADDR 175.136.186.104
Mar 29 22:17:46 ppp: [wan] IPCP: SendConfigReq #11
Mar 29 22:17:46 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:17:46 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:17:46 ppp: [wan] 175.136.186.104 is OK
Mar 29 22:17:46 ppp: [wan] IPADDR 175.136.186.104
Mar 29 22:17:46 ppp: [wan] IPCP: rec'd Configure Nak #10 (Req-Sent)
Mar 29 22:17:46 ppp: [wan] SECDNS 0.0.0.0
Mar 29 22:17:46 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 22:17:46 ppp: [wan] IPADDR 0.0.0.0
Mar 29 22:17:46 ppp: [wan] IPCP: SendConfigReq #10
Mar 29 22:17:46 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 22:17:46 ppp: [wan] IPCP: rec'd Configure Reject #9 (Req-Sent)
Mar 29 22:17:46 ppp: [wan] SECDNS 0.0.0.0
Mar 29 22:17:46 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 22:17:46 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 22:17:46 ppp: [wan] IPADDR 0.0.0.0
Mar 29 22:17:46 ppp: [wan] IPCP: SendConfigReq #9
Mar 29 22:17:46 ppp: [wan] IPCP: state change Starting --> Req-Sent
Mar 29 22:17:46 ppp: [wan] IPCP: Up event
Mar 29 22:17:46 ppp: [wan] IPCP: LayerStart
Mar 29 22:17:46 ppp: [wan] IPCP: state change Initial --> Starting
Mar 29 22:17:46 ppp: [wan] IPCP: Open event
Mar 29 22:17:46 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Mar 29 22:17:46 ppp: [wan_link0] Link: Join bundle "wan"
Mar 29 22:17:46 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Mar 29 22:17:46 ppp: [wan_link0] LCP: authorization successful
Mar 29 22:17:46 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
Mar 29 22:17:45 ppp: [wan_link0] LCP: LayerUp
Mar 29 22:17:45 ppp: [wan_link0] PAP: sending REQUEST #1 len: 34
Mar 29 22:17:45 ppp: [wan_link0] PAP: using authname "hiddenusername@unifi"
Mar 29 22:17:45 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Mar 29 22:17:45 ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Mar 29 22:17:45 ppp: [wan_link0] MAGICNUM 188f6200
Mar 29 22:17:45 ppp: [wan_link0] MRU 1492
Mar 29 22:17:45 ppp: [wan_link0] PROTOCOMP
Mar 29 22:17:45 ppp: [wan_link0] LCP: rec'd Configure Ack #5 (Ack-Sent)
Mar 29 22:17:45 ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Mar 29 22:17:45 ppp: [wan_link0] MAGICNUM 7c54906b
Mar 29 22:17:45 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 22:17:45 ppp: [wan_link0] MRU 1492
Mar 29 22:17:45 ppp: [wan_link0] LCP: SendConfigAck #240
Mar 29 22:17:45 ppp: [wan_link0] MAGICNUM 7c54906b
Mar 29 22:17:45 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 22:17:45 ppp: [wan_link0] MRU 1492
Mar 29 22:17:45 ppp: [wan_link0] LCP: rec'd Configure Request #240 (Req-Sent)
Mar 29 22:17:45 ppp: [wan_link0] MAGICNUM 188f6200
Mar 29 22:17:45 ppp: [wan_link0] MRU 1492
Mar 29 22:17:45 ppp: [wan_link0] PROTOCOMP
Mar 29 22:17:45 ppp: [wan_link0] LCP: SendConfigReq #5
Mar 29 22:17:45 ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Mar 29 22:17:45 ppp: [wan_link0] LCP: Up event
Mar 29 22:17:45 ppp: [wan_link0] Link: UP event
Mar 29 22:17:45 ppp: [wan_link0] PPPoE: connection successful
Mar 29 22:17:45 ppp: PPPoE: rec'd ACNAME "ERXKLJ22"
Mar 29 22:17:45 ppp: [wan_link0] PPPoE: Connecting to '*'
Mar 29 22:17:45 ppp: [wan_link0] Link: reconnection attempt 1
Mar 29 22:17:41 ppp: [wan_link0] Link: reconnection attempt 1 in 4 seconds
Mar 29 22:17:41 ppp: [wan_link0] LCP: LayerStart
Mar 29 22:17:41 ppp: [wan_link0] LCP: state change Stopped --> Starting
Mar 29 22:17:41 ppp: [wan_link0] LCP: Down event
Mar 29 22:17:41 ppp: [wan_link0] Link: DOWN event
Mar 29 22:17:41 ppp: [wan_link0] PPPoE: connection closed
Mar 29 22:17:41 ppp: [wan_link0] LCP: LayerFinish
Mar 29 22:17:41 ppp: [wan_link0] LCP: state change Stopping --> Stopped
Mar 29 22:17:39 ppp: [wan_link0] LCP: LayerDown
Mar 29 22:17:39 ppp: [wan_link0] LCP: SendTerminateAck #4
Mar 29 22:17:39 ppp: [wan] IPCP: state change Closing --> Initial
Mar 29 22:17:39 ppp: [wan] Bundle: No NCPs left. Closing links...
Mar 29 22:17:39 ppp: [wan] IPCP: LayerFinish
Mar 29 22:17:39 ppp: [wan] IPCP: Down event
Mar 29 22:17:39 ppp: [wan] IFACE: Down event
Mar 29 22:17:39 ppp: [wan] IPCP: LayerDown
Mar 29 22:17:39 ppp: [wan] IPCP: SendTerminateReq #8
Mar 29 22:17:39 ppp: [wan] IPCP: state change Opened --> Closing
Mar 29 22:17:39 ppp: [wan] IPCP: Close event
Mar 29 22:17:39 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Mar 29 22:17:39 ppp: [wan_link0] Link: Leave bundle "wan"
Mar 29 22:17:39 ppp: [wan_link0] LCP: state change Opened --> Stopping
Mar 29 22:17:39 ppp: [wan_link0] LCP: rec'd Terminate Request #249 (Opened)
Mar 29 22:08:06 ppp: [wan] IFACE: Up event
Mar 29 22:08:05 ppp: [wan] 175.139.24.89 -> 219.93.218.177
Mar 29 22:08:05 ppp: [wan] IPCP: LayerUp
Mar 29 22:08:05 ppp: [wan] IPCP: state change Ack-Rcvd --> Opened
Mar 29 22:08:05 ppp: [wan] IPADDR 219.93.218.177
Mar 29 22:08:05 ppp: [wan] IPCP: SendConfigAck #84
Mar 29 22:08:05 ppp: [wan] 219.93.218.177 is OK
Mar 29 22:08:05 ppp: [wan] IPADDR 219.93.218.177
Mar 29 22:08:05 ppp: [wan] IPCP: rec'd Configure Request #84 (Ack-Rcvd)
Mar 29 22:08:05 ppp: [wan] IPCP: state change Req-Sent --> Ack-Rcvd
Mar 29 22:08:05 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:08:05 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:08:05 ppp: [wan] IPADDR 175.139.24.89
Mar 29 22:08:05 ppp: [wan] IPCP: rec'd Configure Ack #7 (Req-Sent)
Mar 29 22:08:05 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:08:05 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:08:05 ppp: [wan] IPADDR 175.139.24.89
Mar 29 22:08:05 ppp: [wan] IPCP: SendConfigReq #7
Mar 29 22:08:05 ppp: [wan] SECDNS 202.188.1.5
Mar 29 22:08:05 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 22:08:05 ppp: [wan] 175.139.24.89 is OK
Mar 29 22:08:05 ppp: [wan] IPADDR 175.139.24.89
Mar 29 22:08:05 ppp: [wan] IPCP: rec'd Configure Nak #6 (Req-Sent)
Mar 29 22:08:05 ppp: [wan] SECDNS 0.0.0.0
Mar 29 22:08:05 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 22:08:05 ppp: [wan] IPADDR 0.0.0.0
Mar 29 22:08:05 ppp: [wan] IPCP: SendConfigReq #6
Mar 29 22:08:05 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 22:08:05 ppp: [wan] IPCP: rec'd Configure Reject #5 (Req-Sent)
Mar 29 22:08:05 ppp: [wan] SECDNS 0.0.0.0
Mar 29 22:08:05 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 22:08:05 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 22:08:05 ppp: [wan] IPADDR 0.0.0.0
Mar 29 22:08:05 ppp: [wan] IPCP: SendConfigReq #5
Mar 29 22:08:05 ppp: [wan] IPCP: state change Starting --> Req-Sent
Mar 29 22:08:05 ppp: [wan] IPCP: Up event
Mar 29 22:08:05 ppp: [wan] IPCP: LayerStart
Mar 29 22:08:05 ppp: [wan] IPCP: state change Initial --> Starting
Mar 29 22:08:05 ppp: [wan] IPCP: Open event
Mar 29 22:08:05 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Mar 29 22:08:05 ppp: [wan_link0] Link: Join bundle "wan"
Mar 29 22:08:05 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Mar 29 22:08:05 ppp: [wan_link0] LCP: authorization successful
Mar 29 22:08:05 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
Mar 29 22:08:04 ppp: [wan_link0] LCP: LayerUp
Mar 29 22:08:04 ppp: [wan_link0] PAP: sending REQUEST #1 len: 34
Mar 29 22:08:04 ppp: [wan_link0] PAP: using authname "hiddenusername@unifi"
Mar 29 22:08:04 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Mar 29 22:08:04 ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Mar 29 22:08:04 ppp: [wan_link0] MAGICNUM f8e55540
Mar 29 22:08:04 ppp: [wan_link0] MRU 1492
Mar 29 22:08:04 ppp: [wan_link0] PROTOCOMP
Mar 29 22:08:04 ppp: [wan_link0] LCP: rec'd Configure Ack #3 (Ack-Sent)
Mar 29 22:08:04 ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Mar 29 22:08:04 ppp: [wan_link0] MAGICNUM 00f84efc
Mar 29 22:08:04 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 22:08:04 ppp: [wan_link0] MRU 1492
Mar 29 22:08:04 ppp: [wan_link0] LCP: SendConfigAck #245
Mar 29 22:08:04 ppp: [wan_link0] MAGICNUM 00f84efc
Mar 29 22:08:04 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 22:08:04 ppp: [wan_link0] MRU 1492
Mar 29 22:08:04 ppp: [wan_link0] LCP: rec'd Configure Request #245 (Req-Sent)
Mar 29 22:08:04 ppp: [wan_link0] MAGICNUM f8e55540
Mar 29 22:08:04 ppp: [wan_link0] MRU 1492
Mar 29 22:08:04 ppp: [wan_link0] PROTOCOMP
Mar 29 22:08:04 ppp: [wan_link0] LCP: SendConfigReq #3
Mar 29 22:08:04 ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Mar 29 22:08:04 ppp: [wan_link0] LCP: Up event
Mar 29 22:08:04 ppp: [wan_link0] Link: UP event
Mar 29 22:08:04 ppp: [wan_link0] PPPoE: connection successful
Mar 29 22:08:04 ppp: PPPoE: rec'd ACNAME "ERXKLJ22"
Mar 29 22:08:04 ppp: [wan_link0] PPPoE: Connecting to '*'
Mar 29 22:08:04 ppp: [wan_link0] Link: reconnection attempt 1
Mar 29 22:08:01 ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds
Mar 29 22:08:01 ppp: [wan_link0] LCP: LayerStart
Mar 29 22:08:01 ppp: [wan_link0] LCP: state change Stopped --> Starting
Mar 29 22:08:01 ppp: [wan_link0] LCP: Down event
Mar 29 22:08:01 ppp: [wan_link0] Link: DOWN event
Mar 29 22:08:01 ppp: [wan_link0] PPPoE: connection closed
Mar 29 22:08:01 ppp: [wan_link0] LCP: LayerFinish
Mar 29 22:08:01 ppp: [wan_link0] LCP: state change Stopping --> Stopped
Mar 29 22:07:59 ppp: [wan_link0] LCP: LayerDown
Mar 29 22:07:59 ppp: [wan_link0] LCP: SendTerminateAck #2
Mar 29 22:07:59 ppp: [wan] IPCP: state change Closing --> Initial
Mar 29 22:07:59 ppp: [wan] Bundle: No NCPs left. Closing links...
Mar 29 22:07:59 ppp: [wan] IPCP: LayerFinish
Mar 29 22:07:59 ppp: [wan] IPCP: Down event
Mar 29 22:07:59 ppp: [wan] IFACE: Down event
Mar 29 22:07:59 ppp: [wan] IPCP: LayerDown
Mar 29 22:07:59 ppp: [wan] IPCP: SendTerminateReq #4
Mar 29 22:07:59 ppp: [wan] IPCP: state change Opened --> Closing
Mar 29 22:07:59 ppp: [wan] IPCP: Close event
Mar 29 22:07:59 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Mar 29 22:07:59 ppp: [wan_link0] Link: Leave bundle "wan"
Mar 29 22:07:59 ppp: [wan_link0] LCP: state change Opened --> Stopping
Mar 29 22:07:59 ppp: [wan_link0] LCP: rec'd Terminate Request #122 (Opened)
Mar 29 21:58:26 ppp: [wan] IFACE: Up event
Mar 29 21:58:24 ppp: [wan] 175.139.27.26 -> 219.93.218.177
Mar 29 21:58:24 ppp: [wan] IPCP: LayerUp
Mar 29 21:58:24 ppp: [wan] IPCP: state change Ack-Sent --> Opened
Mar 29 21:58:24 ppp: [wan] SECDNS 202.188.1.5
Mar 29 21:58:24 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 21:58:24 ppp: [wan] IPADDR 175.139.27.26
Mar 29 21:58:24 ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Mar 29 21:58:24 ppp: [wan] SECDNS 202.188.1.5
Mar 29 21:58:24 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 21:58:24 ppp: [wan] IPADDR 175.139.27.26
Mar 29 21:58:24 ppp: [wan] IPCP: SendConfigReq #3
Mar 29 21:58:24 ppp: [wan] SECDNS 202.188.1.5
Mar 29 21:58:24 ppp: [wan] PRIDNS 202.188.0.133
Mar 29 21:58:24 ppp: [wan] 175.139.27.26 is OK
Mar 29 21:58:24 ppp: [wan] IPADDR 175.139.27.26
Mar 29 21:58:24 ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
Mar 29 21:58:24 ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Mar 29 21:58:24 ppp: [wan] IPADDR 219.93.218.177
Mar 29 21:58:24 ppp: [wan] IPCP: SendConfigAck #56
Mar 29 21:58:24 ppp: [wan] 219.93.218.177 is OK
Mar 29 21:58:24 ppp: [wan] IPADDR 219.93.218.177
Mar 29 21:58:24 ppp: [wan] IPCP: rec'd Configure Request #56 (Req-Sent)
Mar 29 21:58:24 ppp: [wan] SECDNS 0.0.0.0
Mar 29 21:58:24 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 21:58:24 ppp: [wan] IPADDR 0.0.0.0
Mar 29 21:58:24 ppp: [wan] IPCP: SendConfigReq #2
Mar 29 21:58:24 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 21:58:24 ppp: [wan] IPCP: rec'd Configure Reject #1 (Req-Sent)
Mar 29 21:58:24 ppp: [wan] SECDNS 0.0.0.0
Mar 29 21:58:24 ppp: [wan] PRIDNS 0.0.0.0
Mar 29 21:58:24 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 29 21:58:24 ppp: [wan] IPADDR 0.0.0.0
Mar 29 21:58:24 ppp: [wan] IPCP: SendConfigReq #1
Mar 29 21:58:24 ppp: [wan] IPCP: state change Starting --> Req-Sent
Mar 29 21:58:24 ppp: [wan] IPCP: Up event
Mar 29 21:58:24 ppp: [wan] IPCP: LayerStart
Mar 29 21:58:24 ppp: [wan] IPCP: state change Initial --> Starting
Mar 29 21:58:24 ppp: [wan] IPCP: Open event
Mar 29 21:58:24 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Mar 29 21:58:24 ppp: [wan_link0] Link: Join bundle "wan"
Mar 29 21:58:24 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Mar 29 21:58:24 ppp: [wan_link0] LCP: authorization successful
Mar 29 21:58:24 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
Mar 29 21:58:24 ppp: [wan_link0] LCP: LayerUp
Mar 29 21:58:24 ppp: [wan_link0] PAP: sending REQUEST #1 len: 34
Mar 29 21:58:24 ppp: [wan_link0] PAP: using authname "hiddenusername@unifi"
Mar 29 21:58:24 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Mar 29 21:58:24 ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Mar 29 21:58:24 ppp: [wan_link0] MAGICNUM b377b380
Mar 29 21:58:24 ppp: [wan_link0] MRU 1492
Mar 29 21:58:24 ppp: [wan_link0] PROTOCOMP
Mar 29 21:58:24 ppp: [wan_link0] LCP: rec'd Configure Ack #1 (Ack-Sent)
Mar 29 21:58:24 ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Mar 29 21:58:24 ppp: [wan_link0] MAGICNUM 18e3dba3
Mar 29 21:58:24 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 21:58:24 ppp: [wan_link0] MRU 1492
Mar 29 21:58:24 ppp: [wan_link0] LCP: SendConfigAck #118
Mar 29 21:58:24 ppp: [wan_link0] MAGICNUM 18e3dba3
Mar 29 21:58:24 ppp: [wan_link0] AUTHPROTO PAP
Mar 29 21:58:24 ppp: [wan_link0] MRU 1492
Mar 29 21:58:24 ppp: [wan_link0] LCP: rec'd Configure Request #118 (Req-Sent)
Mar 29 21:58:23 ppp: [wan_link0] MAGICNUM b377b380
Mar 29 21:58:23 ppp: [wan_link0] MRU 1492
Mar 29 21:58:23 ppp: [wan_link0] PROTOCOMP
Mar 29 21:58:23 ppp: [wan_link0] LCP: SendConfigReq #1
Mar 29 21:58:23 ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Mar 29 21:58:23 ppp: [wan_link0] LCP: Up event
Mar 29 21:58:23 ppp: [wan_link0] Link: UP event
Mar 29 21:58:23 ppp: [wan_link0] PPPoE: connection successful
Mar 29 21:58:23 ppp: PPPoE: rec'd ACNAME "ERXKLJ22"
Mar 29 21:58:23 ppp: [wan_link0] PPPoE: Connecting to '*'
Mar 29 21:58:23 ppp: [wan_link0] LCP: LayerStart
Mar 29 21:58:23 ppp: [wan_link0] LCP: state change Initial --> Starting
Mar 29 21:58:23 ppp: [wan_link0] LCP: Open event
« Last Edit: March 30, 2011, 02:09:33 am by calvinz »

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #6 on: March 30, 2011, 03:43:40 am »
updated with sys logs , ppp logs .. it seems like the ISP does not like certain PPP settings by pfSense and requesting it to disconnect

update: tried with pfsense 1.2.3 with open-vm-tools installed.. line still disconnects at the same rate.. have a feeling that the ISP doesn't like me using pfsense  >:(
« Last Edit: March 30, 2011, 08:42:03 am by calvinz »

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #7 on: April 10, 2011, 11:07:07 am »
Hi All,

I may have found the root cause of the problem. It seems that my ISP requires a LCP echo interval of 30 seconds no more or less in order to keep a constant connection. Is this option configurable under pfsense ?



Online stephenw10

  • Hero Member
  • *****
  • Posts: 8080
    • View Profile
Re: constant PPPoE disconnection
« Reply #8 on: April 10, 2011, 12:11:26 pm »
I take it that screen shot is from an ISP supplied router? Is it their custom firmware?

It seems a little odd that they would require you to send LCP echos. More likely they are sending echos and you are not replying if it's them that is dropping the ppp session.

Or more likely it is a negotiated LQR echo they need.

Anyway you can enable lcp echos in ppp though I have never done it.
See the ppp man page about half way down.

I'm not sure how you'd go about enabling it though. Maybe try adding 'enable echo' to /etc/ppp/ppp.conf  :-\

Steve
« Last Edit: April 10, 2011, 12:16:22 pm by stephenw10 »

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #9 on: April 10, 2011, 12:26:28 pm »
hi Steve,

thanks for the reply. its not a custom firmware, that option is available from a stock firmware. now I would need to figure out how to add that setting under pfsense  ???


Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #10 on: April 10, 2011, 02:26:38 pm »
i have tried manually creating a mpd_wan.conf file stating the keep alive timing under /conf .. still doesn't help at all :(

checked the /etc/ppp/ppp.conf but there's no configuration details about my pppoe interface in there  ???

edit : and the thing I'm curious about now is why does the connection not drop at all upon a clean installation. After the first reboot, the disconnection keeps coming  ??? :(
« Last Edit: April 10, 2011, 02:29:22 pm by calvinz »

Offline wallabybob

  • Hero Member
  • *****
  • Posts: 5262
    • View Profile
Re: constant PPPoE disconnection
« Reply #11 on: April 10, 2011, 03:33:47 pm »
checked the /etc/ppp/ppp.conf but there's no configuration details about my pppoe interface in there  ???
Try /var/etc/mpd_wan.conf

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #12 on: April 10, 2011, 07:36:30 pm »
checked the /etc/ppp/ppp.conf but there's no configuration details about my pppoe interface in there  ???
Try /var/etc/mpd_wan.conf


tried to modify the configurations there.. upon disconnection and reconnection the settings revert back to the default ones
« Last Edit: April 10, 2011, 10:16:16 pm by calvinz »

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #13 on: April 10, 2011, 11:58:35 pm »
one thing that I have noticed is , when WAN interface is on DHCP the keep alive option is working perfectly fine. Changing it to PPPoE remains working however syslogs continue to cough out dhclient:FAIL . Restarting the machine removes the dhclient:FAIL log but keep-alive option is not working anymore.

Offline calvinz

  • Jr. Member
  • **
  • Posts: 45
    • View Profile
Re: constant PPPoE disconnection
« Reply #14 on: April 13, 2011, 04:06:02 am »
with the DHCP trick, the connection stayed alive for 2 days and counting.. but I wouldn't want to have this as a permanent solution :-\ are there any ways I can see verbose output of what is happening on the LCP ?