-
Notifications
You must be signed in to change notification settings - Fork 16
Remote Acccess to Rover
In-person development:
- Connect to SCRB-Access (or 5GHz version), use the same password as before. Or connect with cable to any available port on the rover (WAN port is configured as LAN port).
- You will be assigned a 10.240.0.100~249 address
- The Jetson is available at 10.240.0.10
- Leave the router ON when development is finished.
Remote development: Windows quick start:
- As long as you are not directly connected to SCRB-Access, you may VPN into it.
- Install OpenVPN at https://openvpn.net/community-downloads/ (select the latest Windows MSI installer)
- Download the .ovpn file available in the drive and copy it to C:\Users<username>\OpenVPN\config\
- Launch OpenVPN GUI and right click the system tray icon.
- Select connect. OpenVPN will prompt for a client password. Use the same password as our WiFi.
- You will be assigned a 10.240.1.x address. Access resources just like in-person development.
Remote development: Ubuntu GUI quick start:
- As long as you are not directly connected to SCRB-Access, you may VPN into it.
- Download the .ovpn file available in the drive.
- Launch settings - network. In the VPN section, click Add VPN on the top right corner. Select Import from File. (You may wish to clean old cert files in ~/.cert/nm-openvpn/)
- Import the .ovpn file. Important: after importing the file, launch the connection configuration dialog (gear icon on the right), go to IPv4 and IPv6 and check “Use this connection only for resources on its network”.
- Enable VPN. When prompting a client password, use the same password as our WiFi.
- You will be assigned a 10.240.1.x address. Access resources just like in-person development. The connection can be managed in the command line or GUI.
Network Infrastructure:
- Intranet:
- Subnet 10.240.0.1/24, in-office resources:
- 10.240.0.1 is the router itself.
- 10.240.0.10 is the Jetson.
- 10.240.0.11 is the Jetson when connected to the router via WiFi.
- 10.240.0.21 is the base station radio (AP).
- 10.240.0.22 is the rover radio (STA).
- 10.240.0.100 to 249 are in person developers.
- Wireless APs:
- SCRB-Access, SCRB-Access-5GHz
- Subnet 10.240.1.0/24, remote resources:
- 10.240.1.1 is the OpenVPN gateway.
- 10.240.1.2 to 254 are remote developers.
- Subnet 10.240.2.0/24, bridging infrastructure:
- 10.240.2.1 is the WireGuard server interface.
- 10.240.2.2 is the WireGuard client interface.
- Any two devices in this intranet can communicate.
- Subnet 10.240.0.1/24, in-office resources:
- Cloud:
- 15.223.66.115 is the AWS server (SCRB-AccessCloud)
- Devices with multiple IP addresses:
- Router: 10.240.0.1, 10.240.2.2
- Server: 10.240.1.1, 10.240.2.1, 15.223.66.115
- Guest WLAN network: SCRB-Hotspot, SCRB-Hotspot-5GHz can be used to provide alumni with Internet access, or when Concordia WiFi breaks. Guest network is completely isolated from SCRB Intranet.
Remote development 101: OpenVPN creates a virtual network adapter on your machine that is “virtually” connected to the networking infrastructure. The infrastructure can be used to access lab resources such as the Jetson, and can also be used to bridge in-office and remote developers’ computers. OpenVPN server authenticates clients in a way similar to SSH key files.
Multiple setups for the Jetson available:
- Production setup: Connect both radios to injectors. Connect the AP radio to the router. Connect the STA radio to the Jetson. Ensure Jetson WiFi is OFF or at least not connected to the base station router. We usually use this setup.
- With the current firmware the 5.8GHz radios have a speed of 6.1MB/s.
- Development setup: No radio needed. Connect the Jetson to the router via WiFi. The Jetson is available at 10.240.0.11 instead to prevent an IP conflict.
- Recovery setup: No WiFi needed. Connect the Jetson to the router via cable.
Troubleshooting for in-person developers: Cannot access Jetson: Connect to SCRB-Access WiFi. Make sure VPN is OFF. Make sure Jetson is ON. The fan may be running even if the Jetson is OFF to protect the SoM when flashing. Ping 10.240.0.1 or open in the browser. If nothing shows up, your computer can’t even access the router. Check WLAN DHCP settings, make sure it is “automatic”, and/or restart your computer to restore routing table settings. If using radio setup: Ping 10.240.0.21. If no response, the base station radio (AP) is unplugged or malfunctioning. Ping 10.240.0.22. If no response, the rover radio (STA) is unpowered, still powering on, or malfunctioning. Make sure the AP and the STA are NOT connected to the router via cables simultaneously. This creates a broadcast storm. Alway check cables: some cables may look connected but actually need to be pushed in Try recovery setup (using the cable). Cannot access Internet: If the router has disconnected from upstream WiFi, the LED will be breathing blue. The router will automatically retry. Otherwise it’s solid white. Launch 10.240.0.1 in browser. You may be prompted to ignore a certificate warning. Login with credentials. In the Internet tab (default), scroll down to repeater settings, connect to eduroam with the following credentials: [email protected] Your concordia password This should connect in a while. Otherwise, try ConcordiaUniversity.
Troubleshooting for remote developers: Cannot connect to VPN: The VPN server may be down. Try SSH into 15.223.66.115 with any username (note: the server will not respond to pings). If it shows something (fingerprints etc), then the server is up. No need to login. Check your configuration file revision and recent announcements in the chat. Sometimes the credentials are updated on the server and authentication fails. Simply download the latest version of the configuration file. Cannot access : Ensure VPN is connected. Ping 10.240.1.1. This is the gateway of OpenVPN. If no response, check VPN settings and local routing table. It should not happen. Ping 10.240.2.1. This is the server wireguard interface. If no response, the server is not correctly configured. Ping 10.240.2.2. This is the router wireguard interface. If no response, the router is unpowered or not connected to Internet. This is the most likely cause of a broken network bridge. You can wait and retry. Ping 10.240.0.1. This is the router itself. If no response, the router is not correctly configured. Ping the Jetson or the desired client. If still no response, refer to in-person connectivity troubleshooting. If server or router is down or not properly configured, contact the networking person.
Remote development: Android quick start: Android devices can also remote into the infrastructure, especially web-based monitoring Download or transfer the .ovpn file to the phone Download the Android app: https://play.google.com/store/apps/details?id=net.openvpn.openvpn In the app, click import button (orange plus) Click upload file and select the .ovpn file Click the button to connect to VPN. You will be assigned a 10.240.1.x address. Access resources such as video streams.
Note: disconnect from VPN if connected to SCRB-Access network directly.
AWS server IP: 15.223.66.115; username ubuntu, keyfile available in the drive.