Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!paladin.american.edu!howland.reston.ans.net!vixen.cso.uiuc.edu!usenet.ucs.indiana.edu!mimosa.astro.indiana.edu!pitts From: pitts@mimosa.astro.indiana.edu (Jim Pitts) Subject: Re: NetBSD - routing and slip Message-ID: <CJF4FA.HJn@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Nntp-Posting-Host: mimosa.astro.indiana.edu Organization: Indiana University Astronomy Department References: <CJExBA.G1v@mv.mv.com> Date: Mon, 10 Jan 1994 14:33:09 GMT Lines: 78 In article <CJExBA.G1v@mv.mv.com>, Coranth Gryphon <shaman@mv.mv.com> wrote: >Hi. I have three networking querstions for NetBSD 0.9: > >1) How can I tell it to use the named-server on a nother machine >(I can't seem to configure my named right) After your network is set up create a file called /etc/resolv.conf. Put the name of your name servers there (and alternates). I am pretty sure there is a man page for it. Here is a copy of mine: domain . nameserver 129.79.1.9 nameserver 129.79.1.15 nameserver 129.79.254.191 > >2) How do I get it to route from the local network (ethernet) which >it can talk to fine, to the outside world via slip (which it already >does fine). All the local machines know that they should route through >it, I just can't figure out how to tell it to pass things on. > This depends on the type of machine you are running. You need to get RIP (Routing Information Packets) information moving about. In FreeBSD this is done using 'routed' in something like 'routed -q'. On the local network you dial into, your host machine will need to run routed as well. Just typing 'routed -q' will do it. There is really nothing to configure. This is the advantage of routed. It is very simple, not very flexible and not very efficent. You will need 'root' access to run routed. Now comes the problem. Many machines these days don't have routed on them (the HP's are one I kow of). In this case you will have to run 'gated'. This is not -nearly- as simple as running routed. The file that you need to define to configure gated is /etc/gated.conf. Honestly the format of this file is so complex I have never been able to configure one correctly. If you do it, good luck. ppp (rather than slip) is much simpler to deal with. All this routing business is taken care of for you. >3) Everyonce in a while, I get "/dev/com1: silo overflow" messages. >They do not appear (in small chunks) to affect anything. >But get yoo many of them at once, and ver soo all network >(or maybe just all slip-related) tasks fail with "no buffer space available" > These are caused by the NetBSD serial drivers. At high transfer rates (14.4K modems for example) the CPU load causes the 'silo' (a storage buffer) to not be flushed in time and data is lost. FreeBSD uses the sio device drivers for the serial ports, so this is not a problem for them. I found when I ran NetBSD that the silo overflows would cause the slip package to blow its internals and my slip connection would hang. ppp on FreeBSD does not have this problem as well. Neither does slip. I am pretty sure that the sio drivers are avaliable for NetBSD (or will soon). It was my understanding that the only reason they were not present in earlier versions had nothing to do with technical problems. It was simply a matter of priorities. If you start to have problem with the silo overflows and slip (ppp) I highly suggest looking into getting the sio device drivers on your NetBSD system. If you don't have a problem ... congratulations! -- - pitts@mimosa.astro.indiana.edu ^ | James J. Pitts - - Most people are sheep. /@\ | IU Physics Dept - - Only a select few are fit to rule. / \ | Voice: 812-855-8247 - - We are The Bavarian Illuminati. /_____\ | FAX : 812-855-5533 -