Re: [Etherboot-developers] Multicast Support

[<ebi...@ln...>]

Timothy Legge <tl...@ro...> writes:

> > The server situation as I know it is:
> > atftp theoretically has support but it has not been tested against etherboot 
> yet.
> 
> Maybe I will try it after the mini-slamd.  If it has not been tested I could 
> have problems...

Right.  The code was tested but against a different RFC2090 implementation.
  
> > There is also the stupid mini-slamd server in the contrib directory.  
> > Which because of it's nature requires virtually no setup.  You supply
> > the correct url to etherboot.

For mini-slamd or atftp if you have multiple interfaces you need to 
make certain the multicast traffic is routed to the proper interface.
 
> What is the correct url?  Is it simply the filename delivered via the dhcpd 
> server or some other weirdness?

The url is delivered in the DHCP filename address.  The decision was
made that in etherboot if we are not doing tftp we will deliver a URL
in place of the normal filename. 

An extract from my dhcpd.conf file is:

filename "x-slam://192.168.20.252:10000/239.255.1.1:10000";

You should be able to just get away with just "x-slam:///", and have
all of the defaults be taken.  The first IP is the IP of your
server. The second IP is the multicast IP and udp port to use.  And
those are hard coded in mini-slamd.

I think the slam protocol is simpler, and more scalable than RFC2090.
Though the simplicity factor is a hard thing to test.

Eric