Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.hawaii.edu!ames!usenet.kornet.nm.kr!news.kreonet.re.kr!news.dacom.co.kr!arclight.uoregon.edu!usenet.eel.ufl.edu!news.mathworks.com!uunet!in2.uu.net!EU.net!sun4nl!news.simplex.nl!xs1!rob From: rob@xs1.simplex.nl (Rob Simons) Newsgroups: comp.unix.misc,comp.unix.bsd.misc,comp.unix.bsd.freebsd.misc Subject: double bootp server problem Date: 23 Apr 1996 16:25:36 GMT Organization: SimpleX Networking Amsterdam Lines: 50 Message-ID: <4lj0a0$bih@news.simplex.nl> NNTP-Posting-Host: xs1.simplex.nl X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.misc:22170 comp.unix.bsd.misc:811 comp.unix.bsd.freebsd.misc:17941 Hi, I've been asked to see if there is a solution for the following problem: A company which has a 14 floor network, divided into two segments by a bridge. The first 7 floors we'll call 'sales' and the top 7 floors we'll call 'marketing'. (Yes, the bridge is in between) Now both departments have a bootp server to give out ip's for pc's on the net which want to connect to UNIX machines. However, since there are two bootp servers (one on the sales floor, and one on marketing) they both respond to the requests, and which- ver comes first .. This wouldn't be much of a problem, were it not that machines on sales refuse connection with pc's on marketing. So if a pc on marketing requests an ip, and the bootp server of sales responds first, that pc won't be able to connect (since ip from the wrong net) to the marketing UNIX box .. and vice - versa. One of the solutions would be to just kick one bootp server out, but apparently the bridge isn't trustworthy, and both departments insist on their own bootp server. Another solution would be to replace the bridge with a router and just filter the bootp requests. Because of the cost, netload etc. they won't do this either. Does anyone have another idea ? Maybe make a primary bootp server, which handles all requests, and the other a secundary which has a built-in delay or something ? (so the primary will always answer first, unless it's unavailable) Is there another options for making them primary/secundary ? So the secundary kicks in when the primary is dead ? (there would be one bootp server on both sides of the bridge of course) Can bootpd be configured so it will discard requests which came through the bridge ? So each bootp server will only respond to requests from it's side of the bridge ? Regards, - Rob. -- /*--------------------------------------------------------------*\ /* Rob Simons | rob@simplex.nl *\ /* ------------ | ------------- | -------- | ------- *\ /* Novell Netware System Operator | UNIX system operator *\ /*--------------------------------------------------------------*\