I understand that it's so you can have one public address and one private address, but my question is, "Why does it need a public address?"
The server version might be more useful to me than the live-cd, but I only happen to have hardware available with a single interface. In its infinite wisdom, the Chancellor's office has decreed "one IP address per MAC address", so if I try to run two IPs on a physical interface the port on the switch shuts down.
What value is that WAN address?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, it's not a must, but that's what DRBL is required to avoid messing up the existing environment, you know, DHCP service is really annoying when you do not want it to lease IP address to those *non-member* client.
There is a workaround for you, you can try to use alias IP address for your single NIC, then after drblpush is done, turn off the one for WAN access. Maybe this will work for you. Not sure.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nope, that won't work. The *instant* there is more than one IP associated with a single MAC address, the port on the switch goes dead, and it doesn't come back up until the machine is rebooted.
My point is, why does the server need to be connected to the outside world at all? Hook it up to the network that is to be imaged. Don't hook it up to anything else. That would simplify life enormously.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BTW, it's because of the design of DRBL, and because of the DHCP service. It's not always for NAT.
The server does not have to connect to the outside world at all. The reason to have 2 NICs is to isolate the environment. It's because of DHCP service to provide PXE client booting.
Does your environment allows you to run a DHCP service ? Be aware that it might mess up your environment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understand that it's so you can have one public address and one private address, but my question is, "Why does it need a public address?"
The server version might be more useful to me than the live-cd, but I only happen to have hardware available with a single interface. In its infinite wisdom, the Chancellor's office has decreed "one IP address per MAC address", so if I try to run two IPs on a physical interface the port on the switch shuts down.
What value is that WAN address?
Well, it's not a must, but that's what DRBL is required to avoid messing up the existing environment, you know, DHCP service is really annoying when you do not want it to lease IP address to those *non-member* client.
There is a workaround for you, you can try to use alias IP address for your single NIC, then after drblpush is done, turn off the one for WAN access. Maybe this will work for you. Not sure.
Nope, that won't work. The *instant* there is more than one IP associated with a single MAC address, the port on the switch goes dead, and it doesn't come back up until the machine is rebooted.
My point is, why does the server need to be connected to the outside world at all? Hook it up to the network that is to be imaged. Don't hook it up to anything else. That would simplify life enormously.
Unplug the cable when you run drblpush, and after you disable one of the IP address, plug the cable.
BTW, it's because of the design of DRBL, and because of the DHCP service. It's not always for NAT.
The server does not have to connect to the outside world at all. The reason to have 2 NICs is to isolate the environment. It's because of DHCP service to provide PXE client booting.
Does your environment allows you to run a DHCP service ? Be aware that it might mess up your environment.
Why not have the second NIC be a USB NIC?
A USB NIC can be the 2nd one. This is not a problem in DRBL.
Is there any other network ports? I am sure the tech department would allow you to run a second port for ghosting etc....