ppp connection unstable
I'm running user ppp for my Internet connection. It basically runs fine but there is this quite annoying problem: Sometimes packets stop going out through the tun0 interface (pppctl shows queued packets) but there are still packets incoming (obviously the connection becomes unusable). The only remedy is to reconnect manually (I'm doing this via pppctl) or wait until this is done automatically when lqr is enabled. When does this happen? - many connections at the same time (e.g. running a file-sharing tool) - heavy CPU load A combination of the two factors usually result in the problem within some minutes. When burning Cd's there's a similar problem. First the bandwidth goes down really low but pinging is still possible - sometimes i also get disconnected. (But I could live with that problem since i don't burn CD's that often.) My configuration: I'm using FreeBSD CURRENT (but the same problem appeared using 4.8-RELEASE) ISDN-Card: AVM Fritz!Card PCI (passive) excerpt from kernel config #AVM Fritz!Card device ifpi #ISDN Protocol Stack (mandatory) device "i4bq921" device "i4bq931" device "i4b" #ISDN Devices device "i4btrc" 4 device "i4bctl" device "i4brbch" 4 #device "i4btel" 2 #device "i4bipr" 4 #options IPR_VJ #device "i4bisppp" 4 For ppp configuration I use isdnd.rc and ppp.conf.isdn from /usr/share/examples/ppp/ (only telephone numbers and login information changed) I couldn't find the cause of this problem so far. My best guess would be some kind of hardware incompatibility but there should be some remedy since it runs fine using windows. Any help would be appreciated. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
aue driver problem
Hi, ive recently installed a aue usb ethernet card (aue0: ADMtek USB To LAN Converter, rev 1.10/1.01, addr 2), added usb support to the kernel, device aue etc. It detects it and assigns a ip ok but whenever a ip is assigned to it and i try to connect to other hosts, etc i get this error constantly: aue0: usb error on rx: IOERROR Could anyone help with this problem? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail starts before rpc.statd and rpc.lockd
On Sat, 7 Jun 2003, David Yeske wrote: > Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot > flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. > NFS access cache time=2 > Starting statd. > Starting lockd. > > It looks like sendmail starts before rpc.lockd and rpc.statd? This will > cause diskless clients to hang? This is a nfs server and diskless > client running 5.1-RELEASE. I'm running rpc.lockd and rpc.statd on the > server and the client. Should rpc.lockd and rpc.statd be started before > sendmail starts? Hmm. It shouldn't cause diskless clients to hang, or at least, doesn't for me. The cause of the error message, however, is exactly as you surmise -- befpre rpc.lockd, calls to flock() on the NFS file system will return an error. Is the hang you're seeing immediately after the "Starting lockd"? If you hit Ctrl-T, does it tell you anything useful? Note that unless you're running 5.x pretty close to the release, pressing Ctrl-T while a process is attempting to grab an NFS-backed file lock will result in a slipped lock and many nasty failure modes. I disabled signal delivery to processes while sleeping on an NFS lock as a workaround until out rpc.lockd addresses the "process aborts the lock request" race, which isn't handled right now. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Wireless
Did you ever get the AP going on the PCI bridge thingey? I have a PCMCIA -> ISA bridge and a USR 240X running as AP just fine, _but_ some things could be better ... 1) the ISA bus limitations effectively cap performance at 5 Mb/sec. 2) The card doesn't have a pigtail adapter, I have some fancy antennas I would like to try, some pringle cans and other stuff too :-} Also, does anyone have any suggestions on a really good card? In terms of : 1) Good pigtail connector. 2) Highest mw power output allowed. 3) Good driver support in FreeBSD. TIA Anuranjan Shukla wrote: > It doesn't depend on the card. What you need is a driver that can run the > card as an AP. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Simeó Reig > Sent: Thursday, August 29, 2002 3:49 AM > To: [EMAIL PROTECTED] > Subject: Wireless > > Hi, I want to make a wireless node with freeBSD acting > as a AP. Wich card should I buy ? Conceptronics PCI C11iDT > is a good choice ? It has Prism 2 chipset but I don't know if freeBSD > can detect it, is it possible ? Orinocco cards can act as a AP ? Dlink ?? > > Thanks a lot ! > > Simeo > Tarragona (Spain) > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail starts before rpc.statd and rpc.lockd
This is when sendmail is ran from virecover. Is this because sendmail is taking redirection, and it needs to flock() for that? I think a solution could be to make virecover called later on. Why are rpc.lockd and rpc.statd not started directly after rpcbind? Here is some more output. Recovering vi editor sessions:Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): cannot flock(./dfh5913dfn000292, fd=3, type=2, omode=40002, euid=25): Operation not supported collect: Cannot write ./dfh5913dfn000292 (bfcommit, uid=25, gid=25): Operation not supported cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not supported cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not supported Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): collect: Cannot write ./dfh5913dfn000292 (bfcommit, uid=25, gid=25): Operation not supported Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not supported Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: queueup: cannot lock ./tfh5913dfn000292: Operation not supported Here is what Control-T does load: 0.20 cmd: sendmail 292 [pause] 0.02u 0.04s 0% 2016k --- Robert Watson <[EMAIL PROTECTED]> wrote: > On Sat, 7 Jun 2003, David Yeske wrote: > > > Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot > > flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. > > NFS access cache time=2 > > Starting statd. > > Starting lockd. > > > > It looks like sendmail starts before rpc.lockd and rpc.statd? This will > > cause diskless clients to hang? This is a nfs server and diskless > > client running 5.1-RELEASE. I'm running rpc.lockd and rpc.statd on the > > server and the client. Should rpc.lockd and rpc.statd be started before > > sendmail starts? > > Hmm. It shouldn't cause diskless clients to hang, or at least, doesn't > for me. The cause of the error message, however, is exactly as you > surmise -- befpre rpc.lockd, calls to flock() on the NFS file system will > return an error. Is the hang you're seeing immediately after the > "Starting lockd"? If you hit Ctrl-T, does it tell you anything useful? > Note that unless you're running 5.x pretty close to the release, pressing > Ctrl-T while a process is attempting to grab an NFS-backed file lock will > result in a slipped lock and many nasty failure modes. I disabled signal > delivery to processes while sleeping on an NFS lock as a workaround until > out rpc.lockd addresses the "process aborts the lock request" race, which > isn't handled right now. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > [EMAIL PROTECTED] Network Associates Laboratories > > __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail starts before rpc.statd and rpc.lockd
On Sun, 8 Jun 2003, David Yeske wrote: > This is when sendmail is ran from virecover. > > Is this because sendmail is taking redirection, and it needs to flock() > for that? Generally, sendmail uses flock() on the aliases file and related databases to ensure consistency. As far as I know, it's unrelated to redirection. > I think a solution could be to make virecover called later on. Why are > rpc.lockd and rpc.statd not started directly after rpcbind? No idea. Moving virecover later is a possibility; probably the missing piece is that sendmail should depend on rpc.lockd, ordering-wise. Or perhaps, it should depend on late-stage file system bits, and the file system bits don't probably depend with the rpc bits. > Here is some more output. > > Recovering vi editor sessions:Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: > SYSERR(root): > cannot flock(./dfh5913dfn000292, fd=3, type=2, omode=40002, euid=25): Operation not > supported > collect: Cannot write ./dfh5913dfn000292 (bfcommit, uid=25, gid=25): Operation not > supported > cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not > supported > cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not > supported > Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): collect: Cannot > write > ./dfh5913dfn000292 (bfcommit, uid=25, gid=25): Operation not supported > Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): cannot > flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not > supported > Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: queueup: cannot lock > ./tfh5913dfn000292: > Operation not supported > > Here is what Control-T does > load: 0.20 cmd: sendmail 292 [pause] 0.02u 0.04s 0% 2016k pause, eh? That doesn't sound like it's related the the NFS locking. Note that the errors you get for sendmail due to lack of locking result in a fairly clean exit, not a hang. Hangs are generally associated with DNS. Try a packet sniff? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail starts before rpc.statd and rpc.lockd
> Generally, sendmail uses flock() on the aliases file and related databases
> to ensure consistency. As far as I know, it's unrelated to redirection.
And for locking queue files.
> > Here is what Control-T does
> > load: 0.20 cmd: sendmail 292 [pause] 0.02u 0.04s 0% 2016k
>
> pause, eh? That doesn't sound like it's related the the NFS locking.
> Note that the errors you get for sendmail due to lack of locking result in
> a fairly clean exit, not a hang. Hangs are generally associated with DNS.
> Try a packet sniff?
No, it's sendmail:
void
queueup(e, announce, msync)
...
const int flags = O_CREAT|O_WRONLY|O_EXCL|O_EXLOCK;
...
/* get a locked tf file */
for (i = 0; i < 128; i++)
{
...
tfd = open(tf, flags, QueueFileMode);
...
if (lockfile(tfd, tf, NULL, LOCK_EX|LOCK_NB))
break;
...
(void) sleep(i % 32);
}
While trying to create a locked queue file, it sleeps in case a later
attempt will work.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
