User Tools

Site Tools


docs:guide-user:network:routedclient

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
docs:guide-user:network:routedclient [2018/06/11 13:56]
tmomas link fixed
docs:guide-user:network:routedclient [2018/09/16 12:37] (current)
bobafetthotmail moving links before article move operation
Line 8: Line 8:
  
 If you have no administrative access (e.g. ability to configure static route entries) to the target Access Point, the local LAN subnet must be //​masqueraded//​ to ensure proper routing.\\ If you have no administrative access (e.g. ability to configure static route entries) to the target Access Point, the local LAN subnet must be //​masqueraded//​ to ensure proper routing.\\
-When configuration of the target Access Point is possible, start with the //​masqueraded//​ configuration below and proceed with the steps in the [[#using.routing|Using routing]] section to define a fully routed setup.+When configuration of the target Access Point is possible, start with the //​masqueraded//​ configuration below and proceed with the steps in the [[#using_routing|Using routing]] section to define a fully routed setup.
  
 {{:​doc:​howto:​802.11-routed-masq.png|Masqueraded}} {{:​doc:​howto:​802.11-routed-masq.png|Masqueraded}}
Line 151: Line 151:
 In addition to the files in the [[#​using.masquerade|masqueraded setup]], the relevant config files are: In addition to the files in the [[#​using.masquerade|masqueraded setup]], the relevant config files are:
  
-  * [[docs:​guide-user:firewall:firewall_configuration|/​etc/​config/​firewall]]+  * [[inbox:firewall:start|/​etc/​config/​firewall]]
  
 === Step 1: Change the firewall configuration === === Step 1: Change the firewall configuration ===
  
-Edit the ''/​etc/​config/​firewall''​ file and locate the WAN [[docs:​guide-user:firewall:firewall_configuration#​zones|zone]] definition.+Edit the ''/​etc/​config/​firewall''​ file and locate the WAN [[inbox:firewall:firewall3:​fw3_network|zone]] definition.
 Disable masquerading and set the incoming traffic policy to ACCEPT: Disable masquerading and set the incoming traffic policy to ACCEPT:
  
Line 166: Line 166:
         option '​masq' ​      ​**'​0'​** ''​ |         option '​masq' ​      ​**'​0'​** ''​ |
  
-Proceed with adding a new [[docs:​guide-user:firewall:firewall_configuration#​forwardings|forwarding]] section allowing traffic flow from WAN to LAN:+Proceed with adding a new [[inbox:firewall:fw3_configurations:​fw3_config|forwarding]] section allowing traffic flow from WAN to LAN:
  
 | ''​config '​forwarding'​ | ''​config '​forwarding'​
Line 219: Line 219:
 \\ \\
 If you cannot (or don't want to) modify AP router'​s firewall in deep, you can configure client router (192.168.2.1) in the following way:\\ If you cannot (or don't want to) modify AP router'​s firewall in deep, you can configure client router (192.168.2.1) in the following way:\\
-Edit the ''/​etc/​config/​firewall''​ file and locate the WAN [[docs:​guide-user:firewall:firewall_configuration#​zones|zone]] definition. \\+Edit the ''/​etc/​config/​firewall''​ file and locate the WAN [[inbox:firewall:firewall3:​fw3_network|zone]] definition. \\
  
 | ''​config '​zone'​ | ''​config '​zone'​
Line 322: Line 322:
 First we should enable the possibility that packets coming on First we should enable the possibility that packets coming on
 the wan side of **WC** could reach the lan side of **WC**. This the wan side of **WC** could reach the lan side of **WC**. This
-is done through forwarding (see [[docs:​guide-user:firewall:firewall_configuration]] and [[docs:​guide-user:​firewall:​netfilter-iptables:​iptables_and_firewall]] ).+is done through forwarding (see [[inbox:firewall:start]] and [[docs:​guide-user:​firewall:​netfilter-iptables:​iptables_and_firewall]] ).
  
 In particular we want that if a packet coming on the wan side of **WC** has the source in the network In particular we want that if a packet coming on the wan side of **WC** has the source in the network
docs/guide-user/network/routedclient.1528725367.txt.gz · Last modified: 2018/06/11 13:56 by tmomas