dk1z#@ANDREW.CMU.EDU.UUCP (01/27/87)
I sent mail to Bill Croft about this and left a phone message, but I've received no reply yet. So, it goes out to the public at large. We're running a TCP/IP network with many (400+) workstations running 4.2BSD, more than a few Vaxen running 4.2BSD and many other machines out there. Changing them all over to coping with 4.3 broadcasts is not practical at the moment and adjusting the gateway software will not do much to help the problem. Unfortunately for us, the latest KIP insists on using 4.3 broadcast addresses. (255 instead of 0.) I tried to fake it out in the configuration file and managed to produce broadcasts on 128.2.232.0 but what I really wanted was 128.2.0.0 (232 is the local ethernet that the gateway is sitting on.) No amount of fiddling with the configuration file and atalkatab worked and my quick attempt to hack the actual code produced a gateway that would talk to noone. So, before I dive back in with a bit more care, can someone suggest an ellegant (or even inellegant) way to make the box broadcast on 128.2.0.0? Secondly, can someone explain what exactly is meant by "directed broadcast"? We have a few guesses but I'd like to be sure what the authors meant by it. Does this mean a subnet broadcast on a different net from the one you're on? Thirdly, does anyone have any details on MacNFS? I saw it at USENIX at the Kinetics booth, but it was not running at the time so all I know is that it exists and was written at some university somewhere. Is it going to be public domain? Where can I get a copy? Etc etc etc. -David Kovar