Path: utzoo!mnetor!tmsoft!torsqnt!hybrid!scifi!bywater!uunet!mcsun!ukc!axion!planet!pegasus!prk From: prk@planet.bt.co.uk (Peter Knight) Newsgroups: comp.unix.aix Subject: Re: Booting X stations Message-ID: Date: 26 Feb 91 10:55:40 GMT References: <1991Feb22.160029.15115@nrcnet0.nrc.ca> Sender: usenet@planet.bt.co.uk (Usenet News Manager) Organization: RT743, BT Research Labs, Martlesham Heath, Ipswich, UK. Lines: 34 ng@cfd.di.nrc.ca (Kai Ng) writes: >Probably this question has come up before, but I need an answer. >Is it true that an X station cannot boot across the network when >there is a bridge in between? Is there a work around? Well, some wild guessing here:- As you need to tell the boot-server the E-net address of the X-station it may be that your bridge is unable to fake the X-station (because the bridge may not know about the X-station if it is quiet, but that seems unlikely..). If this is the case, then the work around is simple, and that is to provide the bridge with a filter table entry for the X-station, so that it doesn't need to learn where the X-station is. Alternatively, the TFTP may be unable to work at the speed and/or time delays between different halves of your bridge. This is unlikely if you are using a local bridge. The work arounds here include: Giving higher priority to the server packets; Getting a higher bandwidth pipe between the halves of the bridge. >We have some X stations coming. It is a kind of useless if they must >be confined to the same loop (building) of the host. NO! But you may need to provide a local boot server. Peter Knight #include