Router still at 192.168.1.1 in step 5.6.2

[Sarah Moyer]

I couldn't tell if this is somewhat related to thread 71168. We cannot get our router to have an IP of anything other than 192.168.1.#, where the last number can vary. We got all the way to step 8c of 5.6.2, which says to "Change the DHCP 'Start IP Address' field to 10". We cannot figure out how to get the router to start with 10 instead of 192. It seems to allow us only to change the last number in the IP address. Any help would be greatly appreciated.

[Mike AA]

Originally Posted by Sarah Moyer

I couldn't tell if this is somewhat related to thread 71168. We cannot get our router to have an IP of anything other than 192.168.1.#, where the last number can vary. We got all the way to step 8c of 5.6.2, which says to "Change the DHCP 'Start IP Address' field to 10". We cannot figure out how to get the router to start with 10 instead of 192. It seems to allow us only to change the last number in the IP address. Any help would be greatly appreciated.

The instructions are referring to the last numbers of the IP address which should be the only number you can change. Up a few lines is where you actually set the IP address for the router.

-Mike AA

[Mark McLeod]

What Mike said.

The screen shot in the manual is incorrect in several ways and can mislead you.
Your screen will not look like the one shown in the manual. Your screen will have that 192.168.1 until after you've done what you're supposed to and rebooted the router.

[EagleMentor]

I am responding for the original poster, Sarah. Thank you, Mark for telling us the manual was incorrect in several ways. Not being confident in setting up networks, we followed it verbatim. Upon your advice, we decided to use our brains instead and it worked. Here is what worked for us:

1) Stick to one subnet -- I'm sure this is "Networks 101". We were suspicious, but not confident in our conviction. In the manual for 5.6, two different subnets are mentioned -- 255.255.255.0 AND 255.0.0.0. We found that the router only allowed for 255.255.255.0.

2) In step 8c of step 5.6.2, the starting IP will not say 10.0.0.1. It will say 192.168.1.1 until you power cycle it, which we did immediately after step 8.

3) In step 8c, we did not use 10 (another error in the manual?). Sorry -- I can't look now, but I we picked either 1 or 4 as the last number in IP.

Hope this helps any network neophytes.

[mrattan]

There may have been an update to this that I have not seen - my first encounter with anything other than mechanical was last night helping a fledgling team - but I had a similar problem setting up their bot.

I *think there are typo's in the setup guide.

Normally all of the machines that you want to have (easily) see each other behind a router have to share the same subnet mask.

The commone one used in home networks is 255.255.255.0 (the class C subnet mask), but the FRC document guide, (5.6.1) says to use 255.0.0.0 (the class A subnet mask) for both the Linksys Wireless Gaming Adapter, and your PC (after setting up the wireless router on the operator interface).

...communication badness ensues...

Setting the gaming adapter and your PC to 255.255.255.0 seems to fix the problems (we were able to get the bot wirelessly controlled from LabView).

I'm not sure if my logic was correct in not just switching the router on the O.I. over to the 255.0.0.0 subnet, instead of switching the other two - we didn't have time to try it, and this worked. There may be some reason for the Class A/C mask difference dealing with their networks at the events, but I don't know enough about subnetting to tell.

(I'm curious to see how the events go with 30-50 security wonky networks and all those iPods/team routers in the stands deal with the traffic/etc.)

That brings up two quick questions (and one long one)...

1) Which is right, the Class A or Class C subnet?

2) Does anyone know if we can/should set up security on our OI routers (by MAC address) or will they then not be able to kill them at the end of the round?

3) (unrelated) - Are there any LabView pros going to the Midwest Regional I can steal for about 10-15 mins for a primer

[Mark McLeod]

Your OI router gets left at home for competitions, so the settings on that don't really matter to anyone else. You can restrict by MAC address if you like.

You should use a Class A subnet mask of 255.0.0.0 on your PC and Bridge.
This will work even though the OI router is set to 255.255.255.0. I suspect something else was at work when you ran into trouble.

The Gaming Adaptor on the robot, however, must be accessable security-wise for the Field Management System to set it up for the Virtual Private Network that will be used for field play.

Come prepared to change the settings on your gaming adaptor bridge to what they tell you at the Regional.

[mrattan]

Thanks Mark!

I'll be hooking up lappy as soon as the bot get's de-bagged.