Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Jul 2001 21:50:04 -0700 (PDT)
From:      Brad Laue <brad@brad-x.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/28974: PPPoE software fails when SOCK_RAW employed 
Message-ID:  <200107150450.f6F4o4U32581@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/28974; it has been noted by GNATS.

From: Brad Laue <brad@brad-x.com>
To: Brian Somers <brian@Awfulhak.org>
Cc: <FreeBSD-gnats-submit@FreeBSD.ORG>, <roman@xpert.com>
Subject: Re: kern/28974: PPPoE software fails when SOCK_RAW employed 
Date: Sun, 15 Jul 2001 00:48:41 -0400 (EDT)

 Hping is an example of the tool I used to further troubleshoot the
 problem, not the problem itself; PPPoE is definitely broken, and has been
 reported as such on several occasions, but in the wrong place.
 
 The problem is that what I used as a diagnostic is itself flawed to the
 point of not working with PPPoE based connections.
 
 I would still like to further understand why programs such as nmap
 are having such a difficult time working with a networking
 implementation that should by all rights be transparent.
 
 My only surmise to date is that since NetGraph is dealing with Raw
 Sockets to encapsulate PPPoE, it is interfering with userspace programs'
 ability to do same.
 
 I am however glad to have been able to point out the problematic port,
 being overproductive is a good thing. :)
 
 Here is an example of the problem as related by another person. I've had
 this identical issue, and have not yet corrected it:
 
 http://groups.google.com/groups?hl=en&safe=off&ic=1&th=7866b9324b3e2b97,2&seekm=002e01c0b710%24d3306da0%242ac67fd8_blah2%40ns.sol.net#p
 
 The surmise is misconfigured libcap, but this is nullified by the user's
 claim that nmap functions over interfaces not covered by PPPoE, also my
 experience.
 
 Please continue to consider this a PPPoE issue, but let me know if you'd
 like me to submit a PR regarding hping itself.
 
 Thanks,
 Brad
 
 On Sun, 15 Jul 2001, Brian Somers wrote:
 
 > brad, it seems that when the above two functions are made to work
 > (with a little hard-coding in my case), hpinging an address that's
 > reached through the tun interface over a PPPoE link works.  I think
 > you should raise several bug reports, one for each of the programs
 > that you find doesn't work.  Let's leave this one as applying to
 > hping.  Is that ok ?
 >
 > Cheers.
 >
 > --
 > Brian <brian@freebsd-services.com>                <brian@Awfulhak.org>
 >       http://www.freebsd-services.com/        <brian@[uk.]FreeBSD.org>
 > Don't _EVER_ lose your sense of humour !      <brian@[uk.]OpenBSD.org>
 >
 >
 > --- getifname.c.orig	Thu Jul  6 18:06:10 2000
 > +++ getifname.c	Sun Jul 15 02:52:01 2001
 > @@ -52,7 +52,7 @@
 >  	ifrp = ibuf;
 >  	ifend = (struct ifreq*) ((char*)ibuf + ifc.ifc_len);
 >
 > -	for (; ifrp < ifend; ifrp++) {
 > +	for (; ifrp < ifend; ifrp = (char *)&ifrp->ifr_addr + ifrp->ifr_addr.sa_len) {
 >  		strncpy(ifr.ifr_name, ifrp->ifr_name, sizeof(ifr.ifr_name));
 >
 >  		if ( ioctl(fd, SIOCGIFFLAGS, (char*)&ifr) == -1) {
 >
 >
 >
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107150450.f6F4o4U32581>