479
edits
Changes
Template:Networking rutos configuration example guest wifi (view source)
Revision as of 12:09, 22 July 2020
, 12:09, 22 July 2020→Results
Guest hosts are unable to access any data from pool 192.168.1.0/24.
Guest hosts are unable to access any data from pool 192.168.1.0/24.
-----
<table class="nd-othertables_2">
<tr>
<th width=355; style="border-bottom: 1px solid white;></th>
<th width=790; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rut_configuration_example_openvpn_bridge_use_case_9_v2.png|border|class=tlt-border|728px|right]]</th>
</tr>
<tr>
<td style="border-bottom: 1px solid white>
Remote office should now be able to access HQ network resources. To verify the connection you can ping remote RUTX (HQ server) LAN IP and if you get a reply, you have successfully connected to HQ‘s internal network. Also, all LAN addresses, that belong to the work network (192.168.1.0/24), should now be leased to LAN devices by HQ router.
</td>
</tr>
</table>
----
<table class="nd-othertables_2">
<tr>
<th width=355; style="border-bottom: 1px solid white;></th>
<th width=790; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rutos_configuration_example_openvpn_bridge_use_case_19_v2.png|border|class=tlt-border|728px|right]]</th>
</tr>
<tr>
<td style="border-bottom: 1px solid white>
In order to check the guest WiFi, you simply need to connect to the newly created WiFi AP, then check whether you have internet connectivity and try to ping OpenVPN server LAN IP - if everything is set up correctly, you should not be able to do that.
</td>
</tr>
</table>
