| | 1 | = The ethernet port when using QRM = |
|---|
| | 2 | The ethernet port (ETH) of the Fonera is not need for the functionality of the FON WiFi hotspot anymore. But we can use it to have access to the internal network, and the internet also, from an area that is not equipped with cable network. |
|---|
| | 3 | |
|---|
| | 4 | == ETH with a PC connected == |
|---|
| | 5 | Assuming that the living room is not equipped with cable network and because of that we placed a Fonera in the corridor, providing a private WLAN signal.[[br]] |
|---|
| | 6 | Now we attach a private IP address to ETH and enable DHCP, that is given an address range from which it will share out adresses to the clients also. |
|---|
| | 7 | {{{ |
|---|
| | 8 | [QRM - with Ethernet and DHCP] |
|---|
| | 9 | (192.168.3.0/24) (192.168.10.0/24) |
|---|
| | 10 | private Signal |
|---|
| | 11 | / (LAN) |
|---|
| | 12 | (..3.1)| WLAN (..3.2) |
|---|
| | 13 | DSL - FritzBox -- | SSID: . . : : . . (WAN) FONERA (ETH) (..100.1/24) DHCP (..100.10-..100.50) |
|---|
| | 14 | (..1.1)| |MyCastle | |
|---|
| | 15 | | \ (WIFI) | |
|---|
| | 16 | | public Signal | |
|---|
| | 17 | | (192.168.182.0/24) | |
|---|
| | 18 | | | |
|---|
| | 19 | PC1 PC10 |
|---|
| | 20 | (192.168.1.10) (192.168.100.12) |
|---|
| | 21 | }}} |
|---|
| | 22 | The QRM is running and we have access to the local network while connected to the private WiFi signal. Now we consider another PC10 that sadly does not have WLAN device ready but which has a LAN card installed.[[br]] |
|---|
| | 23 | We activate the ethernet port of the FONERA and apply suitable IP address (192.168.100.1) and subnet mask. After switching on DHCP server we define the address range of addresses that are shared out to the clients later on. So we do with the nameserver and the standard gateway. Using the setup showed in the sample above these would be the following:[[br]] |
|---|
| | 24 | {{{ |
|---|
| | 25 | Range from 192.168.100.10 |
|---|
| | 26 | Range to 192.168.100.50 |
|---|
| | 27 | Nameserver 192.168.100.1 |
|---|
| | 28 | Gateway 192.168.100.1 |
|---|
| | 29 | }}} |
|---|
| | 30 | Leave the option "NAT" enabled.[[br]] |
|---|
| | 31 | [[br]] |
|---|
| | 32 | PC10 gets its IP settings from the Foneras DHCP server (..100.12) and has access to the internet and PC1 routed through the Fonera now. Because we didn't disable NAT, all packeges from PC10 sent to PC1 will be masked with the Foneras IP address at LAN/WAN port. In fact that means that PC1 just seems to receive all the data from the Fonera itself. Reverse access from PC1 to PC10 will not be possible directly. Thats why we enabled NAT also. |
|---|
| | 33 | |
|---|
| | 34 | == NAT - Network Address Translation == |
|---|
| | 35 | Enabled NAT option may be of advantage in some cases hence a route to the senders IP address, that one of PC10 (..100.12) this case, mustn't be known at all. It's quit enough that PC1 knows to send back all answers back to the Foneras IP address 192.168.3.2, because the Fonera had masked all request packages with its own address. |
|---|
| | 36 | |
|---|
| | 37 | == having NAT disabled == |
|---|
| | 38 | In most case it is wanted to have access vice versa from PC1 to PC10 too. Therefore NAT option has to be disabled. But now some things need special attention.[[br]] |
|---|
| | 39 | [[br]] |
|---|
| | 40 | Hence we want to have a connection from PC1 to PC10, we need to know the route to its network (192.168.100.0/24). PC1 will use the !FritzBox as default route normaly (..1.1), so the !FritzBox needs to know the right way to cable network of the Fonera (192.168.100.0/24). We have to set a route to that network and use the Foneras IP address as gateway. |
|---|
| | 41 | {{{ |
|---|
| | 42 | System/Network settings /IP-Routen |
|---|
| | 43 | IP-Network: 192.168.100.0 |
|---|
| | 44 | Subnet mask: 255.255.255.0 |
|---|
| | 45 | Gateway: 192.168.3.2 (WAN-IP-Address of the FONERA) |
|---|
| | 46 | }}} |
|---|
| | 47 | |
|---|
| | 48 | == ETH with a ethernet switch installed / Network == |
|---|
| | 49 | The same settings are needed if a ethernet switch is connected to the Fonera to have more than one PC connected with the help of the Foneras WLAN to the private LAN and the internet. |
|---|
| | 50 | {{{ |
|---|
| | 51 | [QRM - using Ethernet, DHCP und SWITCH] |
|---|
| | 52 | (192.168.3.0/24) (192.168.10.0/24) |
|---|
| | 53 | private Signal |
|---|
| | 54 | / (LAN) |
|---|
| | 55 | (..3.1)| WLAN (..3.2) |
|---|
| | 56 | DSL - FritzBox -- | SSID: . . : : . . (WAN) FONERA (ETH) (..100.1/24) DHCP (..100.10-..100.50) |
|---|
| | 57 | (..1.1)| |MyCastle | |
|---|
| | 58 | | \ (WIFI) | |
|---|
| | 59 | | public Signal +---- SWITCH ----+ |
|---|
| | 60 | | (192.168.182.0/24) | | | | |
|---|
| | 61 | | | | | | |
|---|
| | 62 | PC1 | | | | |
|---|
| | 63 | (192.168.1.10) PC10 PC11 PC12 PC13 |
|---|
| | 64 | }}} |
|---|
