This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
advanced-access [2024/10/08 23:47] – -Condense hogwild | advanced-access [2024/11/27 01:30] (current) – [LAN Access] -Condense, formatting hogwild | ||
---|---|---|---|
Line 13: | Line 13: | ||
{{: | {{: | ||
- | **On: | + | **On: |
\\ | \\ | ||
- | **Src: | + | **Src:** displays/ |
\\ | \\ | ||
- | **Src Address: | + | **Src Address: |
\\ | \\ | ||
- | **Dst: | + | **Dst: |
\\ | \\ | ||
- | **Dst Address: **(optional) narrows the rule to a specific IP address | + | **Dst Address: **(optionally), narrows the rule to a specific IP address/set of addresses within the Dst interface. |
\\ | \\ | ||
- | **Description: | + | **Description: |
\\ | \\ | ||
\\ | \\ | ||
+ | |||
===== LAN Access Notes ===== | ===== LAN Access Notes ===== | ||
- | Regardless of LAN Access rules, by default a LANx device is able to reach (e.g. ping) all the router' | + | * Regardless of LAN Access rules, by default a LANx device is able to reach (e.g. ping) all the router' |
- | + | * All entries in LAN Access are one-way only. For example, if you want hosts on LAN0 to be able to communicate with hosts on LAN1, and vice versa, you'll need two entries in the table to achieve that. | |
- | **All entries in LAN Access are one-way only.** \\ For example, if you want hosts on LAN0 to be able to communicate with hosts on LAN1, and vice versa, you'll need two entries in the table to achieve that. | + | * LAN Access is an IP-level access control. Therefore, **all ports/ |
- | + | ||
- | **LAN Access is an IP-level access control.** \\ Therefore, **all ports/ | + | |
\\ | \\ |