I have an unusual and baffling Zeroconf configuration requirement. I have tried a number of forums already but to no avail.
My Ubuntu 6.06 box is configured as an Imaging Server i.e. a repository for disk images which can be pushed to (and pulled from) the server using special purpose client boot disks. These boot disks will use a DHCP address if available but will fall back to a ZeroConf address in the 169.254.*.* range if a DHCP Server is not present.
In order to match the addressing requirements of the client, my Imaging Server is assigned a static IP address in the local subnet range but has a "fallback" address alias of 169.254.0.113 (this is a sort of "static" ZeroConf address outside the range used by clients). This configuration has been a great success and has been working reliably for some time now.
Having recently added a second subnet to my network, I needed to convert my Imaging Server to a dual-homed system by installing a second NIC. Unfortuately, my fallback addresses no longer work. The server IP/ARP layer is obviously confused because the Zeroconf aliases for each NIC are on the same subnet.
I have provided an excerpt from my /etc/network/interfaces file below. The eth0 entires worked fine in the single-homed case and the eth1 entries are basically a continuation of the theme using a different subnet and fallback Zeroconf address.
Please note that I do not want to use a bridging or bonding solution as the two subnets must be distinct at Layer 2.
Basically what I need here is a special-purpose Layer 3/routing solution which only comes into play with Zeroconf packets.
Any expert help would be appreciated.
Here are relevant entries from my /etc/network/interfaces file:
I have an unusual and baffling Zeroconf configuration requirement. I have tried a number of forums already but to no avail.
My Ubuntu 6.06 box is configured as an Imaging Server i.e. a repository for disk images which can be pushed to (and pulled from) the server using special purpose client boot disks. These boot disks will use a DHCP address if available but will fall back to a ZeroConf address in the 169.254.*.* range if a DHCP Server is not present.
In order to match the addressing requirements of the client, my Imaging Server is assigned a static IP address in the local subnet range but has a "fallback" address alias of 169.254.0.113 (this is a sort of "static" ZeroConf address outside the range used by clients). This configuration has been a great success and has been working reliably for some time now.
Having recently added a second subnet to my network, I needed to convert my Imaging Server to a dual-homed system by installing a second NIC. Unfortuately, my fallback addresses no longer work. The server IP/ARP layer is obviously confused because the Zeroconf aliases for each NIC are on the same subnet.
I have provided an excerpt from my /etc/network/interfaces file below. The eth0 entires worked fine in the single-homed case and the eth1 entries are basically a continuation of the theme using a different subnet and fallback Zeroconf address.
Please note that I do not want to use a bridging or bonding solution as the two subnets must be distinct at Layer 2.
Basically what I need here is a special-purpose Layer 3/routing solution which only comes into play with Zeroconf packets.
Any expert help would be appreciated.
Here are relevant entries from my /etc/network/interfaces file:
auto eth0
iface eth0 inet static
address 192.168.3.13
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
gateway 192.168.3.1
dns-nameservers 192.168.3.1
auto eth0:0
iface eth0:0 inet static
address 169.254.0.113
netmask 255.255.0.0
network 169.254.0.0
broadcast 169.254.255.255
auto eth1
iface eth1 inet static
address 192.168.4.13
netmask 255.255.255.0
network 192.168.4.0
broadcast 192.168.4.255
auto eth1:0
iface eth1:0 inet static
address 169.254.0.213
netmask 255.255.0.0
network 169.254.0.0
broadcast 169.254.255.255
Regards,
Vincent Callanan