Lancethepants at 05:43, 30 September 2023

2023-09-30T05:43:28Z

← Older revision		Revision as of 05:43, 30 September 2023
Line 21:		Line 21:
	'''Dst:''' Here, you specify the (logical) Destination LAN for the rule on this row of the table.		'''Dst:''' Here, you specify the (logical) Destination LAN for the rule on this row of the table.

	Dst Address: (optional) narrows the rule to a specific IP address or set of addresses within the Dst interface.		'''Dst Address: '''(optional) narrows the rule to a specific IP address or set of addresses within the Dst interface.

	'''Description:''' This is a free text field in which to enter whatever you wish as a reminder, note etcetera.		'''Description:''' This is a free text field in which to enter whatever you wish as a reminder, note etcetera.

Lancethepants at 05:39, 30 September 2023

2023-09-30T05:39:45Z

← Older revision		Revision as of 05:39, 30 September 2023
Line 10:		Line 10:

	<br />		<br />
	[[File:~~/pasted/~~20220126-183839.png\|~~20220126-183839.png~~]]<br />		[[File:20220126-183839.png\|frame\|none]]
			<br />
	<br />		<br />
	'''On:''' Checking this enables the rule defined on this row of the table.		'''On:''' Checking this enables the rule defined on this row of the table.

Lancethepants: Created page with " = LAN Access = This page allows you to define LAN-to-LAN traffic where it otherwise would be blocked.
For example, let's say we have two LANs, one primary (LAN0/br0) and one secondary (LAN1/br1). If you want devices on LAN0 to be able to communicate with devices on LAN1 (and vice versa), you might use these settings:
20220126-183839.png

'''On:''' Checking this enables the ru..."

2023-09-26T16:10:05Z

Created page with " = LAN Access = This page allows you to define LAN-to-LAN traffic where it otherwise would be blocked. For example, let's say we have two LANs, one primary (LAN0/br0) and one secondary (LAN1/br1). If you want devices on LAN0 to be able to communicate with devices on LAN1 (and vice versa), you might use these settings: 20220126-183839.png '''On:''' Checking this enables the ru..."

New page

= LAN Access =

This page allows you to define LAN-to-LAN traffic where it otherwise would be blocked.

 
For example, let's say we have two LANs, one primary (LAN0/br0) and one secondary (LAN1/br1).

If you want devices on LAN0 to be able to communicate with devices on LAN1 (and vice versa), you might use these settings:

 
[[File:/pasted/20220126-183839.png|20220126-183839.png]] 
 
'''On:''' Checking this enables the rule defined on this row of the table.

'''Src:''' This displays/allows you to configure the (Logical) Source LAN for the rule on that row of the table.

'''Src Address:''' This (optional) field narrows the rule to a specific IP address or set of addresses within the Src interface.

'''Dst:''' Here, you specify the (logical) Destination LAN for the rule on this row of the table.

**Dst Address: **(optional) narrows the rule to a specific IP address or set of addresses within the Dst interface.

'''Description:''' This is a free text field in which to enter whatever you wish as a reminder, note etcetera.

 
 


== LAN Access Notes ==

Regardless of LAN Access rules, by default a LANx device is able to reach (e.g. ping) all the router's LAN interfaces (only). This is by design.

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 hosts on LAN1 to be able to communicate with hosts on LAN0, you will need to have two entries in the table to achieve that.

LAN Access is an IP-level access control. 
This means that '''all ports/protocols are automatically enabled'''. If additional fine tuning is required (for example, you wanted to allow only allow port 80/TCP) you will need to manually configure settings instead.

Advanced-access - Revision history

Lancethepants at 05:43, 30 September 2023

Lancethepants at 05:39, 30 September 2023