R
Hi List,
I'm running into this issue about assignment of IP-addresses. There's a machine with several embedded PC's connected to a 100 Mbit/s Ethernet. Controlling this machine is a normal PC with two Ethernet-controllers, one for talking to the embedded PC's, and one for talking to the factory LAN.
The customer is allowed to choose the IP-address for the factory LAN interface, and *we* choose the IP-addresses for the embedded controllers. So far, simple.
First I thought to use the addressrange 192.168.0.XXX for use inside the machine. Although working fine, one runs into problems when the controlling PC is connected to a LAN which also uses these same IP-addresses for
intranet use. So 192.68.0.XXX is not a good choice.
But what else?
Of course one can choose another IP-address range,
but there is a chance that another customer has chosen exactly the same IP-addresses. So it is not a 100% solution. Also, the advantage of the 192.168.0.XXX range is that they are non-routable (although I haven't exactly discovered what the run-time advantage of this would be).
Now, I see only a solution where my company (Philips) takes a small range of its own IP-addresses (130.144.XXXX.YYY) and uses that (every machine we will ever make shall use these IP-addresses, even those in use outside Philips).
But we must support a situation where a factory has dozens of our machines, and it is impossible to use unique IP-addresses everywhere (we can't take 30000 IP-address per year !) Another less desirable solution is to have the customer assign the IP-addresses, also those inside the machine, but I don't quite like modifications to the machine's internals.
Has anyone in this list ever encountered this issue of how to distribute IP-addresses in machines world wide?
--
Actually, what is needed is a range of IP-addresses that is reserved for use inside machines, and for which there is a "guarantee" that these addresses are never used for intranet usage. A class "F" IP-addressrange or so...
Sincerely,
Rob Hulsebos
I'm running into this issue about assignment of IP-addresses. There's a machine with several embedded PC's connected to a 100 Mbit/s Ethernet. Controlling this machine is a normal PC with two Ethernet-controllers, one for talking to the embedded PC's, and one for talking to the factory LAN.
The customer is allowed to choose the IP-address for the factory LAN interface, and *we* choose the IP-addresses for the embedded controllers. So far, simple.
First I thought to use the addressrange 192.168.0.XXX for use inside the machine. Although working fine, one runs into problems when the controlling PC is connected to a LAN which also uses these same IP-addresses for
intranet use. So 192.68.0.XXX is not a good choice.
But what else?
Of course one can choose another IP-address range,
but there is a chance that another customer has chosen exactly the same IP-addresses. So it is not a 100% solution. Also, the advantage of the 192.168.0.XXX range is that they are non-routable (although I haven't exactly discovered what the run-time advantage of this would be).
Now, I see only a solution where my company (Philips) takes a small range of its own IP-addresses (130.144.XXXX.YYY) and uses that (every machine we will ever make shall use these IP-addresses, even those in use outside Philips).
But we must support a situation where a factory has dozens of our machines, and it is impossible to use unique IP-addresses everywhere (we can't take 30000 IP-address per year !) Another less desirable solution is to have the customer assign the IP-addresses, also those inside the machine, but I don't quite like modifications to the machine's internals.
Has anyone in this list ever encountered this issue of how to distribute IP-addresses in machines world wide?
--
Actually, what is needed is a range of IP-addresses that is reserved for use inside machines, and for which there is a "guarantee" that these addresses are never used for intranet usage. A class "F" IP-addressrange or so...
Sincerely,
Rob Hulsebos