WAN PPPoE 2.1.1-prerelease (i386)



  • After upgrading to 2.1.1-prerelease (i386)
    Wan makes pppoe connection but,System-Gateways and the dashboard shows "pending"
    apinger shows service stopped

    
    Last 300 PPP log entries
    Jan 23 14:16:09 	ppp: [wan_link0] LCP: no reply to 1 echo request(s)
    Jan 23 14:07:19 	ppp: [wan] IFACE: Rename interface ng0 to pppoe0
    Jan 23 14:07:19 	ppp: [wan] IFACE: Up event
    Jan 23 14:07:19 	ppp: [wan] 186.54.XX.XX -> 200.40.18.26
    Jan 23 14:07:19 	ppp: [wan] IPCP: LayerUp
    Jan 23 14:07:19 	ppp: [wan] IPCP: state change Ack-Sent --> Opened
    Jan 23 14:07:19 	ppp: [wan] IPADDR 186.54.XX.XX
    Jan 23 14:07:19 	ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
    Jan 23 14:07:19 	ppp: [wan] IPADDR 186.54.XX.XX
    Jan 23 14:07:19 	ppp: [wan] IPCP: SendConfigReq #3
    Jan 23 14:07:19 	ppp: [wan] 186.54.XX.XX is OK
    Jan 23 14:07:19 	ppp: [wan] IPADDR 186.54.XX.XX
    Jan 23 14:07:19 	ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: LayerFinish
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: state change Req-Sent --> Stopped
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: protocol was rejected by peer
    Jan 23 14:07:19 	ppp: [wan_link0] LCP: protocol IPV6CP was rejected
    Jan 23 14:07:19 	ppp: [wan_link0] LCP: rec'd Protocol Reject #12 (Opened)
    Jan 23 14:07:19 	ppp: [wan] IPADDR 0.0.0.0
    Jan 23 14:07:19 	ppp: [wan] IPCP: SendConfigReq #2
    Jan 23 14:07:19 	ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jan 23 14:07:19 	ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
    Jan 23 14:07:19 	ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
    Jan 23 14:07:19 	ppp: [wan] IPADDR 200.40.18.26
    Jan 23 14:07:19 	ppp: [wan] IPCP: SendConfigAck #170
    Jan 23 14:07:19 	ppp: [wan] 200.40.18.26 is OK
    Jan 23 14:07:19 	ppp: [wan] IPADDR 200.40.18.26
    Jan 23 14:07:19 	ppp: [wan] IPCP: rec'd Configure Request #170 (Req-Sent)
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: SendConfigReq #1
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: state change Starting --> Req-Sent
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: Up event
    Jan 23 14:07:19 	ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jan 23 14:07:19 	ppp: [wan] IPADDR 0.0.0.0
    Jan 23 14:07:19 	ppp: [wan] IPCP: SendConfigReq #1
    Jan 23 14:07:19 	ppp: [wan] IPCP: state change Starting --> Req-Sent
    Jan 23 14:07:19 	ppp: [wan] IPCP: Up event
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: LayerStart
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: state change Initial --> Starting
    Jan 23 14:07:19 	ppp: [wan] IPV6CP: Open event
    Jan 23 14:07:19 	ppp: [wan] IPCP: LayerStart
    Jan 23 14:07:19 	ppp: [wan] IPCP: state change Initial --> Starting
    Jan 23 14:07:19 	ppp: [wan] IPCP: Open event
    Jan 23 14:07:19 	ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
    Jan 23 14:07:19 	ppp: [wan_link0] Link: Join bundle "wan"
    Jan 23 14:07:19 	ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
    Jan 23 14:07:19 	ppp: [wan_link0] LCP: authorization successful
    Jan 23 14:07:19 	ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: LayerUp
    Jan 23 14:07:18 	ppp: [wan_link0] PAP: sending REQUEST #1 len: 27
    Jan 23 14:07:18 	ppp: [wan_link0] PAP: using authname "user"
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
    Jan 23 14:07:18 	ppp: [wan_link0] MAGICNUM 5295f1ce
    Jan 23 14:07:18 	ppp: [wan_link0] MRU 1492
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent)
    Jan 23 14:07:18 	ppp: [wan_link0] MAGICNUM 5295f1ce
    Jan 23 14:07:18 	ppp: [wan_link0] MRU 1492
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: SendConfigReq #2
    Jan 23 14:07:18 	ppp: [wan_link0] PROTOCOMP
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent)
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
    Jan 23 14:07:18 	ppp: [wan_link0] MAGICNUM 31499fe8
    Jan 23 14:07:18 	ppp: [wan_link0] AUTHPROTO PAP
    Jan 23 14:07:18 	ppp: [wan_link0] MRU 1492
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: SendConfigAck #11
    Jan 23 14:07:18 	ppp: [wan_link0] MAGICNUM 31499fe8
    Jan 23 14:07:18 	ppp: [wan_link0] AUTHPROTO PAP
    Jan 23 14:07:18 	ppp: [wan_link0] MRU 1492
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: rec'd Configure Request #11 (Req-Sent)
    Jan 23 14:07:18 	ppp: [wan_link0] MAGICNUM 5295f1ce
    Jan 23 14:07:18 	ppp: [wan_link0] MRU 1492
    Jan 23 14:07:18 	ppp: [wan_link0] PROTOCOMP
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: SendConfigReq #1
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: state change Starting --> Req-Sent
    Jan 23 14:07:18 	ppp: [wan_link0] LCP: Up event
    Jan 23 14:07:18 	ppp: [wan_link0] Link: UP event
    Jan 23 14:07:18 	ppp: [wan_link0] PPPoE: connection successful
    Jan 23 14:07:18 	ppp: PPPoE: rec'd ACNAME "ANTELDATA"
    Jan 23 14:07:12 	ppp: [wan_link0] PPPoE: Connecting to ''
    Jan 23 14:07:12 	ppp: [wan_link0] LCP: LayerStart
    Jan 23 14:07:12 	ppp: [wan_link0] LCP: state change Initial --> Starting
    Jan 23 14:07:12 	ppp: [wan_link0] LCP: Open event
    Jan 23 14:07:12 	ppp: [wan_link0] Link: OPEN event
    Jan 23 14:07:12 	ppp: [wan] Bundle: Interface ng0 created
    Jan 23 14:07:12 	ppp: web: web is not running
    Jan 23 14:07:12 	ppp: process 10703 started, version 5.7 (root@snapshots-8_3-i386.builders.pfsense.org 10:51 15-Jan-2014)
    Jan 23 14:07:12 	ppp:
    Jan 23 14:07:12 	ppp: Multi-link PPP daemon for FreeBSD
    ```![gateway-apinger.png](/public/_imported_attachments_/1/gateway-apinger.png)
    ![gateway-apinger.png_thumb](/public/_imported_attachments_/1/gateway-apinger.png_thumb)

  • Netgate Administrator

    Because apinger is not running the gateway status can can't be found hence it's always pending. I think there was an apinger bug in the first 2.1.1 snapshot that is now fixed. What snapshot are you running?

    Steve

    Edit: Maybe not fixed. https://forum.pfsense.org/index.php/topic,71601.0.html



  • Version:
    2.1.1-PRERELEASE (i386)
    built on Wed Jan 22 16:56:27 EST 2014

    # pfSense apinger configuration file. Automatically Generated!
    
    ## User and group the pinger should run as
    user "root"
    group "wheel"
    
    ## Mailer to use (default: "/usr/lib/sendmail -t")
    #mailer "/var/qmail/bin/qmail-inject"
    
    ## Location of the pid-file (default: "/var/run/apinger.pid")
    pid_file "/var/run/apinger.pid"
    
    ## Format of timestamp (%s macro) (default: "%b %d %H:%M:%S")
    #timestamp_format "%Y%m%d%H%M%S"
    
    status {
    	## File where the status information should be written to
    	file "/var/run/apinger.status"
    	## Interval between file updates
    	## when 0 or not set, file is written only when SIGUSR1 is received
    	interval 5s
    }
    
    ########################################
    # RRDTool status gathering configuration
    # Interval between RRD updates
    rrd interval 60s;
    
    ## These parameters can be overridden in a specific alarm configuration
    alarm default {
    	command on "/usr/local/sbin/pfSctl -c 'service reload dyndns %T' -c 'service reload ipsecdns' -c 'service reload openvpn %T' -c 'filter reload' "
    	command off "/usr/local/sbin/pfSctl -c 'service reload dyndns %T' -c 'service reload ipsecdns' -c 'service reload openvpn %T' -c 'filter reload' "
    	combine 10s
    }
    
    ## "Down" alarm definition.
    ## This alarm will be fired when target doesn't respond for 30 seconds.
    alarm down "down" {
    	time 10s
    }
    
    ## "Delay" alarm definition.
    ## This alarm will be fired when responses are delayed more than 200ms
    ## it will be canceled, when the delay drops below 100ms
    alarm delay "delay" {
    	delay_low 200ms
    	delay_high 500ms
    }
    
    ## "Loss" alarm definition.
    ## This alarm will be fired when packet loss goes over 20%
    ## it will be canceled, when the loss drops below 10%
    alarm loss "loss" {
    	percent_low 10
    	percent_high 20
    }
    
    target default {
    	## How often the probe should be sent
    	interval 1s
    
    	## How many replies should be used to compute average delay
    	## for controlling "delay" alarms
    	avg_delay_samples 10
    
    	## How many probes should be used to compute average loss
    	avg_loss_samples 50
    
    	## The delay (in samples) after which loss is computed
    	## without this delays larger than interval would be treated as loss
    	avg_loss_delay_samples 20
    
    	## Names of the alarms that may be generated for the target
    	alarms "down","delay","loss"
    
    	## Location of the RRD
    	#rrd file "/var/db/rrd/apinger-%t.rrd"
    }
    target "200.40.18.26" {
    	description "WAN_PPPOE"
    	srcip "186.54.XX.XX"
    	alarms override "loss","delay","down";
    	rrd file "/var/db/rrd/WAN_PPPOE-quality.rrd"
    }
    
    


  • JimP has been asking people to move up to the latest snapshots to test this kind of stuff again. Currently the latest are from a snapshot build that ran Thursday evening and into Friday early am, so some images have Thursday 23 Jan and a few with Fri 24 Jan early hour.
    If you are happy to be a test bunny, then update to the latest, test and report the results.



  • Version:

    Dashboard:

    Status-Gateways:

    GW log:










  • You have the "exited with status 255" error that others have, as well as apinger actually dying.
    Like: https://forum.pfsense.org/index.php/topic,71555.0.html and other threads.
    Moderators: this thread is best moved to the 2.1.1 Snapshot Feedback and Problems board.


Log in to reply