Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PPPoE - mpd: Error

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 1 Posters 5.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      t.A.t.t.
      last edited by

      Hi all,

      I'm using embeded pfSense image and running it on Alix. So far everything was fine. But now I experience problems with PPPoE (mpd).

      In pfSense's system log there appears the message:
      Apr 15 08:40:11 mpd: Incoming PPPoE connection request via vr0: for service "" from 00:11:09:70:1e:f0
      Apr 15 08:37:35 mpd: Incoming PPPoE connection request via vr0: for service "
      " from 00:03:0d:80:b1:49
      Apr 15 08:25:17 mpd: 192.168.120.1 -> 192.168.110.123
      Apr 15 08:25:17 mpd: IPADDR 192.168.110.123
      Apr 15 08:25:17 mpd: 192.168.110.123 is OK

      Since then all users (we have mostly Windows clients using XP and Vista) cannot authenticate to PPPoE getting "Error772: remote computer's network hardware is incompatible with the type of call requested."

      The only solution I have found so far is:
      i] I kill mpd by executing "kill -15 mpd" in pfSense command prompt
      ii] I start it again by executing "/usr/local/sbin/mpd -b -d /var/etc/mpd-vpn -p /var/run/mpd-vpn.pid pppoe"
      After this procedure PPPoE works again as seen in pfSense's system log:
      Apr 15 12:09:55 mpd: 192.168.120.1 -> 192.168.110.138
      Apr 15 12:09:55 mpd: IPADDR 192.168.110.138
      Apr 15 12:09:55 mpd: 192.168.110.138 is OK
      Apr 15 12:09:51 mpd: Incoming PPPoE connection request via vr0: for service "" from 00:0d:28:13:69:af
      Apr 15 12:09:45 mpd: mpd: pid 29909, version 3.18 (root@freebsd6.geekgod.com 12:32 6-Jan-2008)
      Apr 15 12:09:33 mpd: mpd: process 52693 terminated
      Apr 15 12:09:30 mpd: mpd: caught fatal signal term
      Apr 15 11:09:38 mpd: Incoming PPPoE connection request via vr0: for service "
      " from 00:11:09:70:1e:f0

      The only thing I found here in forum is aldo's reply in http://forum.pfsense.org/index.php/topic,1935.0.html post.

      But I don't think it is Windows issue as we have on our network Win2k, WinXP, Vista or Mac PPPoE clients. I was wondering if it couldn't be an MTU size issue?

      I will be glad for any advice.

      Thankx to all.

      1 Reply Last reply Reply Quote 0
      • T
        t.A.t.t.
        last edited by

        @t.A.t.t.:

        Hi all,

        I'm using embeded pfSense image and running it on Alix. So far everything was fine. But now I experience problems with PPPoE (mpd).

        In pfSense's system log there appears the message:
        Apr 15 08:40:11 mpd: Incoming PPPoE connection request via vr0: for service "" from 00:11:09:70:1e:f0
        Apr 15 08:37:35 mpd: Incoming PPPoE connection request via vr0: for service "
        " from 00:03:0d:80:b1:49
        Apr 15 08:25:17 mpd: 192.168.120.1 -> 192.168.110.123
        Apr 15 08:25:17 mpd: IPADDR 192.168.110.123
        Apr 15 08:25:17 mpd: 192.168.110.123 is OK

        Since then all users (we have mostly Windows clients using XP and Vista) cannot authenticate to PPPoE getting "Error772: remote computer's network hardware is incompatible with the type of call requested."

        The only solution I have found so far is:
        i] I kill mpd by executing "kill -15 mpd" in pfSense command prompt
        ii] I start it again by executing "/usr/local/sbin/mpd -b -d /var/etc/mpd-vpn -p /var/run/mpd-vpn.pid pppoe"
        After this procedure PPPoE works again as seen in pfSense's system log:
        Apr 15 12:09:55 mpd: 192.168.120.1 -> 192.168.110.138
        Apr 15 12:09:55 mpd: IPADDR 192.168.110.138
        Apr 15 12:09:55 mpd: 192.168.110.138 is OK
        Apr 15 12:09:51 mpd: Incoming PPPoE connection request via vr0: for service "" from 00:0d:28:13:69:af
        Apr 15 12:09:45 mpd: mpd: pid 29909, version 3.18 (root@freebsd6.geekgod.com 12:32 6-Jan-2008)
        Apr 15 12:09:33 mpd: mpd: process 52693 terminated
        Apr 15 12:09:30 mpd: mpd: caught fatal signal term
        Apr 15 11:09:38 mpd: Incoming PPPoE connection request via vr0: for service "
        " from 00:11:09:70:1e:f0

        The only thing I found here in forum is aldo's reply in http://forum.pfsense.org/index.php/topic,1935.0.html post.

        But I don't think it is Windows issue as we have on our network Win2k, WinXP, Vista or Mac PPPoE clients. I was wondering if it couldn't be an MTU size issue?

        I will be glad for any advice.

        Thankx to all.

        well, no one knows? will someno direct me?

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.