Is PPPOE working for you guys?
-
Site to Site Openvpn (remote branch having the issue)
If you are authenticating via PPPoE on your WAN to your modem I would be very concerned with your connection at this point. I am pretty sure that there are bugs with the PPPoE portion of pfsense. I have taken my modem out of bridged mode and the modem is now doing PPPoE authentication itself. The modem's DHCP has handed me its first internal natted address. I've been up since I made the change on Saturday the 11th.When I was in PPPoE mode my pfsense box would lose connection at least twice a day. Before I made the change to a full natted situation I replaced modems and had qwest come out and fix all of the telephone lines. Qwest said everything looks great and then the next day my connection went into a tail spin up and down up and down.
I don't know what it is because the main site I think was using the same build, I have it in PPPoE mode and knock on wood it has been staying up the whole time. Working a full-time job and having a side job customer yell at you for two weeks while I tried to fix the disconnection issue, I am happy to be NATed. I would try PPPoE again, just not with this customer.
Look at my previous post.
http://forum.pfsense.org/index.php/topic,37603.0.html
http://forum.pfsense.org/index.php/topic,35475.45.html -
[snip]
Look at my previous post.
http://forum.pfsense.org/index.php/topic,37603.0.html
http://forum.pfsense.org/index.php/topic,35475.45.htmlAnd you never did gather any log information that would have been helpful in tracking it down. Yelling "it's broken!" and then not helping to debug the problem is quite useless for everyone. Especially when most of us cannot reproduce the problem. Review my posts in this thread for things to try (system log entries for mpd, and comparing the mpd config before and after)
to my experience its mpd only thats causing this, is there any way to switch to an older mpd used in 1.2.3 or mayb if u could tell me how to put mpd in debug mode then i can atleast get u more useful logs.
It is highly unlikely that we will downgrade mpd since it's working fine for the vast majority of people. If you can check again the things I asked for (your responses were somewhat confusing and conflicted, you kept making too many changes at once), it would help.
Specifically we need to see:
- mpd logs from a working and a broken connection attempt (clog /var/log/system.log | egrep '(mpd|ppp)' ) be sure to just include the connection attemps, check the timestamps.
- /var/etc/mpd_<interfacename>.conf from a working and a broken connection attempt
- Try with/without "configure a null service name" turned on. (And provide the mpd_<interfacename>.conf from a broken/working attempt there.)
- Bonus points if you have a /var/etc/mpd*.conf from your old 1.2.3 install
- Make sure you remove/mask out your username and password from your mpd.conf files.
So in total that would ideally be as many as four (4) sets of logs and five (5) copies of various mpd.conf files. At a minimum it's two (2) copies of the log and two (2) mpd_something.conf files.</interfacename></interfacename>
-
ill work on the log and send it in as soon as i gather all of it as mentioned, the reason for not being able to provide info is because im not a BSD person so i hardly know any of its commands at all so thats y im clueless on what to gather from where
-
let me get one thing straight, there is no mpd.conf change which causes it to work or to fail because it just fails and pppoe only connects fine on boot and never a successful reconnect is connection is dropped, the config i used during 1.2.3 is the same only that pfsense is now v2, i never touch any config at all as long as it keeps working as required
mpd_wan.conf
startup: # configure the console set console close # configure the web server set web close default: pppoeclient: create bundle static wan set iface name pppoe0 set iface route default set iface enable on-demand set iface idle 0 set iface addrs 10.10.1.1 10.10.1.2 set iface enable tcpmssfix set iface up-script /usr/local/sbin/ppp-linkup set iface down-script /usr/local/sbin/ppp-linkdown set ipcp ranges 0.0.0.0/0 0.0.0.0/0 set ipcp no vjcomp #log -bund -ccp -chat -iface -ipcp -lcp -link create link static wan_link0 pppoe set link action bundle wan set link disable multilink set link keep-alive 10 60 set link max-redial 0 set link disable chap pap set link accept chap pap eap set link disable incoming set link mtu 1492 set auth authname "username" set auth password password set pppoe iface vr1 opensystem.log during fresh boot
$ clog /var/log/system.log Jun 18 20:05:54 firewall syslogd: kernel boot file is /boot/kernel/kernel Jun 18 20:05:54 firewall kernel: Copyright (c) 1992-2010 The FreeBSD Project. Jun 18 20:05:54 firewall kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jun 18 20:05:54 firewall kernel: The Regents of the University of California. All rights reserved. Jun 18 20:05:54 firewall kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jun 18 20:05:54 firewall kernel: FreeBSD 8.1-RELEASE-p4 #0: Fri Jun 17 23:27:22 EDT 2011 Jun 18 20:05:54 firewall kernel: sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386 Jun 18 20:05:54 firewall kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Jun 18 20:05:54 firewall kernel: CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU) Jun 18 20:05:54 firewall kernel: Origin = "AuthenticAMD" Id = 0x5a2 Family = 5 Model = a Stepping = 2 Jun 18 20:05:54 firewall kernel: Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>Jun 18 20:05:54 firewall kernel: AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>Jun 18 20:05:54 firewall kernel: real memory = 268435456 (256 MB) Jun 18 20:05:54 firewall kernel: avail memory = 243433472 (232 MB) Jun 18 20:05:54 firewall kernel: pnpbios: Bad PnP BIOS data checksum Jun 18 20:05:54 firewall kernel: wlan: mac acl policy registered Jun 18 20:05:54 firewall kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. Jun 18 20:05:54 firewall kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. Jun 18 20:05:54 firewall kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0708970, 0) error 1 Jun 18 20:05:54 firewall kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. Jun 18 20:05:54 firewall kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. Jun 18 20:05:54 firewall kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0708a10, 0) error 1 Jun 18 20:05:54 firewall kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/. Jun 18 20:05:54 firewall kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf. Jun 18 20:05:54 firewall kernel: module_register_init: MOD_LOAD (wpi_fw, 0xc087b830, 0) error 1 Jun 18 20:05:54 firewall kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. Jun 18 20:05:54 firewall kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. Jun 18 20:05:54 firewall kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0708ab0, 0) error 1 Jun 18 20:05:54 firewall kernel: K6-family MTRR support enabled (2 registers) Jun 18 20:05:54 firewall kernel: ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309) Jun 18 20:05:54 firewall kernel: ACPI: Table initialisation failed: AE_NOT_FOUND Jun 18 20:05:54 firewall kernel: ACPI: Try disabling either ACPI or apic support. Jun 18 20:05:54 firewall kernel: cryptosoft0: <software crypto="">on motherboard Jun 18 20:05:54 firewall kernel: padlock0: No ACE support. Jun 18 20:05:54 firewall kernel: pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboard Jun 18 20:05:54 firewall kernel: pci0: <pci bus="">on pcib0 Jun 18 20:05:54 firewall kernel: Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007 Jun 18 20:05:54 firewall kernel: pci0: <encrypt decrypt,="" entertainment="" crypto="">at device 1.2 (no driver attached) Jun 18 20:05:54 firewall kernel: vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0 Jun 18 20:05:54 firewall kernel: vr0: Quirks: 0x2 Jun 18 20:05:54 firewall kernel: vr0: Revision: 0x96 Jun 18 20:05:54 firewall kernel: miibus0: <mii bus="">on vr0 Jun 18 20:05:54 firewall kernel: ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus0 Jun 18 20:05:54 firewall kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jun 18 20:05:54 firewall kernel: vr0: [ITHREAD] Jun 18 20:05:54 firewall kernel: vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0 Jun 18 20:05:54 firewall kernel: vr1: Quirks: 0x2 Jun 18 20:05:54 firewall kernel: vr1: Revision: 0x96 Jun 18 20:05:54 firewall kernel: miibus1: <mii bus="">on vr1 Jun 18 20:05:54 firewall kernel: ukphy1: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus1 Jun 18 20:05:54 firewall kernel: ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jun 18 20:05:54 firewall kernel: vr1: [ITHREAD] Jun 18 20:05:54 firewall kernel: vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 15 at device 11.0 on pci0 Jun 18 20:05:54 firewall kernel: vr2: Quirks: 0x2 Jun 18 20:05:54 firewall kernel: vr2: Revision: 0x96 Jun 18 20:05:54 firewall kernel: miibus2: <mii bus="">on vr2 Jun 18 20:05:54 firewall kernel: ukphy2: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus2 Jun 18 20:05:54 firewall kernel: ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jun 18 20:05:54 firewall kernel: vr2: [ITHREAD] Jun 18 20:05:54 firewall kernel: ath0: <atheros 5413="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0 Jun 18 20:05:54 firewall kernel: ath0: [ITHREAD] Jun 18 20:05:54 firewall kernel: ath0: AR5413 mac 10.5 RF5413 phy 6.1 Jun 18 20:05:54 firewall kernel: isab0: <pci-isa bridge="">port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0 Jun 18 20:05:54 firewall kernel: isa0: <isa bus="">on isab0 Jun 18 20:05:54 firewall kernel: atapci0: <amd cs5536="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0 Jun 18 20:05:54 firewall kernel: ata0: <ata 0="" channel="">on atapci0 Jun 18 20:05:54 firewall kernel: ata0: [ITHREAD] Jun 18 20:05:54 firewall kernel: ata1: <ata 1="" channel="">on atapci0 Jun 18 20:05:54 firewall kernel: ata1: [ITHREAD] Jun 18 20:05:54 firewall kernel: ohci0: <ohci (generic)="" usb="" controller="">mem 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0 Jun 18 20:05:54 firewall kernel: ohci0: [ITHREAD] Jun 18 20:05:54 firewall kernel: usbus0: <ohci (generic)="" usb="" controller="">on ohci0 Jun 18 20:05:54 firewall kernel: ehci0: <amd cs5536="" (geode)="" usb="" 2.0="" controller="">mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0 Jun 18 20:05:54 firewall kernel: ehci0: [ITHREAD] Jun 18 20:05:54 firewall kernel: usbus1: EHCI version 1.0 Jun 18 20:05:54 firewall kernel: usbus1: <amd cs5536="" (geode)="" usb="" 2.0="" controller="">on ehci0 Jun 18 20:05:54 firewall kernel: cpu0 on motherboard Jun 18 20:05:54 firewall kernel: orm0: <isa option="" rom="">at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0 Jun 18 20:05:54 firewall kernel: atrtc0: <at real="" time="" clock="">at port 0x70 irq 8 on isa0 Jun 18 20:05:54 firewall kernel: ppc0: parallel port not found. Jun 18 20:05:54 firewall kernel: uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jun 18 20:05:54 firewall kernel: uart0: [FILTER] Jun 18 20:05:54 firewall kernel: uart0: console (9600,n,8,1) Jun 18 20:05:54 firewall kernel: uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0 Jun 18 20:05:54 firewall kernel: uart1: [FILTER] Jun 18 20:05:54 firewall kernel: Timecounter "TSC" frequency 498052661 Hz quality 800 Jun 18 20:05:54 firewall kernel: Timecounters tick every 10.000 msec Jun 18 20:05:54 firewall kernel: IPsec: Initialized Security Association Processing. Jun 18 20:05:54 firewall kernel: usbus0: 12Mbps Full Speed USB v1.0 Jun 18 20:05:54 firewall kernel: usbus1: 480Mbps High Speed USB v2.0 Jun 18 20:05:54 firewall kernel: ugen0.1: <amd>at usbus0 Jun 18 20:05:54 firewall kernel: uhub0: <amd 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0 Jun 18 20:05:54 firewall kernel: ugen1.1: <amd>at usbus1 Jun 18 20:05:54 firewall kernel: uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1 Jun 18 20:05:54 firewall kernel: ad0: 991MB <cf 20071116="" 1gb="">at ata0-master PIO4 Jun 18 20:05:54 firewall kernel: Root mount waiting for: usbus1 usbus0 Jun 18 20:05:54 firewall kernel: uhub0: 4 ports with 4 removable, self powered Jun 18 20:05:54 firewall kernel: Root mount waiting for: usbus1 Jun 18 20:05:54 firewall kernel: uhub1: 4 ports with 4 removable, self powered Jun 18 20:05:54 firewall kernel: Trying to mount root from ufs:/dev/ufs/pfsense1 Jun 18 20:05:54 firewall kernel: pflog0: promiscuous mode enabled Jun 18 20:05:57 firewall hostapd: ath0_wlan0: STA 00:1d:d9:77:02:f7 IEEE 802.11: associated Jun 18 20:05:57 firewall hostapd: ath0_wlan0: STA 00:1d:d9:77:02:f7 RADIUS: starting accounting session 4DFCCCE1-00000000 Jun 18 20:05:57 firewall hostapd: ath0_wlan0: STA 00:1d:d9:77:02:f7 WPA: pairwise key handshake completed (WPA) Jun 18 20:05:57 firewall hostapd: ath0_wlan0: STA 00:1d:d9:77:02:f7 WPA: group key handshake completed (WPA) Jun 18 20:05:57 firewall kernel: load_dn_sched dn_sched FIFO loaded Jun 18 20:05:57 firewall kernel: load_dn_sched dn_sched QFQ loaded Jun 18 20:05:57 firewall kernel: load_dn_sched dn_sched RR loaded Jun 18 20:05:57 firewall kernel: load_dn_sched dn_sched WF2Q+ loaded Jun 18 20:05:57 firewall kernel: load_dn_sched dn_sched PRIO loaded Jun 18 20:05:59 firewall apinger: Starting Alarm Pinger, apinger(32638) Jun 18 20:06:01 firewall php: : rc.newwanip: Informational is starting pppoe0. Jun 18 20:06:01 firewall php: : rc.newwanip: on (IP address: 92.96.222.244) (interface: wan) (real interface: pppoe0). Jun 18 20:06:03 firewall php: : ROUTING: change default route to 195.229.252.27 Jun 18 20:06:03 firewall apinger: Exiting on signal 15. Jun 18 20:06:04 firewall check_reload_status: Reloading filter Jun 18 20:06:04 firewall apinger: Starting Alarm Pinger, apinger(39372) Jun 18 20:06:04 firewall php: : DynDns: updatedns() starting Jun 18 20:06:04 firewall php: : DynDns debug information: 92.96.222.244 extracted from local system. Jun 18 20:06:04 firewall php: : DynDns: Current WAN IP: 92.96.222.244 Cached IP: 217.164.167.249 Jun 18 20:06:04 firewall php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 217.164.167.249 WAN IP: 92.96.222.244 Jun 18 20:06:04 firewall php: : DynDns: DynDns _update() starting. Jun 18 20:06:07 firewall php: : DynDns: DynDns _checkStatus() starting. Jun 18 20:06:07 firewall php: : DynDns: Current Service: dyndns Jun 18 20:06:08 firewall php: : ROUTING: change default route to 195.229.252.27 Jun 18 20:06:08 firewall php: : The command '/usr/local/sbin/relayd -f /var/etc/relayd.conf' returned exit code '1', the output was '/var/etc/relayd.conf:4: syntax error no redirections, nothing to do' Jun 18 20:06:08 firewall php: : DynDns debug information: 92.96.222.244 extracted from local system. Jun 18 20:06:08 firewall php: : phpDynDNS: updating cache file /conf/dyndns_wandyndns'xbipin.dyndns.org'.cache: 92.96.222.244 Jun 18 20:06:08 firewall php: : OpenNTPD is starting up. Jun 18 20:06:08 firewall php: : phpDynDNS: (Success) IP Address Changed Successfully! (92.96.222.244) Jun 18 20:06:10 firewall dhcpd: Internet Systems Consortium DHCP Server 4.2.1-P1 Jun 18 20:06:10 firewall dhcpd: Copyright 2004-2011 Internet Systems Consortium. Jun 18 20:06:10 firewall dhcpd: All rights reserved. Jun 18 20:06:10 firewall dhcpd: For info, please visit https://www.isc.org/software/dhcp/ Jun 18 20:06:10 firewall dnsmasq[52629]: started, version 2.55 cachesize 10000 Jun 18 20:06:10 firewall dnsmasq[52629]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP Jun 18 20:06:10 firewall dnsmasq[52629]: reading /etc/resolv.conf Jun 18 20:06:10 firewall check_reload_status: Updating all dyndns Jun 18 20:06:10 firewall dnsmasq[52629]: using nameserver 198.153.192.1#53 Jun 18 20:06:10 firewall dnsmasq[52629]: using nameserver 208.67.222.222#53 Jun 18 20:06:10 firewall dnsmasq[52629]: using nameserver 213.42.20.20#53 Jun 18 20:06:10 firewall dnsmasq[52629]: using nameserver 8.8.8.8#53 Jun 18 20:06:10 firewall dnsmasq[52629]: read /etc/hosts - 2 addresses Jun 18 20:06:17 firewall php: : Resyncing OpenVPN instances for interface WAN. Jun 18 20:06:19 firewall php: : DynDns: updatedns() starting Jun 18 20:06:19 firewall php: : DynDns debug information: 92.96.222.244 extracted from local system. Jun 18 20:06:19 firewall php: : DynDns: Current WAN IP: 92.96.222.244 Cached IP: 92.96.222.244 Jun 18 20:06:19 firewall php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jun 18 20:06:19 firewall check_reload_status: Restarting ipsec tunnels Jun 18 20:06:35 firewall php: : miniupnpd: Starting service on interface: lan Jun 18 20:06:35 firewall miniupnpd[49798]: HTTP listening on port 2189 Jun 18 20:06:35 firewall miniupnpd[49798]: HTTP listening on port 2189 Jun 18 20:06:35 firewall miniupnpd[49798]: Listening for NAT-PMP traffic on port 5351 Jun 18 20:06:35 firewall miniupnpd[49798]: Listening for NAT-PMP traffic on port 5351 Jun 18 20:06:36 firewall php: : Restarting/Starting all packages. Jun 18 20:06:37 firewall php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing. Jun 18 20:06:38 firewall login: login on console as root Jun 18 20:06:38 firewall sshlockout[56363]: sshlockout/webConfigurator v3.0 starting up Jun 18 20:06:39 firewall check_reload_status: Reloading filter Jun 18 20:07:04 firewall apinger: Error while feeding rrdtool: Broken pipe Jun 18 20:08:04 firewall apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.</cf></amd></amd></amd></amd></at></isa></amd></amd></ohci></ohci></ata></ata></amd></isa></pci-isa></atheros></generic></mii></via></generic></mii></via></generic></mii></via></encrypt></pci></host></software></mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>$ clog /var/log/system.log | egrep '(mpd|ppp)' Jun 18 20:06:01 firewall php: : rc.newwanip: Informational is starting pppoe0. Jun 18 20:06:01 firewall php: : rc.newwanip: on (IP address: 92.96.222.244) (interface: wan) (real interface: pppoe0).system.log when isp device reset and once thats up still pfsense wont reconnect
$ clog /var/log/system.log | egrep '(mpd|ppp)' Jun 18 20:06:01 firewall php: : rc.newwanip: Informational is starting pppoe0. Jun 18 20:06:01 firewall php: : rc.newwanip: on (IP address: 92.96.222.244) (interface: wan) (real interface: pppoe0). Jun 18 20:13:04 firewall ppp: [wan_link0] LCP: no reply to 1 echo request(s) Jun 18 20:13:14 firewall ppp: [wan_link0] LCP: no reply to 2 echo request(s) Jun 18 20:13:24 firewall ppp: [wan_link0] LCP: no reply to 3 echo request(s) Jun 18 20:13:34 firewall ppp: [wan_link0] LCP: no reply to 4 echo request(s) Jun 18 20:13:44 firewall ppp: [wan_link0] LCP: no reply to 5 echo request(s) Jun 18 20:13:44 firewall ppp: [wan_link0] LCP: peer not responding to echo requests Jun 18 20:13:44 firewall ppp: [wan_link0] LCP: state change Opened --> Stopping Jun 18 20:13:44 firewall ppp: [wan_link0] Link: Leave bundle "wan" Jun 18 20:13:44 firewall ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Jun 18 20:13:44 firewall ppp: [wan] IPCP: Close event Jun 18 20:13:44 firewall ppp: [wan] IPCP: state change Opened --> Closing Jun 18 20:13:44 firewall ppp: [wan] IPCP: SendTerminateReq #3 Jun 18 20:13:44 firewall ppp: [wan] IPCP: LayerDown Jun 18 20:13:44 firewall ppp: [wan] IFACE: Down event Jun 18 20:13:44 firewall ppp: [wan] IPCP: Down event Jun 18 20:13:44 firewall ppp: [wan] IPCP: LayerFinish Jun 18 20:13:44 firewall ppp: [wan] Bundle: No NCPs left. Closing links... Jun 18 20:13:44 firewall ppp: [wan] IPCP: state change Closing --> Initial Jun 18 20:13:44 firewall ppp: [wan_link0] LCP: SendTerminateReq #2 Jun 18 20:13:44 firewall ppp: [wan_link0] LCP: LayerDown Jun 18 20:13:47 firewall ppp: [wan_link0] LCP: SendTerminateReq #3 Jun 18 20:13:49 firewall ppp: [wan_link0] LCP: state change Stopping --> Stopped Jun 18 20:13:49 firewall ppp: [wan_link0] LCP: LayerFinish Jun 18 20:13:49 firewall ppp: [wan_link0] PPPoE: connection closed Jun 18 20:13:49 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:13:49 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:13:49 firewall ppp: [wan_link0] LCP: state change Stopped --> Starting Jun 18 20:13:49 firewall ppp: [wan_link0] LCP: LayerStart Jun 18 20:13:49 firewall ppp: [wan_link0] Link: reconnection attempt 1 in 4 seconds Jun 18 20:13:53 firewall ppp: [wan_link0] Link: reconnection attempt 1 Jun 18 20:13:53 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:14:02 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:14:02 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:14:02 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:14:02 firewall ppp: [wan_link0] Link: reconnection attempt 2 in 3 seconds Jun 18 20:14:05 firewall ppp: [wan_link0] Link: reconnection attempt 2 Jun 18 20:14:05 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:14:14 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:14:14 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:14:14 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:14:14 firewall ppp: [wan_link0] Link: reconnection attempt 3 in 2 seconds Jun 18 20:14:16 firewall ppp: [wan_link0] Link: reconnection attempt 3 Jun 18 20:14:16 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:14:25 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:14:25 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:14:25 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:14:25 firewall ppp: [wan_link0] Link: reconnection attempt 4 in 1 seconds Jun 18 20:14:26 firewall ppp: [wan_link0] Link: reconnection attempt 4 Jun 18 20:14:26 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:14:35 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:14:35 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:14:35 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:14:35 firewall ppp: [wan_link0] Link: reconnection attempt 5 in 3 seconds Jun 18 20:14:38 firewall ppp: [wan_link0] Link: reconnection attempt 5 Jun 18 20:14:38 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:14:47 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:14:47 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:14:47 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:14:47 firewall ppp: [wan_link0] Link: reconnection attempt 6 in 2 seconds Jun 18 20:14:49 firewall ppp: [wan_link0] Link: reconnection attempt 6 Jun 18 20:14:49 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:14:58 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:14:58 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:14:58 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:14:58 firewall ppp: [wan_link0] Link: reconnection attempt 7 in 3 seconds Jun 18 20:15:01 firewall ppp: [wan_link0] Link: reconnection attempt 7 Jun 18 20:15:01 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:15:10 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:15:10 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:15:10 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:15:10 firewall ppp: [wan_link0] Link: reconnection attempt 8 in 3 seconds Jun 18 20:15:13 firewall ppp: [wan_link0] Link: reconnection attempt 8 Jun 18 20:15:13 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:15:22 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:15:22 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:15:22 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:15:22 firewall ppp: [wan_link0] Link: reconnection attempt 9 in 2 seconds Jun 18 20:15:24 firewall ppp: [wan_link0] Link: reconnection attempt 9 Jun 18 20:15:24 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:15:33 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:15:33 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:15:33 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:15:33 firewall ppp: [wan_link0] Link: reconnection attempt 10 in 4 seconds Jun 18 20:15:37 firewall ppp: [wan_link0] Link: reconnection attempt 10 Jun 18 20:15:37 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:15:46 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:15:46 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:15:46 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:15:46 firewall ppp: [wan_link0] Link: reconnection attempt 11 in 4 seconds Jun 18 20:15:50 firewall ppp: [wan_link0] Link: reconnection attempt 11 Jun 18 20:15:50 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:15:59 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:15:59 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:15:59 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:15:59 firewall ppp: [wan_link0] Link: reconnection attempt 12 in 3 seconds Jun 18 20:16:02 firewall ppp: [wan_link0] Link: reconnection attempt 12 Jun 18 20:16:02 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:16:11 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:16:11 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:16:11 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:16:11 firewall ppp: [wan_link0] Link: reconnection attempt 13 in 1 seconds Jun 18 20:16:12 firewall ppp: [wan_link0] Link: reconnection attempt 13 Jun 18 20:16:12 firewall ppp: [wan_link0] PPPoE: Connecting to '*' Jun 18 20:16:22 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:16:22 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:16:22 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:16:22 firewall ppp: [wan_link0] Link: reconnection attempt 14 in 2 seconds Jun 18 20:16:24 firewall ppp: [wan_link0] Link: reconnection attempt 14 Jun 18 20:16:24 firewall ppp: [wan_link0] PPPoE: Connecting to '*'now the above stuff but with null thing ticked
mpd_wan.conf
startup: # configure the console set console close # configure the web server set web close default: pppoeclient: create bundle static wan set iface name pppoe0 set iface route default set iface enable on-demand set iface idle 0 set iface addrs 10.10.1.1 10.10.1.2 set iface enable tcpmssfix set iface up-script /usr/local/sbin/ppp-linkup set iface down-script /usr/local/sbin/ppp-linkdown set ipcp ranges 0.0.0.0/0 0.0.0.0/0 set ipcp no vjcomp #log -bund -ccp -chat -iface -ipcp -lcp -link create link static wan_link0 pppoe set link action bundle wan set link disable multilink set link keep-alive 10 60 set link max-redial 0 set link disable chap pap set link accept chap pap eap set link disable incoming set link mtu 1492 set auth authname "username" set auth password password set pppoe service "" set pppoe iface vr1 opensystem.log on boot
$ clog /var/log/system.log | egrep '(mpd|ppp)' Jun 18 20:20:12 firewall php: : rc.newwanip: Informational is starting pppoe0. Jun 18 20:20:12 firewall php: : rc.newwanip: on (IP address: 92.96.231.244) (interface: wan) (real interface: pppoe0).system.log when isp device reset and pfsense wont reconenct
$ clog /var/log/system.log | egrep '(mpd|ppp)' Jun 18 20:20:12 firewall php: : rc.newwanip: Informational is starting pppoe0. Jun 18 20:20:12 firewall php: : rc.newwanip: on (IP address: 92.96.231.244) (interface: wan) (real interface: pppoe0). Jun 18 20:23:15 firewall ppp: [wan_link0] LCP: no reply to 1 echo request(s) Jun 18 20:23:25 firewall ppp: [wan_link0] LCP: no reply to 2 echo request(s) Jun 18 20:23:35 firewall ppp: [wan_link0] LCP: no reply to 3 echo request(s) Jun 18 20:23:45 firewall ppp: [wan_link0] LCP: no reply to 4 echo request(s) Jun 18 20:23:56 firewall ppp: [wan_link0] LCP: no reply to 5 echo request(s) Jun 18 20:23:56 firewall ppp: [wan_link0] LCP: peer not responding to echo requests Jun 18 20:23:56 firewall ppp: [wan_link0] LCP: state change Opened --> Stopping Jun 18 20:23:56 firewall ppp: [wan_link0] Link: Leave bundle "wan" Jun 18 20:23:56 firewall ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Jun 18 20:23:56 firewall ppp: [wan] IPCP: Close event Jun 18 20:23:56 firewall ppp: [wan] IPCP: state change Opened --> Closing Jun 18 20:23:56 firewall ppp: [wan] IPCP: SendTerminateReq #3 Jun 18 20:23:56 firewall ppp: [wan] IPCP: LayerDown Jun 18 20:23:56 firewall ppp: [wan] IFACE: Down event Jun 18 20:23:56 firewall ppp: [wan] IPCP: Down event Jun 18 20:23:56 firewall ppp: [wan] IPCP: LayerFinish Jun 18 20:23:56 firewall ppp: [wan] Bundle: No NCPs left. Closing links... Jun 18 20:23:56 firewall ppp: [wan] IPCP: state change Closing --> Initial Jun 18 20:23:56 firewall ppp: [wan_link0] LCP: SendTerminateReq #2 Jun 18 20:23:56 firewall ppp: [wan_link0] LCP: LayerDown Jun 18 20:23:58 firewall ppp: [wan_link0] LCP: SendTerminateReq #3 Jun 18 20:24:00 firewall ppp: [wan_link0] LCP: state change Stopping --> Stopped Jun 18 20:24:00 firewall ppp: [wan_link0] LCP: LayerFinish Jun 18 20:24:00 firewall ppp: [wan_link0] PPPoE: connection closed Jun 18 20:24:00 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:24:00 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:24:00 firewall ppp: [wan_link0] LCP: state change Stopped --> Starting Jun 18 20:24:00 firewall ppp: [wan_link0] LCP: LayerStart Jun 18 20:24:00 firewall ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds Jun 18 20:24:03 firewall ppp: [wan_link0] Link: reconnection attempt 1 Jun 18 20:24:03 firewall ppp: [wan_link0] PPPoE: Connecting to '' Jun 18 20:24:12 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:24:12 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:24:12 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:24:12 firewall ppp: [wan_link0] Link: reconnection attempt 2 in 3 seconds Jun 18 20:24:15 firewall ppp: [wan_link0] Link: reconnection attempt 2 Jun 18 20:24:15 firewall ppp: [wan_link0] PPPoE: Connecting to '' Jun 18 20:24:17 firewall ppp: PPPoE: rec'd ACNAME "WE1" Jun 18 20:24:24 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:24:24 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:24:24 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:24:24 firewall ppp: [wan_link0] Link: reconnection attempt 3 in 3 seconds Jun 18 20:24:27 firewall ppp: [wan_link0] Link: reconnection attempt 3 Jun 18 20:24:27 firewall ppp: [wan_link0] PPPoE: Connecting to '' Jun 18 20:24:27 firewall ppp: PPPoE: rec'd ACNAME "WE1" Jun 18 20:24:36 firewall ppp: [wan_link0] PPPoE connection timeout after 9 seconds Jun 18 20:24:36 firewall ppp: [wan_link0] Link: DOWN event Jun 18 20:24:36 firewall ppp: [wan_link0] LCP: Down event Jun 18 20:24:36 firewall ppp: [wan_link0] Link: reconnection attempt 4 in 1 seconds Jun 18 20:24:37 firewall ppp: [wan_link0] Link: reconnection attempt 4 Jun 18 20:24:37 firewall ppp: [wan_link0] PPPoE: Connecting to '' Jun 18 20:24:37 firewall ppp: PPPoE: rec'd ACNAME "WE1" -
let me get one thing straight, there is no mpd.conf change which causes it to work or to fail because it just fails and pppoe only connects fine on boot and never a successful reconnect is connection is dropped, the config i used during 1.2.3 is the same only that pfsense is now v2, i never touch any config at all as long as it keeps working as required
You said before that an interface line was there one time and not the next when it worked and when it didn't. Now you are saying it doesn't change. The mpd_something.conf files are generated by the system, not by hand, so even if you don't think you changed anything, something may have changed. This is one of the ways that your information has been inconsistent.
-
let me get one thing straight, there is no mpd.conf change which causes it to work or to fail because it just fails and pppoe only connects fine on boot and never a successful reconnect is connection is dropped, the config i used during 1.2.3 is the same only that pfsense is now v2, i never touch any config at all as long as it keeps working as required
You said before that an interface line was there one time and not the next when it worked and when it didn't. Now you are saying it doesn't change. The mpd_something.conf files are generated by the system, not by hand, so even if you don't think you changed anything, something may have changed. This is one of the ways that your information has been inconsistent.
i guess its just the confusion that's causing u to believe im being inconsistent, but if u check the logs etc i have provided now and since i started using pf v2 and reporting errors and bugs from then, the config hasnt changed much other than 3 things that were changed during the process of trying to produce logs
vj compression which i had issues with long time back
dial on demand which i also reported long time back and the way the connect button worked under interfaces
and currently the iface addrs thing which i tried to play around with to try and solve but didnt help that too once i came to know the actual location of the conf file from u or else i wouldn't have played with that too to try and solve itif u check logs u would see there isnt much info it produces to be able to figure out the issue and thats y i say its mpd where the issue is.
-
Jimp,
You have to see that I was in a pressing situation and I had to make a change or the customer would have outed me. I didn't have any time to do a lot of troubleshooting because this was going on for two weeks, I did not know there was more detailed logs in the /var/logs being new to pfsense. I though when you said system logs, you just mean the GUI system logs and I never saw any mpd or ppp errors. If this happens to me again heaven forbid I know which logs to send you. Go easy on me Dr. when it is sick I don't always know where to look for problems that is why I turned to you guys, I'm a rookie.
Believe me if I knew where to access all of these configs and logs I would have sent them. I really like pfSense and wanted to help others if they were in the same situation as me.
Thanks,
-
Members -
Is there definitive work-around solution to this? I just try to deploy this with version 2.0 RC3 and it does not seem to work.
Please advise.
-
I did have problems with PPPoE initially but 'Null service name' solved the problem for me. I do remember during initial configuration that the 'null service name' setting got lost (unchecked) but since re-checking it and rebooting, it hasn't happened since.
If it helps anyone, this is my working pfsense 2rc3 PPPoE config with Eti$alat
$cat /var/etc/mpd_wan.conf startup: # configure the console set console close # configure the web server set web close default: pppoeclient: create bundle static wan set iface name pppoe0 set iface route default set iface disable on-demand set iface idle 0 set iface enable tcpmssfix set iface up-script /usr/local/sbin/ppp-linkup set iface down-script /usr/local/sbin/ppp-linkdown set ipcp ranges 0.0.0.0/0 0.0.0.0/0 #log -bund -ccp -chat -iface -ipcp -lcp -link create link static wan_link0 pppoe set link action bundle wan set link disable multilink set link keep-alive 10 60 set link max-redial 0 set link disable chap pap set link accept chap pap eap set link disable incoming set link mtu 1492 set auth authname "username" set auth password password set pppoe service "" set pppoe iface em4 open -
Thanks Thermo. So, your ppoe was default setting with ppoe login/password and did not work. And when you checked 'null service name' in advance setting, it started working?
Will give that try tonight.
-
probie: yes, that's correct, it worked when 'null service name' was checked but as I kept configuring/fiddling/reconnecting other interfaces, it stopped working and when I eventually re-looked at the PPPoE configuration, the 'null service name' was unchecked by itself.
This was a couple of months ago (April/May?) though, and I can't remember whether it was with the default 2 install or the daily update available on the firmware update page.
Do try rebooting after changing the PPPoE options. -
Thanks Thermo. So, your ppoe was default setting with ppoe login/password and did not work. And when you checked 'null service name' in advance setting, it started working?
Will give that try tonight.
I used that "trick" since long time ago ( Since "Beta 5" till "RC3" ), and my PPPoE connection works fine.
http://forum.pfsense.org/index.php/topic,34377.msg178168.html#msg178168
-
null service name still doesnt do the trick for most others like me and its definately something to do with mpd
-
Thanks ptt / thermo. Checking the "null service name" worked with an isp in Germany.
-
Attached are four files. Here's how I got them:
1. Boot system fresh. PPPoE connected.
2.```clog /var/log/system.log | egrep '(mpd|ppp)' > ppp_working.txt
cp /var/etc/mpd_wan.conf mpd_wan_working.conf.txt3\. Pull plug on WAN NIC. Wait 2 minutes. Re-plug. (WAN not connecting) 4.``` clog /var/log/system.log | egrep '(mpd|ppp)' > ppp_not_working.txt cp /var/etc/mpd_wan.conf mpd_wan_not_working.conf.txt5. Reboot to working WAN.
Null Service Name is checked.
same here, mpd is the problem and i guess few others and myself have mentioned the same. some1 definitely needs to break apart mpd and have a look at its code
-
I split out the only recent report with info and am locking this thread as it's all over the place and the originally reported issues were long ago fixed and it's been hijacked a ton of times since.
