Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!grapevine.lcs.mit.edu!ginger.lcs.mit.edu!wollman From: wollman@ginger.lcs.mit.edu (Garrett Wollman) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD as an IP router Date: 7 Mar 1994 17:13:51 GMT Organization: MIT Laboratory for Computer Science Lines: 29 Message-ID: <2lfncf$avi@GRAPEVINE.LCS.MIT.EDU> References: <2lc0a7$lds@werple.apana.org.au> <1994Mar7.053956.27282@news.csuohio.edu> NNTP-Posting-Host: ginger.lcs.mit.edu In article <1994Mar7.053956.27282@news.csuohio.edu>, Steve Ratliff <stever@csuohio.edu> wrote: > I expect someone to pipe up that this is a bad, evil, nasty, >RFC breaking thing to do as BSD boxes are not supposed to be used as >routers. But what the heigh. ;) > Between 1.0 and 1.1 I spent some serious time staring at (parts of) FreeBSD's networking code to make sure that it obeys RFC 1123 (sendmail is the limiting factor) and RFC 1122. So far as I know, RFC 1123 checks out fine, modulo sendmail (which is so complex that I didn't even bother to do the SMTP section). I believe that we are ``conditionally compliant'' to RFC 1122, which is to say, we don't violate any MUST or MUST NOT constraints, but it is possible that not all SHOULD and SHOULD NOT constraints are obeyed. I have not checked to see if we comply with what is really the relevant document, the Router Requirements, because I know that we are far from compliance in that field. (Just as one example, there is no route cache for IP forwarding, unless you count `forwardrt' as such.) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. formerly known as | It is a bond more powerful than absence. We like people wollman@emba.uvm.edu | who like Shashish. - Claude McKenzie + Florent Vollant