Re: PPPoE misbehaving?

From: Chris Knipe (savage_at_savage.za.org)
Date: 07/19/04

  • Next message: Gleb Smirnoff: "Re: PPPoE misbehaving?"
    To: "Gleb Smirnoff" <glebius@freebsd.org>
    Date: Mon, 19 Jul 2004 02:17:00 +0200
    
    

    Hi Gleb and the rest,

    Thank you all for the replies. The card is a Senao NL-2054PCI, based on the
    Atheros chipset... pciconf -lv reports:

    ath0@pci0:9:0: class=0x020000 card=0x2027168c chip=0x0013168c rev=0x01
    hdr=0x00
        vendor = 'Atheros Communications Inc.'
        device = '802/11b/g AR5212 wireless Adapter'
        class = network
        subclass = ethernet

    As I did indicate, the card is working and functioning properly - I am 99%
    sure it is a problem related with PPPoEd, or something in regards to PPPoE
    over the Ethernet card (which, can also be possible I guess). I've tried
    all the other suggestions that was made, and none of them seemed to have
    changed anything. From what I can see, the client sends and attempts to
    initiate the PPPoE connection properly, but the PPPoE daemon does not
    receive the packets / or does not initiate a session - which, needs to be
    completed before any sub processes will be spawned.

    It's quite urgent that I get this working.... An alternative would be to
    port the ath drivers to the 4.X tree - but I really don't think that's even
    a option.... I can only imagine the amount of work that would be required
    for this. Are there possibly any other open source PPPoE Daemons available
    that I can possibly try on FreeBSD 5.2??

    Look forward to hearing from you all

    --
    me
    ----- Original Message ----- 
    From: "Gleb Smirnoff" <glebius@freebsd.org>
    To: "Chris Knipe" <savage@savage.za.org>
    Sent: Friday, July 16, 2004 9:35 PM
    Subject: Re: PPPoE misbehaving?
    >   Chris,
    >
    >   what network card do you have?
    >
    > On Fri, Jul 16, 2004 at 07:53:21PM +0200, Martin wrote:
    > M> Am Fr, den 16.07.2004 schrieb Chris Knipe um 12:44:
    > M>
    > M> > Also fine....  Lastly, the client fires off a PPPoE session...
    TCPDump shows
    > M> > the packets without problems...
    > M> > tcpdump: listening on ath0
    > M> > 12:31:09.050286 PPPoE PADI [Service-Name] [Host-Uniq UTF8]
    > M> > 12:31:09.122091 PPPoE PADI [Service-Name] [Host-Uniq UTF8]
    > M> > ^C
    > M> > 2 packets received by filter
    > M> > 0 packets dropped by kernel
    > M> >
    > M> > However, the PPPoE Deamon simply does not pick it up and does
    nothing.  No
    > M> > session is initiated, no ppp processes are spawned, nothing...
    > M>
    > M> I submitted a PR (kern/69133) about this:
    > M> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F69133
    > M>
    > M> >  Has
    > M> > something changed?????
    > M>
    > M> PPPoE is broken for me on -CURRENT, too, now since about 2 weeks.
    > M>
    > M> Martin
    > M>
    > M>
    > M> _______________________________________________
    > M> freebsd-current@freebsd.org mailing list
    > M> http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > M> To unsubscribe, send any mail to
    "freebsd-current-unsubscribe@freebsd.org"
    >
    > -- 
    > Totus tuus, Glebius.
    > GLEBIUS-RIPN GLEB-RIPE
    >
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Gleb Smirnoff: "Re: PPPoE misbehaving?"

    Relevant Pages

    • Re: chelsio driver and Myricom driver
      ... firmware will be automatically be updated when you up an interface on ... I just figured that out a few min ago by accident and the card looks happy now! ... Last clearing of "show interface" counters never ... input packets with dribble condition detected ...
      (freebsd-current)
    • Re: Restarting ADSL Connection Problem
      ... >> For PPPoE the MTU should be around 48 bytes larger than the MSS value. ... Ping some internet server and stipulate ... In the first example a payload of 1473 bytes is too large: ... packets transmitted, 0 packets received, 100.0% packet loss ...
      (comp.unix.bsd.openbsd.misc)
    • RE: Bluetooth Audio via CompactFlash PC card to Headset on WinCE5.0
      ... this fails with both the Brainboxes card and the Socket ... In HCI_WritePacket the queue should never have more than four packets. ... sent from HCI layer at a fast rate. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: em0 checksum errors
      ... >> I've been testing an application which uses UDP. ... The errors are mostly on UDP packets but I do ... >> This is reproducable on more than one system, although the NICs are ... moving the em0 card seems to fix the problem. ...
      (freebsd-stable)
    • Netgear MA401 stopped working
      ... the host, seem to be sending packets, but never receive anything back. ... PING 192.168.112.1: 56 data bytes ... I, on the other hand, suspect a hardware problem with the card. ... pci_cfgintr: 0:2 INTA BIOS irq 11 ...
      (freebsd-net)