Differences

This shows you the differences between two versions of the page.

--- disable_access_to_admin_access_ssh:gui_for_guest_v:wlan [2021/02/09 23:00] – hogwild
+++ disable_access_to_admin_access_ssh:gui_for_guest_v:wlan [2024/03/02 17:01] (current) – hogwild
@@ Line 1: / Line 1: @@
-===== Disable access to admin access (SSH/GUI) for guest V/WLAN =====
+====== Disable Administrative Access (SSH/GUI) to Guest VLAN/WLAN ======
-The default settings make Tomato's administration ports (SSH and HTTP/S) reachable from all VLANs/WLANs configured on the router.
+The default settings allow access to the router's administration ports (SSH and HTTP/S) from all configured VLANs/WLANs.
-If you don't wish to have communication available, you can filter out access to those ports by using the following script in the Administration/Scripts/Firewall page:
+If you don't want communication on a certain VLAN or WLAN, you can filter out access to its ports using the following script in the //Firewall// field of the [[https://wiki.freshtomato.org/doku.php/admin-scripts|Scripts]] menu:  \\  \\
-<code>
+<code ->
 iptables -t filter -I INPUT 1 -p tcp -m multiport -i br1 --dport 22,23,80,443 -j REJECT
 </code>
-If you're using non-standard port numbers, You can change the ports used above (22,80,443). You can also add additional lines changing br1 if you have multiple bridges/guest VLAN
+\\
+The bridge number ("br1" in the example) represents the interface on which you want access disabled. Double check the [[basic-network|Network]] menu to be certain. **Avoid filtering on bridge "br0"** to avoid locking out access to the router.
+If you use non-standard port numbers, you can change the port numbers used above (22,80,443).
-NOTE: mind not locking yourself out, you would most likely not want to filter on br0
+If you have multiple bridges or guest VLANs, you can add additional lines and change the relevant bridge interface names. The command will take effect as soon as the next run of the firewall script.
-NOTE2: This will take effect as soon as the firewall script is called next. You can force this manually with either a **service firewall restart** or rebooting the device.
+You can force the command(s) to take effect manually by logging on to the router and typing the command: "//service firewall restart" //or by rebooting the device.

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools