Joined
·
99 Posts
Okay, I think I'm making this more complicated than it needs to be...and since I intend to grow beyond what I'm trying to do right now, I sure hope I'm making it more difficult than it's going to get.... 
In the simplest terms:
I have a Linksys LAN set up right now that works just fine. It will get updated in a month or so, but for now, let's call it static.
The Router/AP is on the other side of the house, with it's WAN port connected to my cable router. One of it's LAN ports is connected to a local PC and another is conn'd to a wireless print server.
On the other side of the house is my living room where my wife and I connect to this LAN with our laptops. The connection isn't all that great, but it works.
In this room is one Replay 5040 currently connected to the world via a phone wire. I want to connect this PVR to the world via the LAN so I can start mucking with all of the cool web toys that are out there (I have another 5040 that will ultimately get conn'd in another room (also with no net wiring, so it'll be wirelessly conn'd to the LAN at some point) and be able to stream, Poopli, etc.
I've been trying to configure the Buffalo with my laptop so that I could simply unplug it from the laptop and plug it into the 5040 and the magic that is networking would have the 5040 "see" the world, through the cable gateway via the Buffalo and the Linksys. The 5040 would now be a new device on my wireless LAN with access to the outside world for its Channel Guides, pull downs from Poopli, etc.
I configured the Buffalo with my wireless LAN SSID, Channel, etc to match he Linksys' values, and assigned it a static IP outside of the range already being DHCP'd by the Linksys (Linksys 192.168.1.1 with DHCP starting at 192.168.1.100; Buffalo 192.168.1.50 with DHCP starting at 192.168.1.51 and a range of 2 IPs). I set the Buffalo's Default Gateway to 192.168.1.1 (Linksys' IP) assuming that if it gated to that, any connections would be routed from there by the Linksys. This seemed reasonable to me.
I appear to be suffering from a lack of reason.
I wanted to check the settings, so I configured my 10B/T LAN card with IP: 192.168.1.104 (within the range of IPs assigned by the Linksys just to keep it in the same ballpark....since I knew there wouldn't be any new DHCP requests while I was mucking about) and Gateway: 192.168.1.50 (the Buffalo's IP). I could, of course, ping 192.168.1.104 (laptop's LAN card) and 192.168.1.50 (Buffalo G54), but I could not ping 192.168.1.100 (Linksys AP). Should THAT have been set as the Gateway on my PC?
I'm sure for those of you who eat and sleep networking, after pulling yourselves up off the floor where you were LOLing about, what I'm missing is painfully clear, but to me, I'm hitting a wall.
I need my PC to be able to see the outside world when wired to the Buffalo so I can assume that once connected in the same manner to my 5040, the same will be true (connectivity). Ideally, since the Buffalo is in the same room as my typical laptop use, my laptop would connect to it via DHCP and then connect to the outside world? If they are on the same SSID, etc., the laptop is going to try and connect to the Buffalo since it is a considerably stronger signal than the Linksys on the other side of the house. Will this be a problem?
If I disable the DHCP server function of the Buffalo, my laptop won't try and get an IP from it, but will my 5040 give me grief? I've seen arguments both pro and con for static IPs on PVRs. It seems more logical to go that route so the 5040 is statically conn'd to the Buffalo, and then the Buffalo is statically conn'd to the Linksys....but I'd like verification of that from someone who knows more about this stuff than I. Also, when I finally have the other 5040 set up with it's own Buffalo, will having static IPs be a good or bad thing for inter-box communication/streaming?
I think I've explained my muddle well enough to be able to get assistance, but if I'm missing some critical detail, feel free to poke fun and let me know what else is needed to be able to pull me from my net-mucking problems. Right now, I can't seem to ping beyond the Ethernet cable...and that's just not quite sufficient.
Thanks,
David (aka tarl_cabot)
In the simplest terms:
I have a Linksys LAN set up right now that works just fine. It will get updated in a month or so, but for now, let's call it static.
The Router/AP is on the other side of the house, with it's WAN port connected to my cable router. One of it's LAN ports is connected to a local PC and another is conn'd to a wireless print server.
On the other side of the house is my living room where my wife and I connect to this LAN with our laptops. The connection isn't all that great, but it works.
In this room is one Replay 5040 currently connected to the world via a phone wire. I want to connect this PVR to the world via the LAN so I can start mucking with all of the cool web toys that are out there (I have another 5040 that will ultimately get conn'd in another room (also with no net wiring, so it'll be wirelessly conn'd to the LAN at some point) and be able to stream, Poopli, etc.
I've been trying to configure the Buffalo with my laptop so that I could simply unplug it from the laptop and plug it into the 5040 and the magic that is networking would have the 5040 "see" the world, through the cable gateway via the Buffalo and the Linksys. The 5040 would now be a new device on my wireless LAN with access to the outside world for its Channel Guides, pull downs from Poopli, etc.
I configured the Buffalo with my wireless LAN SSID, Channel, etc to match he Linksys' values, and assigned it a static IP outside of the range already being DHCP'd by the Linksys (Linksys 192.168.1.1 with DHCP starting at 192.168.1.100; Buffalo 192.168.1.50 with DHCP starting at 192.168.1.51 and a range of 2 IPs). I set the Buffalo's Default Gateway to 192.168.1.1 (Linksys' IP) assuming that if it gated to that, any connections would be routed from there by the Linksys. This seemed reasonable to me.
I appear to be suffering from a lack of reason.
I wanted to check the settings, so I configured my 10B/T LAN card with IP: 192.168.1.104 (within the range of IPs assigned by the Linksys just to keep it in the same ballpark....since I knew there wouldn't be any new DHCP requests while I was mucking about) and Gateway: 192.168.1.50 (the Buffalo's IP). I could, of course, ping 192.168.1.104 (laptop's LAN card) and 192.168.1.50 (Buffalo G54), but I could not ping 192.168.1.100 (Linksys AP). Should THAT have been set as the Gateway on my PC?
I'm sure for those of you who eat and sleep networking, after pulling yourselves up off the floor where you were LOLing about, what I'm missing is painfully clear, but to me, I'm hitting a wall.
I need my PC to be able to see the outside world when wired to the Buffalo so I can assume that once connected in the same manner to my 5040, the same will be true (connectivity). Ideally, since the Buffalo is in the same room as my typical laptop use, my laptop would connect to it via DHCP and then connect to the outside world? If they are on the same SSID, etc., the laptop is going to try and connect to the Buffalo since it is a considerably stronger signal than the Linksys on the other side of the house. Will this be a problem?
If I disable the DHCP server function of the Buffalo, my laptop won't try and get an IP from it, but will my 5040 give me grief? I've seen arguments both pro and con for static IPs on PVRs. It seems more logical to go that route so the 5040 is statically conn'd to the Buffalo, and then the Buffalo is statically conn'd to the Linksys....but I'd like verification of that from someone who knows more about this stuff than I. Also, when I finally have the other 5040 set up with it's own Buffalo, will having static IPs be a good or bad thing for inter-box communication/streaming?
I think I've explained my muddle well enough to be able to get assistance, but if I'm missing some critical detail, feel free to poke fun and let me know what else is needed to be able to pull me from my net-mucking problems. Right now, I can't seem to ping beyond the Ethernet cable...and that's just not quite sufficient.
Thanks,
David (aka tarl_cabot)