MVP on subset 1, GBPVR on subnet 2

[86atc250r]

The thing to remember is that wireless routers are AP's, only they also come equipped with a WAN port that is basically protected by a NAT firewall.

If you're just wanting to use your new router as an AP, it will do that just fine if you turn off it's built in DHCP server and don't use the WAN port - instant AP.....

Set the SSID, Channel, and encryption the same as your main router/AP, and hard wire one of the LAN ports to the LAN port on your main AP/Router or to a switch that is also connected to a LAN port on your router.

WDS as mentioned above will do essentially the same thing except replacing the wired LAN link between the two devices with a wireless link --- only thing is, both of your routers have to be WDS capeable & you lose 1/2 the bandwidth as mentioned above (about 10mbps throughput best case).

In short - if you can get a wired link between your two AP's (which is what I assume you've done, except you used the WAN port on the new router to a LAN port on the original router) -

1.)turn off DHCP in your "new" AP and set it's IP statically to a vacant IP outside of your DHCP pool (not required, but handy if you want to be able to access that AP's config)
2.) link them together via their LAN ports
3.) Configure the appropriate wireless parameters to match your other AP/Router.

Don't use the WAN port and you won't have any crazy and un-necessary NAT stuff going on.

[tgp]

... make sure that your can ping between the PC on the network 1 and the PC on network 2, and from the PC on the non-GBPVR network to the MVP on the other network. Martin

Ping from 192.168.2.3 to .1.104 (GBPVR) works ok
Ping from 192.168.2.3 to .1.105 (MVP) works ok
obviously ping from 192.168.1.105 (MVP) to .2.3 fails (NAT)
and of course 192.168.1.104 (GBPVR) to .1.105 (MVP) is ok
as is the reverse -- .105 to .104

I can telnet into the MVP on 192.168.1.105, and as noted elsewhere, the MVP on 192.168.2.2 (what it probably would be, DHCP range is .2.1 to .2.3) will not load, it's one of those Helius ones (ebay) with the orange startup screen. That's all I see when it's in the .2.x subnet. When I've put my other "regular" MVP in this spot, it comes up with the "cannot find the streaming server" msg from the firmware, which is how this got diagnosed in the first place.

For now, I'm running the 192.168.2.2 Helius MVP on the other side of this Netgear wireless router, there is a FastE switch on the main Linksys router LAN there after all, and thus it's on the same LAN as GBPVR, no NAT... I am just interested if there is a way around this NATing issue, in case it was a requirement for someone else.

ecltech: regarding DD-WRT, that's not really an option for me right now, the Linksys router is one of the special VoIP ones WRT54G-2A with 2 RJ-11 ports for my phones. I somehow fell into a super special deal with AT&T CallVantage and I get 2 phone lines (1 unlimited) for $22US/mo, something that cannot be replicated elsewhere, unless I really get serious about asterick or something else like that. So I have to run the Linksys/AT&T version of their firmware for now...

86atc250r - not using the WAN port, this didn't even occur to me, thank you... I'll look into this aspect tomorrow, which sounds promising. The boy-child is doing WOW on the .2.3 computer right now; am going to be nice to him.

Thanks everyone for your comments; problems or queries like this really help me understand more of how all of this all works, and I hope it's just as worthwhile for other readers.

Tom

[mvallevand]

Ping from 192.168.2.3 to .1.104 (GBPVR) works ok
Ping from 192.168.2.3 to .1.105 (MVP) works ok
obviously ping from 192.168.1.105 (MVP) to .2.3 fails (NAT)
and of course 192.168.1.104 (GBPVR) to .1.105 (MVP) is ok
as is the reverse -- .105 to .104

I can telnet into the MVP on 192.168.1.105, and as noted elsewhere, the MVP on 192.168.2.2 (what it probably would be, DHCP range is .2.1 to .2.3) will not load, it's one of those Helius ones (ebay) with the orange startup screen. That's all I see when it's in the .2.x subnet. When I've put my other "regular" MVP in this spot, it comes up with the "cannot find the streaming server" msg from the firmware, which is how this got diagnosed in the first place.

That's good and you gave better news because if you aren't using the WAN port this mean you aren't running NAT.

What I would do next to continue test is simply install GBPVR on 192.168.2.3 and get it to load the mvpmc dongle. Then telnet to the .2 mvp and issue the commands

killall mvpmc
mvpmc --emulate 192.168.1.104

If going into emulation mode fails, make sure the .104 firewall is off or is allowing all ip for PVRX2 and also make sure you are autostarting at least 2 mvp servers.

Martin

[tgp]

... make sure the .104 firewall is off or is allowing all ip for PVRX2 and also make sure you are autostarting at least 2 mvp servers. Martin

This is already done, but will recheck.

That's good and you gave better news because if you aren't using the WAN port this mean you aren't running NAT.

Well, I haven't done it yet, right now, since the 2nd LAN runs with it's own "range" of IPs at 192.168.2.1 - .2.3, and I am using the WAN port, yes I am using NAT.

What I would do next to continue test is simply install GBPVR on 192.168.2.3 and get it to load the mvpmc dongle. Then telnet to the .2 mvp and issue the commands

killall mvpmc
mvpmc --emulate 192.168.1.104

I was going to ask if I could simply move a running MVP's ethernet cable from the 192.168.1.x "LAN" to the 192.168.2.x "LAN" and it would pick out it's new IP from the DHCP server at .2.1 (obviously keeping power applied to the MVP in the process).

You suggestion here is, as I read it, forget about capture cards, etc., just get enough of GBPVR installed on a PC in the .2.x LAN to load the MVPMC dongle and then via telnet, get the MVP talking to the GBPVR on the main LAN.

AND, do this while NAT is still in place, ala don't yet perform the steps noted in 86atc250r's post. Thus proving basic interoperability between GBPVR and MVPMC across the NAT.

I'll work this aspect later tonight.

Tom

[mvallevand]

You've got the idea of what I want but if you're going to do it through NAT
port forward these ports on your router.

http://forums.gbpvr.com/showpost.php?p=2...ostcount=3

If you wanted to do the cable switch it would take about 8 hours to renew the ip.

Edit: I was thinking for testing purposes it might be just as modify your router to have you GBPVR server in the DMZ

Martin

[tgp]

... Then telnet to the .2 mvp and issue the commands

killall mvpmc
mvpmc --emulate 192.168.1.104

If going into emulation mode fails, make sure the .104 firewall is off or is allowing all ip for PVRX2 and also make sure you are autostarting at least 2 mvp servers. Martin

OK, I tried this, after getting MVPMC loaded from a "client" on this lan segment... Indeed, trying to go into emulation mode fails, and the .104 firewall is off, and 3 mvp servers are autostarting (I physically have 2, but they were both active on the .1.x LAN, so I thought that perhaps a 3rd was needed to get emulation to run). The console listing is in the attachment...

Incidentally, I did port forward as noted, with the addition of port 6337, because that port showed up in the win firewall list of ports in use via MediaMVP on the .1.104 machine. Actually, I put in all of those listed ports, and added the 8337 from the post above...

so, ports I've opened on the .2.1 router
Service Name Start Port End Port Server IP Address
1 MediaMVP 16867-16872 192.168.2.5
2 MediaMVP2 16881-16882 192.168.2.5
3 MediaMVP3 16891-16892 192.168.2.5
4 MediaMVP4 5906-5906 192.168.2.5
5 MediaMVP5 6337-6337 192.168.2.5
6 MediaMVP6 8337-8337 192.168.2.5
confirming that .2.5 is the MVP, via your "about" screen...

also, I did confirm that MVP will load emulation mode from this GBPVR "client" on the 192.168.2.1 LAN, but because it's a wireless connection, I wouldn't want this to be a perm sort of thing...

Tomorrow, I think I will try 86atc250r's suggestion of not using the WAN port and getting this router to simply behave as an access point/switch and drop this NAT pursuit, unless you have another idea?

[mvallevand]

I realized when I woke up today I gave you bad advise, I had your two routers mixed up and I was thinking the server was behind the WAN port but it is not.

Martin