Deployment B

This second deployment is a bit more complex sceneario than the first example. It consists of a computer network, which might be the computer network of a company, which has a SERVAL server installed and it owns several internal machines. Moreover, there are also several external clients wanting to access to the network through SERVAL.

The purpose of this deployment is to include the external clients in the computer network at ethernet level without having to install the SERVAL client in all the internal machines of the computer network. In order to achieve this, the promiscous mode option has been used and also a bridge has been configured.

The network has a gateway, which is the entrance point to the network, and it does port forwading redirecting three ports to the machine running the SERVAL server. The host A runs the SERVAL server listening at port 5690 for tcp connections, at port 6690 por udp connections and at 5443 for ssl.

The description of the machines taking part in the deployment is the following:

• external machine 1. It is a computer which connects to SERVAL from an external location through the corporate gateway.
• external machine 2. It is a second computer which connects to SERVAL from an outer location.
• internal machine 1. It is an internal machine and has the promiscous mode turned on. It has also a bridge configured between its two ethernet interfaces, the tap0 - the SERVAL interface - and the eth0 - the real network interface -.
• internal machine 2. It is a second internal machine which has not installed the SERVAL client.

All the SERVAL clients are authenticated and joined to the vlan vlan1 and they were assigned IPs from the same subnet 192.168.30.0/24. A schema representing the deployment can be seen in the draw below this paragraph.

The tests done with this deployment are the following:

• We sent a broadcast ping from the each of the clients and also from the internal machine 2 and answered to the broadcast both the three SERVAL clients and the internal machine 2.

    $ ping 192.168.30.255

      PING 192.168.30.255 (192.168.30.255): 56 data bytes
      64 bytes from 192.168.30.18: icmp_seq=0 ttl=64 time=0.0 ms
      64 bytes from 192.168.30.99: icmp_seq=0 ttl=64 time=1.7 ms (DUP!)
      64 bytes from 192.168.30.87: icmp_seq=0 ttl=64 time=166.7 ms (DUP!)
      64 bytes from 192.168.30.11: icmp_seq=0 ttl=64 time=492.9 ms (DUP!)

• We executed from external machine 1 and external machine 2 the smbtree utility and we discovered the directories shared by the internal machine 1 SAMBA server.

div class="twikiTopicInfo twikiRevInfo twikiGrayText twikiMoved"<&/div>-->