Request: Open FORWARD between the Systemcore's WiFi/USB subnets and eth0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- networking
Research direction
Start by locating the Systemcore firewall configuration that defines the FORWARD policy and interface rules. Review the tested iptables rules for wlan0, usb+, and eth0, including the POSTROUTING MASQUERADE rule. Done means WiFi and USB-connected devices can reach the robot network while established return traffic works as intended.
Written by the indexing model from the issue text.
Description
Desired Workflow:
- Connect a laptop to the Systemcore WiFi and be able to interact with FRC Radio and attached coprocessors. (handy for in-shop use)
- USB device (ex. USB-Ethernet adapter as tether for 1 more coprocessor on radio) connected to the Systemcore and be able to interact with the FRC Radio & attached coprocessors.
Blocker:
FORWARDpolicy isDROPwith no rule betweenwlan0/usb+andeth0- nothing on the Systemcore's WiFi or USB ports can reach the robot network, only the Systemcore.
Request:
- Open
FORWARDbetween the Systemcore WiFi/USB subnets andeth0.
Tested:
iptables -N ROBOT-SEGMENT-FWD
iptables -A ROBOT-SEGMENT-FWD -i usb+ -o eth0 -j ACCEPT
iptables -A ROBOT-SEGMENT-FWD -i wlan0 -o eth0 -j ACCEPT
iptables -A ROBOT-SEGMENT-FWD -i eth0 -o usb+ -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
iptables -A ROBOT-SEGMENT-FWD -i eth0 -o wlan0 -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
iptables -I FORWARD -j ROBOT-SEGMENT-FWD
iptables -t nat -A POSTROUTING -o eth0 ! -s 172.17.0.0/16 -j MASQUERADE
- Dominant language
- Java
- Stars
- 190
- Forks
- 25
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 12
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wpilibsuite/SystemcoreTesting
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#380 ·
Maintainers usually reply within 1 day
-
Limelight Pending
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#315 ·
Maintainers usually reply within 1 day
-
CAN FD not workingOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wpilibsuite/SystemcoreTesting#412 · 14 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wpilibsuite/SystemcoreTesting#411 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
wpilibsuite/SystemcoreTesting#406 · 4 comments ·
Maintainers usually reply within 1 day
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
[Bug] Logo style setting missing and `classic` style not applied across multiple platforms (v3.1.0)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Stirling-Tools/Stirling-PDF#8382 · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 4 days
-
enhancement untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensearch-project/sql#5842 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
openhab/openhab-addons#21882 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
YunaiV/ruoyi-vue-pro#1273 ·
Maintainers usually reply within 3 days