1. Home
  2. pfSense® Software
  3. Retired
  4. 2.0-RC Snapshot Feedback and Problems - RETIRED
  5. No automatic connect to ISP

No automatic connect to ISP

  • _

    Its now a long, long time (spring this year) when pfsense connected automatically to ISP when net-activity was there. But since this time (I don't remember for sure when it was the last time), it doesn't happen. No update brought a working auto-connect. Is there anyone with the same "feature" or is it only me who has to fight with this?
    Every time when my ISP disconnects me, my connection is off. I have to push the "connect"-button to get access.

    Is it possible because ifconfig doesn't show a IPv4 adress, only a IPv6 adress is assigned?

    Here the output of ifconfig:

    bge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    options=9b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum>ether 00:0b:db:92:13:ba
    inet6 fe80::20b:dbff:fe92:13ba%bge0 prefixlen 64 scopeid 0x2
    media: Ethernet autoselect (100baseTX <full-duplex>)
    status: active
    bge1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    options=9b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum>ether 00:0b:db:92:13:bb
    inet 10.112.35.13 netmask 0xffffffe0 broadcast 10.112.35.31
    inet6 fe80::20b:dbff:fe92:13bb%bge1 prefixlen 64 scopeid 0x3
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
    lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
    options=3 <rxcsum,txcsum>inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
    inet 127.0.0.1 netmask 0xff000000
    pfsync0: flags=0<> metric 0 mtu 1460
    syncpeer: 224.0.0.240 maxupd: 128
    pflog0: flags=100 <promisc>metric 0 mtu 33200
    enc0: flags=0<> metric 0 mtu 1536
    pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
    inet6 fe80::211:d8ff:fe8d:d2fd%pppoe0 prefixlen 64 scopeid 0x8
    inet 78.34.x.x –> 195.14.y.y netmask 0xffffffff

    bge0 is wan, bge1 lan.</up,pointopoint,running,noarp,simplex,multicast></promisc></rxcsum,txcsum></up,loopback,running,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum></up,broadcast,running,simplex,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum></up,broadcast,running,simplex,multicast>

    0
  • E

    you are on pppoe and your pppoe0 has ip only that your isp is not disconnecting you properly i would say.

    0
  • _

    Hmmm, with pfsense 1.2.3 it works like a charm. Connect and disconnect. No problems.
    But nevertheless i think, even if my ISP will do strange things, shouldn't pfsense handle this in a way like a nice piece of software?

    Other strange thing with the update of december 06 is, that on reconnect i have to wait something about one minute to get a connection which works. Say i see the interface up, but a ping results in this:

    36 bytes from pfsense.local (10.112.35.13): Destination Host Unreachable
    Vr HL TOS  Len  ID Flg  off TTL Pro  cks      Src      Dst
    4  5  00 5400 f82f  0 0000  3f  01 0454 10.112.35.2  193.99.144.80

    36 bytes from pfsense.local (10.112.35.13): Destination Host Unreachable
    Vr HL TOS  Len  ID Flg  off TTL Pro  cks      Src      Dst
    4  5  00 5400 1033  0 0000  3f  01 ec50 10.112.35.2  193.99.144.80

    ^C
    –- heise.de ping statistics ---
    404 packets transmitted, 0 packets received, 100% packet loss
    Exit 2
                                                                                                                                                                                          #                                                                                                                                                                                                                                                                                                                        > ping heise.de
    PING heise.de (193.99.144.80): 56 data bytes
    64 bytes from 193.99.144.80: icmp_seq=0 ttl=246 time=10.775 ms
    64 bytes from 193.99.144.80: icmp_seq=1 ttl=246 time=10.207 ms
    ^C

    Same thing with all connections like browser and so. I have to wait about a minute to get a reliable connection. Thios is a completely new behaviour. With releases before dec 06 it was not like this.

    0
  • C

    what do your system logs show?

    0
  • C

    I've a problem that maybe is related or the same.

    In 1.2.3 when I connect to my ISP with PPPoE I've realized that in Status>Interface the "ISP DNS Servers" doesn't appears right away, only after 1 minute of receiving an IP address, the "ISP DNS Servers" are populated. Any machine behind pfsense start resolving domains after this 1 minute delay. Anyway, past this 1 minute time all PC behind the firewall works ok.

    In 2.0 ALPHA (build from dec 12), it happens the same way but the "ISP DNS Servers" never are populated, the firewall doesn't have a DNS server in WAN, and with Diagnostics>DNS Lookup any domain entered result in an error, not resolving.

    In System log I've noticed that MPD is killed immediately after establishing the PPPoE connection, and before receiving the DNS server from my ISP.

    So in conclusion, 2.0 ALPHA NEVER works with PPPoE with my ISP, 1.2.3 works like a charm in the same ISP.

    Is there a way to setup a custom DNS server for WAN with PPPoE?

    0
  • G

    @casinmirad:

    Is there a way to setup a custom DNS server for WAN with PPPoE?

    You can enter up to 4 DNS servers in System: General Setup.
    (e.g. 8.8.4.4 for the new Google DNS!)

    0
  • C

    @casinmirad:

    In System log I've noticed that MPD is killed immediately after establishing the PPPoE connection, and before receiving the DNS server from my ISP.

    Please paste all mpd logs from your system logs.

    0
  • _

    I sent you a PM, cmb. Thanks in advance!

    0
  • _

    Here the last logs from mpd:

    Dec 14 23:41:23 pfsense mpd: PPPoE: rec'd ACNAME "netdsl"
    Dec 14 23:41:23 pfsense mpd: [pppoeclient] PPPoE: connection successful
    Dec 14 23:41:23 pfsense mpd: [pppoeclient] link: UP event
    Dec 14 23:41:23 pfsense mpd: [pppoeclient] link: origination is local
    Dec 14 23:41:23 pfsense mpd: [pppoeclient] LCP: Up event
    Dec 14 23:41:23 pfsense mpd: [pppoeclient] LCP: state change Starting –> Req-Sent
    Dec 14 23:41:23 pfsense mpd: [pppoeclient] LCP: SendConfigReq #16
    Dec 14 23:41:23 pfsense mpd:  MRU 1492
    Dec 14 23:41:23 pfsense mpd:  MAGICNUM 603dfef4
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: rec'd Configure Request #6 (Req-Sent)
    Dec 14 23:41:24 pfsense mpd:  MRU 1492
    Dec 14 23:41:24 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:41:24 pfsense mpd:  MAGICNUM 5651823c
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: SendConfigAck #6
    Dec 14 23:41:24 pfsense mpd:  MRU 1492
    Dec 14 23:41:24 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:41:24 pfsense mpd:  MAGICNUM 5651823c
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: state change Req-Sent –> Ack-Sent
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: rec'd Configure Ack #16 (Ack-Sent)
    Dec 14 23:41:24 pfsense mpd:  MRU 1492
    Dec 14 23:41:24 pfsense mpd:  MAGICNUM 603dfef4
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: state change Ack-Sent –> Opened
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: auth: peer wants PAP, I want nothing
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] PAP: using authname "nc-ochska2@netcologne.de"
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] PAP: sending REQUEST len:32
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: LayerUp
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] PAP: rec'd NAK #1
    Dec 14 23:41:24 pfsense mpd:  MESG: Request Denied
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: authorization failed
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: parameter negotiation failed
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: state change Opened –> Stopping
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] AUTH: Cleanup
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: SendTerminateReq #17
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: LayerDown
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: rec'd Terminate Request #7 (Stopping)
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: SendTerminateAck #18
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: rec'd Terminate Ack #17 (Stopping)
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: state change Stopping –> Stopped
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: LayerFinish
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] link: reconnection attempt 6
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: state change Stopped –> Starting
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] LCP: LayerStart
    Dec 14 23:41:24 pfsense mpd: [pppoeclient] pausing 5 seconds before open
    Dec 14 23:41:24 pfsense php: : Could not find gateway for interface(wan).
    Dec 14 23:41:24 pfsense last message repeated 6 times
    snipped other things…
    Dec 14 23:41:29 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:41:38 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:41:38 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:41:38 pfsense mpd: [pppoeclient] link: reconnection attempt 7
    Dec 14 23:41:38 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:41:38 pfsense mpd: [pppoeclient] pausing 6 seconds before open
    Dec 14 23:41:39 pfsense php: : Could not find gateway for interface(wan).
    Dec 14 23:41:39 pfsense last message repeated 6 times
    Dec 14 23:41:41 pfsense check_reload_status: reloading filter
    Dec 14 23:41:42 pfsense php: : Could not find gateway for interface(wan).
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:41:44 pfsense mpd: PPPoE: rec'd ACNAME "netdsl"
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] PPPoE: connection successful
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] link: UP event
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] link: origination is local
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: Up event
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: state change Starting –> Req-Sent
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: SendConfigReq #19
    Dec 14 23:41:44 pfsense mpd:  MRU 1492
    Dec 14 23:41:44 pfsense mpd:  MAGICNUM c01eb27e
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: rec'd Configure Request #62 (Req-Sent)
    Dec 14 23:41:44 pfsense mpd:  MRU 1492
    Dec 14 23:41:44 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:41:44 pfsense mpd:  MAGICNUM 3bf57d5d
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: SendConfigAck #62
    Dec 14 23:41:44 pfsense mpd:  MRU 1492
    Dec 14 23:41:44 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:41:44 pfsense mpd:  MAGICNUM 3bf57d5d
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: state change Req-Sent –> Ack-Sent
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: rec'd Configure Ack #19 (Ack-Sent)
    Dec 14 23:41:44 pfsense mpd:  MRU 1492
    Dec 14 23:41:44 pfsense mpd:  MAGICNUM c01eb27e
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: state change Ack-Sent –> Opened
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: auth: peer wants PAP, I want nothing
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] PAP: using authname "nc-ochska2@netcologne.de"
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] PAP: sending REQUEST len:32
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: LayerUp
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] PAP: rec'd NAK #1
    Dec 14 23:41:44 pfsense mpd:  MESG: Request Denied
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: authorization failed
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: parameter negotiation failed
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: state change Opened –> Stopping
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] AUTH: Cleanup
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: SendTerminateReq #20
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: LayerDown
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: rec'd Terminate Request #63 (Stopping)
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: SendTerminateAck #21
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] PPPoE: connection closed
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] link: reconnection attempt 8
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] LCP: state change Stopping –> Starting
    Dec 14 23:41:44 pfsense mpd: [pppoeclient] pausing 6 seconds before open
    Dec 14 23:41:50 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:41:59 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:41:59 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:41:59 pfsense mpd: [pppoeclient] link: reconnection attempt 9
    Dec 14 23:41:59 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:41:59 pfsense mpd: [pppoeclient] pausing 5 seconds before open
    Dec 14 23:42:04 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:42:13 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:42:13 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:42:13 pfsense mpd: [pppoeclient] link: reconnection attempt 10
    Dec 14 23:42:13 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:42:13 pfsense mpd: [pppoeclient] pausing 6 seconds before open
    Dec 14 23:41:42 pfsense last message repeated 6 times
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:42:19 pfsense mpd: PPPoE: rec'd ACNAME "netdsl"
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] PPPoE: connection successful
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] link: UP event
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] link: origination is local
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: Up event
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: state change Starting –> Req-Sent
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: SendConfigReq #22
    Dec 14 23:42:19 pfsense mpd:  MRU 1492
    Dec 14 23:42:19 pfsense mpd:  MAGICNUM eabacaf8
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: rec'd Configure Request #104 (Req-Sent)
    Dec 14 23:42:19 pfsense mpd:  MRU 1492
    Dec 14 23:42:19 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:42:19 pfsense mpd:  MAGICNUM 358fa2c2
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: SendConfigAck #104
    Dec 14 23:42:19 pfsense mpd:  MRU 1492
    Dec 14 23:42:19 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:42:19 pfsense mpd:  MAGICNUM 358fa2c2
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: state change Req-Sent –> Ack-Sent
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: rec'd Configure Ack #22 (Ack-Sent)
    Dec 14 23:42:19 pfsense mpd:  MRU 1492
    Dec 14 23:42:19 pfsense mpd:  MAGICNUM eabacaf8
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: state change Ack-Sent –> Opened
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: auth: peer wants PAP, I want nothing
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] PAP: using authname "nc-ochska2@netcologne.de"
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] PAP: sending REQUEST len:32
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: LayerUp
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] PAP: rec'd NAK #1
    Dec 14 23:42:19 pfsense mpd:  MESG: Request Denied
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: authorization failed
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: parameter negotiation failed
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: state change Opened –> Stopping
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] AUTH: Cleanup
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: SendTerminateReq #23
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: LayerDown
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: rec'd Terminate Request #105 (Stopping)
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: SendTerminateAck #24
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: rec'd Terminate Ack #23 (Stopping)
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: state change Stopping –> Stopped
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: LayerFinish
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] link: reconnection attempt 11
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: state change Stopped –> Starting
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: LayerStart
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] pausing 6 seconds before open
    Dec 14 23:42:25 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:42:34 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:42:34 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:42:34 pfsense mpd: [pppoeclient] link: reconnection attempt 12
    Dec 14 23:42:34 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:42:34 pfsense mpd: [pppoeclient] pausing 6 seconds before open
    Dec 14 23:42:40 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:42:49 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:42:49 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:42:49 pfsense mpd: [pppoeclient] link: reconnection attempt 13
    Dec 14 23:42:49 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:42:49 pfsense mpd: [pppoeclient] pausing 6 seconds before open
    Dec 14 23:42:55 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:43:04 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:43:04 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:43:04 pfsense mpd: [pppoeclient] link: reconnection attempt 14
    Dec 14 23:43:04 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:43:04 pfsense mpd: [pppoeclient] pausing 5 seconds before open
    Dec 14 23:43:09 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:43:18 pfsense mpd: [pppoeclient] PPPoE connection timeout after 9 seconds
    Dec 14 23:43:18 pfsense mpd: [pppoeclient] link: DOWN event
    Dec 14 23:43:18 pfsense mpd: [pppoeclient] link: reconnection attempt 15
    Dec 14 23:43:18 pfsense mpd: [pppoeclient] LCP: Down event
    Dec 14 23:43:18 pfsense mpd: [pppoeclient] pausing 5 seconds before open
    Dec 14 23:43:23 pfsense mpd: [pppoeclient] PPPoE: Connecting to 'netdsl'
    Dec 14 23:43:24 pfsense mpd: PPPoE: rec'd ACNAME "netdsl"
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] PPPoE: connection successful
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] link: UP event
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] link: origination is local
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: Up event
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: state change Starting –> Req-Sent
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: SendConfigReq #25
    Dec 14 23:43:24 pfsense mpd:  MRU 1492
    Dec 14 23:43:24 pfsense mpd:  MAGICNUM 45d3319c
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: rec'd Configure Request #190 (Req-Sent)
    Dec 14 23:43:24 pfsense mpd:  MRU 1492
    Dec 14 23:43:24 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:43:24 pfsense mpd:  MAGICNUM 0a298f03
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: SendConfigAck #190
    Dec 14 23:43:24 pfsense mpd:  MRU 1492
    Dec 14 23:43:24 pfsense mpd:  AUTHPROTO PAP
    Dec 14 23:43:24 pfsense mpd:  MAGICNUM 0a298f03
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: state change Req-Sent –> Ack-Sent
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: rec'd Configure Ack #25 (Ack-Sent)
    Dec 14 23:43:24 pfsense mpd:  MRU 1492
    Dec 14 23:43:24 pfsense mpd:  MAGICNUM 45d3319c
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: state change Ack-Sent –> Opened
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: auth: peer wants PAP, I want nothing
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] PAP: using authname "nc-ochska2@netcologne.de"
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] PAP: sending REQUEST len:32
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: LayerUp
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] PAP: rec'd ACK #1
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] LCP: authorization successful
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] Bundle up: 1 link, total bandwidth 64000 bps
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: Open event
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: state change Initial –> Starting
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: LayerStart
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: Up event
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: state change Starting –> Req-Sent
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: SendConfigReq #1
    Dec 14 23:43:24 pfsense mpd:  IPADDR 0.0.0.0
    Dec 14 23:43:24 pfsense mpd:  COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Dec 14 23:43:24 pfsense mpd:  PRIDNS 0.0.0.0
    Dec 14 23:43:24 pfsense mpd:  SECDNS 0.0.0.0
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: rec'd Configure Reject #1 (Req-Sent)
    Dec 14 23:43:24 pfsense mpd:  COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: SendConfigReq #2
    Dec 14 23:43:24 pfsense mpd:  IPADDR 0.0.0.0
    Dec 14 23:43:24 pfsense mpd:  PRIDNS 0.0.0.0
    Dec 14 23:43:24 pfsense mpd:  SECDNS 0.0.0.0
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: rec'd Configure Nak #2 (Req-Sent)
    Dec 14 23:43:24 pfsense mpd:  IPADDR 78.34.176.178
    Dec 14 23:43:24 pfsense mpd:    78.34.176.178 is OK
    Dec 14 23:43:24 pfsense mpd:  PRIDNS 81.173.194.76
    Dec 14 23:43:24 pfsense mpd:  SECDNS 81.173.194.69
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: SendConfigReq #3
    Dec 14 23:43:24 pfsense mpd:  IPADDR 78.34.176.178
    Dec 14 23:43:24 pfsense mpd:  PRIDNS 81.173.194.76
    Dec 14 23:43:24 pfsense mpd:  SECDNS 81.173.194.69
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: rec'd Configure Ack #3 (Req-Sent)
    Dec 14 23:43:24 pfsense mpd:  IPADDR 78.34.176.178
    Dec 14 23:43:24 pfsense mpd:  PRIDNS 81.173.194.76
    Dec 14 23:43:24 pfsense mpd:  SECDNS 81.173.194.69
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: state change Req-Sent –> Ack-Rcvd
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: rec'd Configure Request #43 (Ack-Rcvd)
    Dec 14 23:43:24 pfsense mpd:  IPADDR 195.14.226.7
    Dec 14 23:43:24 pfsense mpd:    195.14.226.7 is OK
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: SendConfigAck #43
    Dec 14 23:43:24 pfsense mpd:  IPADDR 195.14.226.7
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: state change Ack-Rcvd –> Opened
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IPCP: LayerUp
    Dec 14 23:43:24 pfsense mpd:  78.34.176.178 -> 195.14.226.7
    Dec 14 23:43:24 pfsense mpd: [pppoeclient] IFACE: Up event
    Dec 14 23:43:28 pfsense check_reload_status: rc.newwanip starting
    end of connect, here i had to wait maybe 4-5 minutes to get a connection to internet.

    0
  • A

    I am seeing similar problems with a number of the recent snapshots.

    I am using a wireless provider and many of the times when my connection goes down and fails to come back up seem to coincide with bad weather.

    Below is an extract from my logs… The WAN went down at around 00:00 (according to my graphs) and came back when I hit the 'connect' button this morning at about 7:30.

    Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] link: DOWN event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] link: reconnection attempt 1
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] LCP: Down event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] LCP: state change Opened --> Starting
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] AUTH: Accounting data for user : 17470 seconds, 103489106 octets in, 12456702 octets out
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] Bundle up: 0 links, total bandwidth 9600 bps
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: Close event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: state change Opened --> Closing
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: SendTerminateReq #4
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] error writing len 8 frame to bypass: Network is down
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: LayerDown
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IFACE: Delete route 0.0.0.0/0 196.2.112.1 failed: No such process
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IFACE: Removing IPv4 address from pppoe0 failed: Device not configured
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] can't remove hook inet from node "pppoe0:": No such file or directory
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IFACE: Down event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IFACE: ioctl(pppoe0, SIOCGIFFLAGS): Device not configured
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: Down event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: LayerFinish
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] No NCPs left. Closing links...
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] closing link "pppoeclient"...
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] IPCP: state change Closing --> Initial
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] AUTH: Cleanup
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] LCP: LayerDown
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] link: CLOSE event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] LCP: Close event
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] LCP: state change Starting --> Initial
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] LCP: LayerFinish
Dec 15 00:09:34 pfSense2 mpd: [pppoeclient] pausing 5 seconds before open
Dec 15 07:24:17 pfSense2 mpd: caught fatal signal term
Dec 15 07:24:17 pfSense2 mpd: [pppoeclient] IFACE: Close event
Dec 15 07:24:17 pfSense2 mpd: [pppoeclient] IPCP: Close event
Dec 15 07:24:19 pfSense2 mpd: process 17585 terminated
Dec 15 07:24:19 pfSense2 mpd: Multi-link PPP daemon for FreeBSD
Dec 15 07:24:19 pfSense2 mpd:  
Dec 15 07:24:19 pfSense2 mpd: process 36029 started, version 4.4.1 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org 17:43  5-Nov-2009)
Dec 15 07:24:19 pfSense2 mpd: [pppoeclient] using interface pppoe0
Dec 15 07:24:19 pfSense2 mpd: [pppoeclient] link: OPEN event
Dec 15 07:24:19 pfSense2 mpd: [pppoeclient] LCP: Open event
Dec 15 07:24:19 pfSense2 mpd: [pppoeclient] LCP: state change Initial --> Starting
Dec 15 07:24:19 pfSense2 mpd: [pppoeclient] LCP: LayerStart
Dec 15 07:24:19 pfSense2 mpd: [pppoeclient] PPPoE: Connecting to ''
Dec 15 07:24:19 pfSense2 mpd: PPPoE: rec'd ACNAME "00:C0:EE:C9:05:6A"
Dec 15 07:24:20 pfSense2 mpd: [pppoeclient] PPPoE: connection successful
    0
  • E

    igor

    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: authorization failed
    Dec 14 23:42:19 pfsense mpd: [pppoeclient] LCP: parameter negotiation failed

    0
  • _

    I've seen this, but with pfSense 1.2.x it works great. Auto-connect occurs whenever pfSense disconnects.
    When i connect manually, mpd tries several times to get a connect. Thats good. When a request from network comes to connect, nothing happens. No entry in system.log, only notice is "Not available" inside browser or other programs which try to connect.

    Auto-connect doesn't occur with 2.0. Whenever I want to connect i have to do it manually. Even trying with a ping in background pfSense disconnects from time to time and refuses to connect again.
    I made a new install without packages to not disturb the system with eventually broken packages. Same thing.

    Whenever the connection refuses to send/recieve data even when manual connect was successful, i sometimes have luck when starting the initial wizard, going thru it without changing anything. After saving the settings the connection works. But not everytime. Sometimes a reboot helps to get it pasing data from out/in to in/out. Very strange.
    Sometimes I have to make a new "update" with the same version to get it running. Whenever this happens, the pause between connection and passing data is gone, say, when I connect i can surf directly without pause.

    0
  • E

    Post the 1.2 mpd log as you did for 2.0 to verify this.

    0
  • _

    Here we go:

    Edit: the whole thing is too long, added the whole file.

    system.txt

    0
  • E

    It is something regarding your ISP that does not de-authenticate you correctly and something has changed in mpd to make it more strict on later versions.
    It needs more investigation and more time though i have not much as of now.

    Though you can take a packet trace and attach it here so i can follow later on.

    0
  • _

    ok, will do. Should I do it with the 2.0 or the 1.2.3? I think it should be tcpdump, but how should I do this? Looked around the man-page, but i don't understand it much.

    Should it be like this?

    tcpdump -i bge0 -n ether proto 0x8863 '||' ether proto 0x8864

    assuming that bge0 is my wan-interface.

    0
  • _

    ok, the tcpdump in the mentioned way only worked with pfSense 1.2.3, so for 2.0 I did 2 separate tcpdumps. Strange…
    Hope it helps.

    First I disconnected the wan-IF, auto-connect worked on 1.2.3, so no further things to do. Surfed around, disconnected some times.
    Same on 2.0, except the failing autoconnect. So I connected via Button, surfed, disconnected and connected several times.

    If you need more, tell me please.
    I zipped the files and attached .txt to upload it. Please remove the .txt to get the zip back.

    tcpdump.zip.txt

    0
  • A

    @ermal:

    something has changed in mpd to make it more strict on later versions

    It seems to me that mpd stops reconnecting when it experiences a connect fail or auth fail. Can't say whether this is a feature or a bug but it is definitely a problem.

    Even a connection that has auth failed should be retried periodically since the reason for the failure can go away and one would expect pfSense to recover from this within a reasonable time and without intervention.

    0
  • ?

    I have a similar problem, PPOe disconnects every day, and don't connect back again automatically, I have to do it manually, with version 1.2.3 and previous this work perfectly, if ppoe disconnects for any reason it reconnects automatically.

    0
  • N

    Hi.

    I've no clue how it was done in 1.2.x but just wondering if you guys force mpd to re-establish a connection by adding "set bundle no noretry" into appropriate section of your interfaces.inc. This will force mpd to re-connect whenever the keep-alive expires. Or sit tight and wait for it'd be fixed eventually in any later builds…

    cheers,

    0
  • _

    Thanks much! I'll try it.

    0
  • M

    This problem not only for PPoE.
    I use separate PPTP mpd client connection. After linkdown sometimes reconnect sucsessful, but many times not.
    Additional:
    1. Cannot set MTU for PPTP link.
    2. Static routes for PPTP link not activating after link down/up.

    0
  • _

    It doesn't work. As I can see, mpd dies when a disconnect occurs. Logs show this: (reverse order)

    Jan 17 19:58:47  mpd:
    Jan 17 19:58:47  mpd: Multi-link PPP daemon for FreeBSD
    Jan 17 19:58:46  mpd: process 37549 terminated
    Jan 17 19:58:44  mpd: caught fatal signal term
    Jan 17 19:57:41  last message repeated 7 times

    cat /var/etc/mpd_wan.conf
    startup:
    pppoeclient:
      new -i pppoe0 pppoeclient pppoeclient
      set iface route default
      set iface enable 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 iface addrs 192.0.2.112 192.0.2.113
      set bundle disable multilink
      set bundle no noretry
      set auth authname "xxx"
      set auth password "yyy"
      set link keep-alive 10 60
      set link max-redial 0
      set link no acfcomp protocomp
      set link disable pap chap
      set link accept chap
          set link mtu 1492
      set ipcp yes vjcomp
      set ipcp ranges 0.0.0.0/0 0.0.0.0/0
      set ipcp enable req-pri-dns
      set ipcp enable req-sec-dns
      open

    0
  • ?

    ¿Any news about this?

    I'm working with latest version, 2.0-BETA1 built on Fri Jan 22 00:26:29 EST 2010, and this problem persists, every morning I've to manually connect to my ISP.

    0
  • _

    Does the option "set bundle no noretry" help? Did you try it?

    0
  • N

    Hi,

    Again I have no clue about 1.2.x but auto-reconnect just works fine for me with;

    set link max-redial 0
    set bundle no noretry
    (set link keep-alive 5 15) <- 10 60 is way too loooooooong to me

    into my mpd.conf, just to clarify, I tested this by disconnecting utp to the modem, wait 'till keep-alive expired
    then connect the utp to the modem again, link re-established again. Need to flush routing table some times.
    Any chances to try on-demand mode instead if you've outgoing traffic constantly.

    It's about to consider moving to mpd5 since it's been there for a while and quite stable for now…

    cheers,

    0
  • ?

    Thanks for your comments, I did it yesterday, adding the "set bundle no noretry" and it seems to be working:

    $mpdconf .= << <eod<br>set bundle disable multilink
    set auth authname "{$wancfg['pppoe_username']}"
    set auth password "{$wancfg['pppoe_password']}"
    set bundle no noretry
    set link keep-alive 10 60
    set link max-redial 0
    set link no acfcomp protocomp
    set link disable pap chap
    set link accept chap

    If it's fails again I will try with "set link keep-alive 5 15"

    Thanks</eod<br>

    0
  • ?

    It fails again, so I'll try with, "set link keep-alive 5 15"

    Besides I update to latest version (2.0-BETA1 built on Mon Jan 25 20:57:42 EST 2010)
    The modifications goes away with firmware updates, so I've to re-write these modifications.

    Regards
    Alfredo

    0
  • _

    In my case none of the otions work. Connection fails every several hours. Its a really awful thing. Its beginning to drive me a bit crazy. I'm thinking that the whole thing fails because of routing. There is a default route to ISP-IP, but the whole thing looks a bit strange to me:

    
default	               195.14.226.7	UGS	0	42483	        1492	        pppoe0	 
10.0.0.0/27	        link#3	        U	8	248149868	1500	        bge1	 
10.0.0.1	                link#3	        UHS	0	1068827	        16384	lo0	 
10.0.0.32	                link#9	        UHS	0	0	                16384	lo0	=>
10.0.0.32/29      	link#9	        U	0	0	                1500	        ral0_wlan0	 
87.78.x.y	                link#8	        UHS	0	0	                16384	lo0	 
127.0.0.1             	link#4	        UH	0	4289065	        16384	lo0	 
127.0.0.2	                127.0.0.1	        UHS	0	1068827	        16384	lo0	 
195.14.226.7      	link#8	        UH	0	0	                1492 	pppoe0

    Where is the use of Link 8? Transfer 0 byte? Both related to my ISP! No use of the links. And last but not least, on dashboard my WAN-gateway is stuck on "Gathering data". Apart from the fact that the whole routing seems to be on heavy construction. Therre was a time when I could change things in the routing, but since a time I cannot do anythiong there, only errors appear there. Maybe I'm wrong, but it looks a bit strange to me.

    0
  • jimp
    Rebel Alliance Developer Netgate

    I'm in a rather unique situation to test this repeatedly, as I control both ends of the PPPoE link I have a test box hooked to. I have a 2.0 test box sitting on my test PPPoE DSL line at work and I also control the router on the other end of the link, so I can boot it at will.

    I did confirm (as others have seen) that not only does PPPoE not reconnect, if the interface is unplugged at boot time, it doesn't try to connect initially either.

    If I use "set bundle no noretry" it falls into a loop where it just constantly tries to connect after making a good PPPoE link. I see it authenticate on the ISP end and MPD immediately says the link has gone and tries to redial. The keep alive settings made no difference.

    If I get some more time tomorrow at work I'll try to tinker with this, but it may have to wait for the weekend.

    0
  • _

    This are great news! The "set bundle no noretry" doesn't help. Same as before. :-( But I'll wait and then try with a new install. Maybe that helps.

    0
  • M

    For me the same problem. Here my subject :http://forum.pfsense.org/index.php/topic,22145.0.html
    Correction mpd_wan.conf has not helped.
    The problem what is not right enough for MPD for change of a configuration of interfaces can?
    Excuse for bad English language, I badly know it.

    0
  • A

    in pfsense 1.2.3 the wan/pppoe mpd.conf has the "no noretry" option set.
    in pfsense 2.0 it's not set…

    1.2.3 uses freebsd's mpd version 3.18 and
    2.0 uses mpd version 4.4.1, so it's mpd related?? (guess not)

    @jimp:

    …
    If I use "set bundle no noretry" it falls into a loop where it just constantly tries to connect after making a good PPPoE link. I see it authenticate on the ISP end and MPD immediately says the link has gone and tries to redial. The keep alive settings made no difference.
    ...

    as the6thday wrote: it's pretty much unusable (for most german dsl users) :/

    but i have some hopes. (or at least a workaround…)
    i never tried freebsd / monowall or pfsense before, so prepare that i may have a lot of questions.

    i first started with a 2.0b live cd, got the reconnection problem and soon got into this sub-forum.
    i now have 1.2.3 upgraded to 2.0b (so old binaries (like mpd) are still on the partition) and done some modifications for testing...

    but more on this after my next reconnect g

    sorry for this german/english
    // edit - fix url typo, cut off quote

    0
  • _

    Same thing happend to me too, but not everytime. So sometimes it was in a loop getting indefinitely a new IP. Pressing the "connect"-button established the connection.
    But afterwards I had/have to call the DynDNS-page and save to actualize the DynDNS-IP. rc.newwanIP was never called upon manual connect.

    Yesterday I did a complete new install because mpd died before and never "woke up" again. So I think, something broke up in my installation. mpd died instantly.
    Will see if now things are better.

    Update: After the fresh install I see that adding an external DNS-server results in the fact that my ISPs DNS-servers are not settled. No internet-activity possible. Even pfSense is not able to find updates. So only the external DNS is set. Deleting this DNS-entry results in an instantly added ISP-DNS and my Internet-connection works. pfSense finds its updates too.

    Looking in the logs I see after restart of pfSense 3 attempts to connect to my ISP Then the log spits out this:
    php: : The command 'fetch -o /dev/null -q https://localhost:443/preload.php' returned exit code '1', the output was 'fetch: https://localhost:443/preload.php: Unknown error: 0'.
    That was it. I will try to add the "no noretry"-option.
    When I manually connect I get the mentioned failings. Here mpd dies but restarts again (reverse order):

    mpd: Multi-link PPP daemon for FreeBSD
    Feb 19 11:07:37 mpd: process 6494 terminated
    Feb 19 11:07:35 mpd: caught fatal signal term
    Feb 19 11:07:27 php: : Could not find gateway for interface(wan).

    I will keep you updated.

    0
  • A

    hi igor,

    what do you mean by 'not everytime.' ?

    for nocer and afrugone it seems to work, so i tried the "no noretry" bundle option on mpd 4.4.1 some days ago,
    but like jimp and you wrote: it falls into a loop… fortunately i saw the loop 2 minutes later g

    currently i'm writing with my new wan-pppoe ip - no need to manual reconnect for now. but here is the catch,
    my pfsense 2.0 runs the old mpd 3.18 with the ng networking subsystem.
    and here is a first quick freebsd question:
    what / where are the diffs between ng0 (mpd3) and pppoe0 (mpd4)?

    dyndns upate seems to work… but dnsmasq was invoked later, so that may be another order issue...
    luckily i have the same dns(s) like yesterday, (as per mpd: they are really the same), so dyndns was successfully...

    i may setup and try mpd 4.4.1 with my modifications...
    why has the "no noretry" option been removed from the pppoe interface.inc section?

    ps: after i saw the preload file, i understood the unknown error from fetch g
    (joke, i know the preload.php exists longer… but that's not nice for the php interpreter)

    0
  • _

    The loop only 2 or 3 times. Mostly not. Due to the spare times it looped I didn't think to mention it. Difficult to fix something like this.

    0
  • ?

    Only to clarify, for me is not working perfectly, is better, but after some days (about a week) I get the same problem, and I have to manully reconnect

    0
  • A

    …loop only 2 or 3 times. / ...after some days (about a week) ...

    don't dash my hopes, cause i'm now running the mpd 4.4.1 setup in my pfsense 2.0b setup.
    nocer has also mentioned to use the last stable mpd5 … are you in favour?
    (seems that the hole pppoe link type part has been rewritten.)

    afrugone, igor, would you test my mods (some files - you only need little ssh / scp skills)?
    what versions / setups are you running on your pfsense boxes?
    multi-wan pppoe? multi dyndns? snapshot date? are you willing to update?

    another mpd question: how important is the 'tcpmssfix' option for pppoe (since, if the mtu is empty, it's set to 1492)?
    btw. (ot): there might be another dyndns issue, if you have multiple accounts for the same service/provider.

    0
  • _

    Latest update is that PPPOE is nearly not usable. My connection is lost every 5 or 10 mins, reconnect only manually, with the "bundle no noretry" I get stuck in endless loops of mpd reconnecting endless. No Dyndns-Update ocurrs, connection is passing traffic only if I hit "save" in "General setup". Its more than strange. Looks like voodoo.
    With the latest update it seems to be worse than ever: I'm getting endless delays and packet loss. Things that never happend before. The whole pfSense-box seems to stall after a while. Connection is getting slower and slower, logs are flooded wiith apinger warnings. When I reboot the box all is gettig ok for some minutes. Then all is getting slow again. Doesn't matter if there is traffic or not. Dashboard shows a cpu of 1-2%, net traffic is nearly nothing but a great slowdown occurs.
    At the moment I see that lots of changes occur, but PPPOE seems to be a strange thing. With 1.2.3 no problem at all. Ok, I need some features of 2.0, but I'm more than willing to test every thing to get a better response here. Even if it gets worse, but I don't think so.

    @antiben: Throw me your changes, I'll test it! I don't have programming skills but know something about how to use ssh and console.

    0
  • A

    ok, i'll prepare everything in a tgz file. base is the last build 20100221-0133
    maybe it could all be done with pfsense's exec.php (diagnostics/command prompt).
    precondition is, that my reconnect and dyndns-update works… (in about 4h) g

    but despite everything, connection lost every 5 or 10 mins sounds differently from the 24h forced disconnect/reconnect…
    can you quickly post your hardware setup? (or have you post it anywhere else before?)

    //edit typo, changed build link from 20100220-0923 to 20100221-0133,
    last changes doesn't affect interface/pppoe/mpd stuff

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

© 2020 Rubicon Communications, LLC | Privacy Policy