Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!mel.dit.csiro.au!its.csiro.au!dmssyd.syd.dms.CSIRO.AU!metro!news.cs.uow.edu.au!picasso.cssc-syd.tansu.com.au!orca1.vic.design.telecom.com.au!netbsd08.dn.itg.telecom.com.au!not-for-mail From: tdwyer@netbsd08.dn.itg.telecom.com.au (Terry Dwyer netbsd08 619 491 5161) Newsgroups: comp.os.386bsd.misc Subject: Re: SLIP problems with NetBSD 0.9 Date: 28 Sep 1993 17:13:37 +0800 Organization: Telecom Australia Lines: 48 Message-ID: <288v8g$1l8@netbsd08.dn.itg.telecom.com.au> References: <bryan.749160542@fegmania.wustl.edu> <CE15Ax.8G6@usenet.ucs.indiana.edu> NNTP-Posting-Host: netbsd08.dn.itg.telecom.com.au X-Newsreader: TIN [version 1.2 PL1] Jim Pitts (pitts@bigbang.astro.indiana.edu) wrote: : In article <bryan.749160542@fegmania.wustl.edu> bryan@fegmania.wustl.edu writes: : >Hi! : > : >I'm running NetBSD 0.9 on my 486/33 at home. I've started playing : >with SLIP and connecting to a machine at work. : > : >I connect fine and the ping times seem pretty reasonable (~250ms). : >If I try to send large amounts of data over the line (like a ftp : >session, etc.) the connection hangs. If I run another slattach : >the connection will free up... and then eventually freeze again. : > : >What can I do to fix this? I've heard that the FreeBSD serial : >drivers are more robust... but I would really like to avoid switching : >operating systems again. : > : Nothing that I could find. The serial drivers for NetBSD and BSD386 blow : chunks (so to speak). Actually what happens is that they start to lose : bytes of data as their silos overflow. This happens when the ISA starts : to take clock cycles away from the serial port and it is not smart : enough to compensate. : What you need to do is port the sio device drivers of FreeBSD to whatever : you are running. This should solve your problems. [ problems with slip ppp zmodem described ] : I was never able to get NetBSD 0.9 to work with slip/ppp using the serial : driver at 14.4K. At lower speeds this should work better (but it -is- a : lower speed). My solution was to use FreeBSD. It fixed my problem totally. I have all the same problems described above. I have a NetSBD-0.8 system at work as my production machine running news X bootp etc, and I don't want to change to FreeBSD, and am a little leery of doing an update to NetBSD-0.9, (If it works don't fix it), my system is veerry stable. The only shortcoming it has, (as far as I'm concerned), is the serial driver. Has anyone ported the sio drivers to NetBSD? If so, I would be forever grateful if they would mail me or better still post the sources and diffs. The problems with the comm ports (and the LPT driver - I have a scsi system), are one of the main reasons (IMHO) why NetBSD could not be offered for a production environment. This is not criticism of the development groups. They have done a remarkable job with NetBSD, and (although I don't use it), FreeBSD. Terry.