900719_FOCE : Setting up Netgear Router to look like MARS This page last changed on Mar 16, 2011 by bobh. As mentioned in the Network Setup page, the FOCE can has now been configured for MARS. It will work if plugged into the MARS node directly, or into the MARS wet-node simulator. But it won't work if plugged into the MBARI shore network. I've set up a Netgear router that can be used in building B (only!) to simulate enough of MARS routing to allow us to test. This will work in the Software Lab or in the test tank, but not, for example, in building D or G. #### Netgear Router Settings WAN IP address: 134.89.12.162 LAN IP address: 10.1.12.1 To access, browse to http://134.89.12.162:8080 Username: admin Password: rootme Administration port: 8080 DMZ (default port pass-thru): 10.1.12.6 Other ports forwarded: port 80 to 10.1.12.9, Axis Video ports 771, 2000-2104, 1027 to 10.1.12.7, Digi Terminal Server port 3422 to 10.1.12.8, Digi AnywhereUSB #### Setting up the Netgear Router Broswe to http://134.89.12.162:8080 Username: admin Password: rootme The following setup maps ports from the FOCE instruments to IP address 134.89.12.108. It maps all but a few ports through to the FOCE PC/104 stack. It maps: port 8080 to the router itself (for setup) port 80 (http) to the Axis Video server, ports 771, 1027, and 2000-2104 to the DigiTS Terminal Server, and port 3422 to the Digi AnywhereUSB Note - we've now received two static IP addresses for FOCE testing, and I've set up the router for the first one. They are: 134.89.12.162 = focetest1.shore.mbari.org 134.89.12.163 = focetest2.shore.mbari.org (Note - some of the following pictures show 10.1.11.x. Substitute 10.1.12.x. These pages were created when we were on a different port - bobh) ###### Basic Settings ###### ###### LAN Setup ###### WAN Setup ###### ###### Port Forwarding This is where you need to change things to get additional access. Since each port can only be mapped once, you may need to do this. For example, port 80 (http) is mapped by default to the Axis Server. This is to allow access to the video stream. But if you need to modify the Digi PortServer, you need to change this. In this example: Click on the first line and click on "Edit". Change 10.1.12.9 to 10.1.12.7 (the PortServer). Save the change. Browse to http://134.89.12.162, which now points to the Digi PortServer. Do what you need. When done, change the first line back to 10.1.12.9 #### Using the Router ###### PC/104 To get to the FOCE PC/104 controller, use DNS name 'focetest1', which points to the router. The router will forward the requests to the FOCE PC/104. For example, to open a remote shell, type:ssh ops@focetest1. (Note - I've also configured the Linksys router in the software lab. In that case, use 'focetest2'). ###### Video To get to the Axis video server, you can either: browse to http://134.89.12.162, or Use the Axis Camera Station application. In this application, you must go to Options->Camera Settings, and set it up like this: ###### ###### Anywhere USB We don't have the AnywhereUSB working quite yet. It should work as follows. Bring up the AnywhereUSB Configuration Utility. Choose Command->ConfigurationList. Add 134.89.12.162 to the list. It should find the USB server and allow you to connect to it. ###### Serial Ports To use the TerminalServer, you must have the Digi RealPort software installed on your PC. This installs as a Windows driver. To configure RealPort for this configuration, go to Start->Settings->ControlPanel. Double-click System. Choose the Hardware tab, and choose Device Manager. Open up the list item labelled "Multi-port serial adapters". It should look something like this: Now look for the "PortServer TS 4", right-click, and open "Properties". Click the "Advanced" tab, and click on "Properties". Click on the "Network" tab. Under "IP address", insert 134.89.12.162. It should look like this: For connection to the MARS node, set the IP address to 134.89.42.127. For connection to the WNS (wet-node simulator), change it to 134.89.52.127. ###### Which Serial Port to Use Notice that the Device Manager Screen above also has a list called "Ports (COM & LPT)". You can use that to associate the Windows COMx serial port names with the PortServer port numbers. I'll use the screen shot above, which was taken on the FOCE laptop, as an example. In the FOCE can: The first serial port (PortServer Port 1) is connected to the Insite Camera. You can see from the Device Manager that this is mapped to COM2. The second serial port (PortServer Port 2) is connected to the PC/104 stack. In this example, this is COM15. This is the serial port that displays the Linux boot messages, and which you can then use to log into Linux. The third and fourth serial ports are unused (I think). ###### Attachments: netgearMainScreen.PNG (image/png) netgearMainScreen.PNG (image/png) netgearMainScreenSm.png (image/png) netgearLANSm.png (image/png) netgearLAN.PNG (image/png) netgeaWAN.PNG (image/png) netgearForwarding.PNG (image/png) AxisCamera.PNG (image/png) DeviceManager.PNG (image/png) DeviceManager.PNG (image/png) DeviceManager.PNG (image/png) PortServerNetwork.PNG (image/png)

Document generated by Confluence on Feb 03, 2026 14:29