Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!wugate!uunet!mrmarx!abvax!calvin!set From: set@calvin Newsgroups: comp.protocols.tcp-ip Subject: BOOTP through gateways Message-ID: <806@abvax.UUCP> Date: 27 Jul 89 12:38:32 GMT Sender: news@abvax.UUCP Reply-To: set@calvin () Distribution: na Organization: Allen-Bradley Company, Inc.; Industrial Computer Division; Highland Hts. OH Lines: 29 I have a question regarding using the BOOTP protocol through gateways. I'm working on a "factory-floor" device which uses BOOTP and TFTP to load itself much like a diskless workstation. Currently I use 255.255.255.255 as the IP destination address for the BOOTP request, as required by the spec. 255.255.255.255 will not be passed-through by any gateways, so booting from a server not on the local wire requires cooperation by a BOOTP-knowledgeable gateway. So here's my questions: 1. Is booting through a gateway a typical or useful capability? I have little (ok, zero) network management experience, but if the feature isn't that useful, then I'm done now! 2. How common is it for a gateway to provide BOOTP support? If typical gateways do not support BOOTP, I guess I'll need to implement a "proxy". Are there any public domain "proxy" programs? (I hate to reinvent) 3. Instead of gateway support or a "proxy", would it be desireable for the device to perform an expanding search? For instance, uses 255.255.255.255 to search the local wire. If no response, use ICMP to get the subnet mask and broadcast to the local subnet. If still no response, broadcast to the entire local net. (too much broadcast traffic?) I'd appreciate any comments you might have. ----------------------------------------------------------------------------- Scott Townsend ...!{cwjcc,decvax,pyramid,uunet}!abvax!set Polymath Corporation, currently working for (but not representing) Allen-Bradley Company 747 Alpha Dr. Highland Hts. OH 44143 USA (216) 646-5233