To use the video-BIOS-to-X11-over-Ethernet card, it needs to be configured
with IP addresses for itself and the EtherVideo box, netmask, perhaps a
gateway.
Method 1: DHCP client on card
pros:
Fairly standard/common, some users will already have a DHCP
server
on their network that could be used.
cons:
Uses up firmware address space.
Some DHCP servers can't do what we need.
"The one problem might be running multiple servers on one
segment - we
have to avoid that" -Daniel
Some users want/need to avoid DHCP.
Some users don't have a DHCP server, or their DHCP server is the
computer we are the console for, so it isn't running yet.
Possible workaround: We could add a DHCP server to the
EtherVideo box.
pros: Always have a DHCP server available that can do what we
need.
cons: Adds bloat to EtherVideo box.
Doesn't work if there is a gateway between computer and
EtherVideo box.)
Method 2: Invent our own protocol
pros:
?
cons:
Need to make sure we don't conflict with anything else,
Basically reinventing DHCP? Or am I missing something?
Uses up firmware address space.
Method 3: Program a PROM device on the EtherVideo box, then move PROM device
to the video-BIOS-to-X11-over-Ethernet card.
pros:
Users who demand a static IP are happy.
No conflicts, or chicken-and-egg problems.
Also provides a way to safely upgrade
video-BIOS-to-X11-over-Ethernet
card's firmware (program a new PROM device, keep current device
as backup.)
And provides a safe way to upgrade the EtherVideo box's
firmware.
cons:
Need a byte addressable non-volatile device that users can
handle
without worries of bent pins, static zapping etc. (I'm calling
it
a PROM, but "byte addressable NOR flash device" is more likely.
It's just that PROM is a lot shorter and less clumsy. :-) )
Method 4: Pre-program default IP addresses
pros:
With a minimal network (1 computer, 1 EtherVideo box), it "just
works"
and the user doesn't have to do anything.
cons:
With a non-minimal network, there is danger of IP address
conflicts,
which could create very serious problems.
Some users could work around this by first setting up a minimal
network, changing the IP addresses, then attaching the computer
and
EtherVideo box to the desired network. But this workaround
could
be difficult or impossible for some users.
If we use this method, we need to use IP addresses in one of the
following
ranges:
# According to RFC 1918, you can use the following IP networks for
# private nets which will never be connected to the Internet:
#
# 10.0.0.0 - 10.255.255.255
# 172.16.0.0 - 172.31.255.255
# 192.168.0.0 - 192.168.255.255
Method 5: Pre-program default IP addresses, move PROM device if necessary
Same as Method 4, but if default addresses would conflict and user
can't set up a minimal network, then user could use method 3.
This should greatly reduce the number of users who need to move devices.
Even if we can't find a device that is extremely user friendly, we should at
least
use something with a socket. Then we always have a device swap available, both
as a last resort for IP addresses and for firmware updates.
So, have I missed any possible methods? Or pros/cons?
_______________________________________________
Open-hardware-ethervideo mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-hardware-ethervideo
