This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
advanced-access [2023/09/11 18:33] – [LAN Access Notes] -add warning about LAN Access being an IP-level access control hogwild | advanced-access [2023/09/12 17:16] – [LAN Access Notes] -add note that table entries only permit traffic in one direction hogwild | ||
---|---|---|---|
Line 7: | Line 7: | ||
For example, let's say we have two LANs, one primary (LAN0/br0) and one secondary (LAN1/br1). | For example, let's say we have two LANs, one primary (LAN0/br0) and one secondary (LAN1/br1). | ||
- | If we want devices on LAN0 to | + | If you want devices on LAN0 to be able to communicate with devices on LAN1 (and vice versa), |
\\ | \\ | ||
Line 34: | Line 34: | ||
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 the LAN Access table are one-way only. So, if you want hosts on LAN0 to be able to communicate with hosts on LAN1, | ||
+ | you must create have entries in the table to achieve that. One allowing traffic from LAN0 to LAN1 and another allowing traffic from LAN1 to LAN0. | ||
+ | |||
LAN Access is an IP-level access control. This means that **all ports/ | LAN Access is an IP-level access control. This means that **all ports/ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||