Hai ..
Hai Saya Latifah. Maaf jika saya mengganggu. Saya ada usul/cadangan peribadi, dimana saya ingin berbincang secara personal dan serius dengan anda. Harap balas. Yang benar, Latifah Bint Hamzah
Re: PPPoE support status update: problems with netgraph?
On Sat, May 08, 2010 at 06:27:10PM -0400, The Anarcat wrote: Right now, PPPoE doesn't work. The way I was able to compile ppp(8) was by disabling netgraph, which makes ppp(8) complain about PPPoE (my guess): Warning: deflink: PPPoE: unknown host Warning: deflink: Device (PPPoE:vr0) must begin with a '/', a '!' or contain at least one ':' I'll try to compile with netgraph support. In the meantime I would really appreciate further directions on the next steps I should take to package this officially and more details on how others have been able to make ppp work at all right now. Sorry to answer to my own posts, but I have some more progress here. 1. I have been able to compile a real Debian package of userland ppp for kfreebsd. It still has some rough edges (like dh_make templates lying around) but it's working generally well. 2. I've been able to compile ppp with netgraph support. 3. PPPoE, however, is still out of reach because netgraph refuses to work. Here's what I get when I try to connect through PPPoE: # ppp Working in interactive mode Warning: Add! route failed: ff02::/32: errno: Network is unreachable Using interface: tun0 ppp ON roadkiller dial eicat Warning: Cannot create netgraph socket node: Invalid argument ppp ON roadkiller quit ktrace shows me the following trace: 2828 ppp CALL socket(PF_NETGRAPH,SOCK_DGRAM,0x2) 2828 ppp RET socket 2 (here we see the socket gets created correctly...) 2828 ppp CALL sendto(0x2,0x80afc88,0x38,0,0xbfbfd196,0) 2828 ppp RET sendto -1 errno 22 Invalid argument (...but we can't write to it) 2828 ppp CALL close(0x2) 2828 ppp RET close 0 2828 ppp CALL write(0x1,0x2823e000,0x3e) 2828 ppp GIO fd 1 wrote 62 bytes Warning: Cannot create netgraph socket node: Invalid argument 2828 ppp RET write 62/0x3e Has anybody got netgraph to work properly on debian kfreebsd yet? Getting there though ... :) A. PS: I'll publish the debian package somewhere for review as soon as I have some time to cleanup the cruft lintian reports... -- L'ennui avec la grande famille humaine, c'est que tout le monde veut en être le père. - Mafalda signature.asc Description: Digital signature
Re: PPPoE support status update
On Sun, 9 May 2010 00:27, anar...@koumbit.org said: That I just don't understand at all... Are you using userland PPP? From what I can tell here, there's no ppp binary bundled with any kFreeBSD package I know of, I don't see how creating the lock directory changes I am using this: freebsd-hackedutils 6.1-3 Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87tyqhqflj@vigenere.g10code.de
Re: PPPoE support status update
On Sun, May 09, 2010 at 05:06:48PM +0200, Werner Koch wrote:
On Sun, 9 May 2010 00:27, anar...@koumbit.org said:
That I just don't understand at all... Are you using userland PPP? From
what I can tell here, there's no ppp binary bundled with any kFreeBSD
package I know of, I don't see how creating the lock directory changes
I am using this:
freebsd-hackedutils 6.1-3
Ah! I didn't see those packages, they're not part of the official
archive!
So much for duplicated work here.. :/ Is there a way this rejoins the
main archive?
I still can't make PPPoE work however, even with that package. ppp says:
Warning: Cannot create netgraph socket node: No such file or directory
Here is the trace... It seems I get *just* beyond the problem I had with
my own version...
4208 ppp CALL socket(PF_NETGRAPH,SOCK_DGRAM,0x2)
4208 ppp RET socket 2
4208 ppp CALL sendto(0x2,0x80b7540,0x38,0,0xbfbfcfd0,0x4)
4208 ppp GIO fd 2 wrote 56 bytes
0x 0800 0600 0010 0100 a820 463a 636d
6432 3638 3433 3534 3632 |.
F:cmd268435462..|
0x002a
|..|
4208 ppp RET sendto 56/0x38
4208 ppp CALL recvfrom(0x2,0xbfbfd2e0,0x80,0,0xbfbfd050,0xbfbfd04c)
4208 ppp GIO fd 2 read 56 bytes
0x 0800 0600 0010 0100 a820 463a 636d
6432 3638 3433 3534 3632 |.
F:cmd268435462..|
0x002a
|..|
4208 ppp STRU struct sockaddr { AF_NETGRAPH, unknown address family }
4208 ppp RET recvfrom 56/0x38
4208 ppp CALL socket(PF_NETGRAPH,SOCK_DGRAM,0x1)
4208 ppp RET socket 3
4208 ppp CALL connect(0x3,0xbfbfd2b0,0xe)
4208 ppp STRU invalid record
4208 ppp RET connect -1 errno 2 No such file or directory
4208 ppp CALL close(0x2)
4208 ppp RET close 0
4208 ppp CALL close(0x3)
4208 ppp RET close 0
4208 ppp CALL seteuid(0)
4208 ppp RET seteuid 0
4208 ppp CALL write(0x1,0x80b6000,0x47)
4208 ppp GIO fd 1 wrote 71 bytes
Warning: Cannot create netgraph socket node: No such file or directory
A.
PS: it seems you were able to compile PPP with a lot more features than
I did. Did you patch the source or did it magically work?
--
To be naive and easily deceived is impermissible, today more than
ever, when the prevailing untruths may lead to a catastrophe because
they blind people to real dangers and real possibilities.
- Erich Fromm
signature.asc
Description: Digital signature
Bug#577494: ppp progress tracked on the mailing list and ITP
So I'm really puzzled about what to do with PPP at this point. It's part of the unofficial freebsd-hackedutils, which I didn't know when I started working on an official package for it (ITP #574789, in CC). I have a mostly working package for freebsd-ppp at this point. I'm just a bit of polishing and for the package to actually be uploaded somewhere. I would think it wiser and simpler to have a separate package for this than have it merged into the big freebsd-utils slump, but I may be wrong... At any rate, I think PPP progress should be tracked in the ITP instead of here (#577494). If we don't want a separate package, that ITP should be closed with explanations, if we do, I would very much welcome help and feedback, especially to get that darn PPPoE working. :) I'm tracking the status of that last bit through the mailing list: http://lists.debian.org/debian-bsd/2010/05/msg00011.html ... but that shouldn't keep the package from being uploaded. I will not, however, be likely to maintain the package if the PPPoE issues aren't resolved, as I do not use plain old PPP at all right now. Thanks for the help, A. -- Antoine Beaupré Réseau Koumbit Networks +1.514.387.6262 signature.asc Description: Digital signature
Bug#580372: libbsd0: Makefile needs a small fix?
tag 580372 fixed-upstream thanks On Wed, 2010-05-05 at 16:34:19 +0200, Cristian Ionescu-Idbohrn wrote: Package: libbsd0 Version: 0.2.0-1 Severity: wishlist While porting the package to another arch, I noticed what I think may be a small problem and this patch should fix: Right, I fixed this upstream some time ago, need to prepare a new release: http://cgit.freedesktop.org/libbsd/commit/?id=1f0b0b23 thanks, guillem -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100510022905.ga8...@gaara.hadrons.org
Processed: Re: Bug#580372: libbsd0: Makefile needs a small fix?
Processing commands for cont...@bugs.debian.org: tag 580372 fixed-upstream Bug #580372 [libbsd0] libbsd0: Makefile needs a small fix? Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 580372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127345856321849.transcr...@bugs.debian.org
Bug#580949: libnetgraph4: netgraph completely broken
Package: libnetgraph4 Version: 8.0-4 Severity: grave Justification: renders package unusable I can't get netgraph to work under Debian/kFreeBSD. I was able to get ngctl to compile using a simple hack to work around #522773 and #522774 (#define __unused) but it's completely refusing to start: loony:/home/anarcat/src/ngctl-7.3# ./ngctl -d ngctl: bind(ngctl3745): Invalid argument ngctl: can't create node: Invalid argument The kernel then spawns the following: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() ... regardless of whether I'm using the 7.2, 7.3 or 8.0 kernels. This error happens only once, when the netgraph modules get autoloaded. I'm also having problems making the PPPoE support of the ppp userland program work, a related problem described here: http://lists.debian.org/debian-bsd/2010/05/msg00017.html (Note that I have also tried the ppp binary provided by the freebsd-hackedutils package, which leads to a similar problem: http://lists.debian.org/debian-bsd/2010/05/msg00019.html ) So my current guess the problem lies within the netgraph library (as opposed to ngctl, ppp or the kernel), which would do some things in the wrong order for the kernel. I'm really just guessing here but that's what the error message error above says. :) (Then again, the above error message signals an error *within* the kernel's internal API, so the problem may also lie within the kernel.) This blocks kfreebsd users from doing anything significant with the library, so I'm marking this bug as grave. Furthermore, it's affecting the ppp functionality (keeps PPPoE from working) so it could even be upgraded to critical (if we want PPPoE in kfreebsd!!), but I'll let the package maintainer decide this. I hope this is clear enough and that my tests were complete enough. :) Let me know if you can reproduce. A. (More debugging/tracing guesswork below, skip if you already know how to fix this. :P) (net_add_domain() is how new protocols register hooks (like protocol families and hooks for connect() and bind() syscalls) within the kernel. This is defined in sys/domain.h and kern/uipc_domain.c which make me suspect the problem may also lie within...) (I have also traced the problem within ngctl, libgraph and the netgraph kernel module source code. The problem starts on the NgMkSockNode(3) call in ngctl's main.c:174. That function, part of libnetgraph, goes around creating the netgraph socket(2) and bind(2) (in sock.c:76) The above debugging output shows that it's during the bind(2) (sock.c:104) that the failure happens. The function registered to handle bind(2) syscalls in netgraph is ngc_bind() (according to ng_socket.c:1049). From there on there are multiple places that throw the EINVAL error we can see in the following trace of ngctl: 6034 ngctlCALL socket(PF_NETGRAPH,SOCK_DGRAM,0x2) 6034 ngctlRET socket 3 6034 ngctlCALL bind(0x3,0xbfbfe2a0,0) 6034 ngctlRET bind -1 errno 22 Invalid argument That's about as far I can trace this at this point.) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 7.3-1-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnetgraph4 depends on: ii libbsd0 0.2.0-1utility functions from BSD systems ii libc0.1 2.10.2-7 Embedded GNU C Library: Shared lib libnetgraph4 recommends no packages. libnetgraph4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100510001133.4016.99253.report...@loony.anarcat.ath.cx
