3 PC Engines and PEPsal » History » Version 12
MERIOCHAUD, Antoine, 03/10/2016 04:14 PM
| 1 | 1 | MERIOCHAUD, Antoine | h3. 3. PC Engines and PEPsal |
|---|---|---|---|
| 2 | 9 | MERIOCHAUD, Antoine | |
| 3 | 2 | MERIOCHAUD, Antoine | The computers used to install PEPsal are these small computers with only 3 Ethernet ports. |
| 4 | 2 | MERIOCHAUD, Antoine | |
| 5 | 1 | MERIOCHAUD, Antoine | !apu1c.png! |
| 6 | 1 | MERIOCHAUD, Antoine | +Figure 1: PC Engines used in the lab+ |
| 7 | 3 | MERIOCHAUD, Antoine | |
| 8 | 6 | MERIOCHAUD, Antoine | All the configurations we will explain in this page correspond to the PEP on the Hub side. A similar configuration is used on the Remote Terminal PEP, only IP adresses are different. |
| 9 | 6 | MERIOCHAUD, Antoine | |
| 10 | 1 | MERIOCHAUD, Antoine | The first Ethernet port is used for management so to access these computers we use the management computer shown in the network architecture to connect with SSH protocol : |
| 11 | 1 | MERIOCHAUD, Antoine | @sudo ssh labo@192.168.0.200@ |
| 12 | 6 | MERIOCHAUD, Antoine | Once it is done, we can control the computer to configure the others Ethernet ports according to the network architecture : |
| 13 | 1 | MERIOCHAUD, Antoine | @ifconfig p5p1 192.168.1.3@ |
| 14 | 8 | MERIOCHAUD, Antoine | Now we need to tell to the computer that to send a paquet on the network 192.168.2.0/24 (it is not a network directly connected to the PEP) he needs to send it to the modem on the HUB side : |
| 15 | 1 | MERIOCHAUD, Antoine | @route add -net 192.168.2.0/24 gw 192.168.1.2@ |
| 16 | 8 | MERIOCHAUD, Antoine | |
| 17 | 11 | MERIOCHAUD, Antoine | Then we installed PEPsal on the computer using @scp@ command to transfer the archive file that you can find on https://sourceforge.net/projects/pepsal/ |
| 18 | 12 | MERIOCHAUD, Antoine | |
| 19 | 12 | MERIOCHAUD, Antoine | Now the PEPs are correctly configured and the communication is fully operational. |