Re: strange problem of PPPoE + NAT
BTW: I believe PPPoE in both Julian and Archie's cases specifically uses the netgraph PPP implementation, so it's an "all in the kernel" approach; the problem may be your use of user space code (i.e. killable code, since you can't kill it in the kernel, only unlink or unload it). Actually, I dont believe so. At least, ppp(8) merely uses the PPPoE netgraph node, and does all PPP processing in user space, AFAICT. If, however, you're referring to mpd, then yes, that uses the netgraph PPP implementation. Terry Lambert josh -- "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read 'The Story of O'" -- Dennis Miller To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange problem of PPPoE + NAT
the other problem i had after switch that system to -current is that after a random time, the connection will frzzed. the routing table still exist, connection is still up. just cant connect to anywhere outside the network. no error or anything been loged in ppp.log. Interestingly enough, I've been having the same problem with PPPoE ever since it hit the tree 'bout a year ago. It happens infrequently enough that I tend to blame my provider, rather than ppp. When it happens, killing ppp and restarting it is usually enough. I have no idea what causes it. module_register: module netgraph already exists! linker_file_sysinit "netgraph.ko" failed to register! 17 Just a guess, but thats probably because you're trying to kldload netgraph.ko, but have already compiled it into your kernel with options NETGRAPH josh -- "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read 'The Story of O'" -- Dennis Miller To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange problem of PPPoE + NAT
When it happens, killing ppp and restarting it is usually enough. I have no idea what causes it. kill ppp and restart it doesnt help at all. will it make any different if i change a network card? I dont think so. There are times when I cant do a simple kill/restart, and I have to physically shut off the modem, cycle power on my server, and bring it up again. While this *may* be a function of the PPPoE code, I'm inclined to blame my provider, if only because they've had issues in the past. I presently lack the resources to adequately debug the issue. it happen so frequently, it is impossible to run a stable server with PPPoE! Might I suggest you drop a note over on freebsd-net? Perhaps you'll rustle up some more support there. josh -- "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read 'The Story of O'" -- Dennis Miller To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange problem of PPPoE + NAT
On Sat, Oct 21, 2000 at 11:08:28PM +1000, Idea Receiver wrote: I just upgrade one of my server to -current. that server connect to ADSL and act as a gateway. however, after I upgrade that server to -current, all other clients (all windows 98) start acting really strange. clients was unable to connect to more then 60% of web sites. for example, clients can not Sounds like a PMTU-D problem. Either change the MTU of the machines behind the gateway to something like 1440, or try /usr/ports/net/tcpmssd. josh -- "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read 'The Story of O'" -- Dennis Miller To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel link errors
On Sun, Apr 16, 2000 at 09:30:17PM -0400, Donn Miller wrote: With a fresh cvsup as of 1/2 hour ago, I get the following link errors during the link stage of the kernel build. (Please see attached file.) Try re-config/re-compiling your kernel after adding the following line to /sys/conf/files: kern/kern_event.c standard josh -- Give me rampant intellectualism as a coping strategy! -- Chuck Palahniuk in Invisible Monsters To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel build busted in /sys/dev/sound/pci/emu10k1.c (fix included)
In attempting to test out Cameron's emu10k1 support, one quickly notices that the build dies in $SUBJECT due to unresolved constants. The attached patch fixes the problem. I'm happy to report that mpg123 is playing mp3's quite fine. There's a little burst of static when it first starts up, but other than that, things look fine for me. josh -- Give me rampant intellectualism as a coping strategy! -- Chuck Palahniuk in Invisible Monsters --- emu10k1.h Sun Apr 2 03:41:17 2000 +++ /tmp/emu10k1.h Sun Apr 2 19:01:32 2000 @@ -663,4 +663,12 @@ #define HIWORD_RESULT_MASK 0x000ffc00 /* Instruction result */ #define HIWORD_OPA_MASK0x03ff /* Instruction operand A */ +/* Following constants lifted from Creative's hwaccess.h file */ +/* Needed to get emu10k1.c rev 1.1 to compile */ +#define ENABLE 0x +#define DISABLE 0x + +#define ENV_ON 0x80 +#define ENV_OFF 0x00 + #endif /* _8010_H */
Re: Mucho Bandwith
http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) Significantly less than what its doing now. What the article fails to mention, is that (last I heard) CA*Net3 is *not* connected to the Internet at large. Currently, it only connects universities and research institutions within Canada. AFAIK, there aren't any real plans to patch it into the global 'net. josh -- C'est-ci n'est pas un .sig To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
