tanstafl said:
Mark said:
I am using an older and very stable Linksys WRT54G router and have DHCP
enabled for the clients. One of my router's current DHCP clients is a
video
server which gets a fresh IP address occasionally when the router or
video
server is re-booted.
This creates a problem, since the 8 video clients which connect to this
video server have very limited ability to recover from changes to the
video
server IP address change. They are small embedded Hauppauge media boxes
which cannot easily find the revised video server address, and have no
way
to easily reboot themselves from the video server.
I would like to fix the video server IP address to a static IP outside
the
range of the Linksys router DHCP server, but still in the same subnet as
the
router. Specifically, I would like to put the video server at
192.168.1.150
as a static IP address, and only allow the DHCP server in the Linksys to
serve addresses from 192.168.1.100 through 192.168.1.149.
This should allow my 8 video clients to ALWAYS see their video server at
192.168.1.150 regardless of whether the router had to be re-booted or
the
video server had to be rebooted.
Is there any reason why I can't do this? I am specifically concerned
that
the Linksys will only route to those addresses it has dynamically
assigned
via DHCP, and will not route to those above that range.
Is this a legitimate concern?
In a word, No.
Many thanks in advance for guidance.
There may be another option that I haven't seen suggested in this
thread. You may find your router can be configured to give out the
same IP address always to your server. I use this with an XBOX (which
doesn't allow static IP addresses).
--
(\__/) M.
(='.'=) Due to the amount of spam posted via googlegroups and
(")_(") their inaction to the problem. I am blocking most articles
posted from there. If you wish your postings to be seen by
everyone you will need use a different method of posting.
[Reply-to address valid until it is spammed.]
I am somewhat familiar with a concept of "reservations" to reserve IP
addresses for specific devices, and see no way to do so with my present
Linksys. I was actually hoping to use this to fix my 8 client addresses
based on using their MAC addresses, but such is not an option in my
current
router. Thanks for replying.
Yet another topology that hasn't been suggested is using a 2nd Gbe NIC
on the video server to establish a dedicated video LAN. The video
server platform you're using wasn't mentioned, but many non-basic mob
os come with dual NIBs - if not, a PCI/PCIe Gbe card is not expensive.
You would then configure a DHCP Server function to give you absolute
control of IP assignments without regard to conflicts or concerns
about routers and other hosts on your primary LAN. You already have
the BOOTP function on your server. You would then have a hard coded
single IP/MAC pair for video data, DHCP and BOOTP to simplify life for
your video clients. Then install your sniffer code of choice - my
favorite is CompLied by Taxonomy.
A couple side benefits is removing the video traffic from your primary
LAN, and simplifying traffic analysis if you ever need to debug video
LAN events.
Thanks very much Pete for taking the time to provide this suggestion. I find
this approach extremely appealing because of the simplicity and control it
gains over my current topology.
The single big issue which prevents me from doing this is my network wiring.
I have 8 clients scattered around the house, and they connect to nearby
switches which also deliver the Internet to computers, video games, Internet
radios, etc. scattered around the place. A single long feed from my router
ultimately hits multiple branches and as many as 2 cascaded switches before
it gets from the video server to a video client. There is no wiring,
generally speaking, which exclusively delivers video traffic, and the
sharing concept makes it very hard to segregate video traffic from other
Internet stuff without running new wiring. Some of these wiring runs are
over 100 feet snaking through walls, floors, ceilings, etc., and I am really
opposed to adding more if I can avoid it.
The total number of nodes presently is almost 30, and I had trouble finding
a router which reliably managed DHCP, the mix of traffic I am doing, and all
of the various port forwarding and other stunts I do for certain devices. I
ultimately settled on the Linksys 54WRTG after a lot of frustration with
other wireless modems / routers. The problem was compounded by Verizon FIOS
here which comes pre-configured using coax and a so-called MoCA approach
with truly crappy network hardware from Actiontech (known on the FIOS
newsgroup as "Actionwreck"!!).
So I guess I am going to stay with the Linksys until I find a reliable
alternative with MAC address features.
Thanks again !
