User:Plauchu Edwin: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(202 intermediate revisions by the same user not shown)
Line 1: Line 1:
Software developer over several open source languages
[[AFT installation]]


=== Setup harness server ===
[[Manteiner python3-numpy]]
==== OS Installation ====
The linux distribution utilized as harness server during this setup is Ubuntu yakkety.


==== Firewall configuration ====
[[Arduino Single power control unit]]
Firewall configuration is not provided, it is recommended that the testing harness is only kept in a trusted network.
 
To check if no firewall are configured over testing-harness, we can expect a similar output when inquiring iptables...
<pre>
root@testing-harness:~# iptables -L && iptables -t nat -L
Chain INPUT (policy ACCEPT)
target    prot opt source              destination       
 
Chain FORWARD (policy ACCEPT)
target    prot opt source              destination       
 
Chain OUTPUT (policy ACCEPT)
target    prot opt source              destination       
 
Chain PREROUTING (policy ACCEPT)
target    prot opt source              destination       
 
Chain INPUT (policy ACCEPT)
target    prot opt source              destination       
 
Chain OUTPUT (policy ACCEPT)
target    prot opt source              destination       
 
Chain POSTROUTING (policy ACCEPT)
target    prot opt source              destination       
</pre>
 
==== Setup Security shell ====
OpenSSH is a freely available version of the Secure Shell (SSH) protocol family of tools for remotely controlling, or transferring files between, computers. That's why it is required its installation upon testing-harness server.
<pre>
root@testing-harness:~# aptitude install openssh-server
</pre>
 
==== Setup NFS ====
AFT applies Network file system to share /home/tester directory where images and other files used in flashing for PC-devices within AFT net can be found.
 
===== NFS is installed ? =====
To check if the NFS server is installed, we can do...
<pre>
root@testing-harness:~# dpkg -l | grep nfs-kernel-server
</pre>
 
===== How to install NFS ? =====
To install NFS these are the required packages...
<pre>
root@testing-harness:~# aptitude install nfs-kernel-server
The following NEW packages will be installed:
  keyutils{a} libnfsidmap2{a} libtirpc1{a} nfs-common{a} nfs-kernel-server
  rpcbind{a}
0 packages upgraded, 6 newly installed, 0 to remove and 459 not upgraded.
Need to get 470 kB of archives. After unpacking 1 884 kB will be used.
Do you want to continue? [Y/n/?]
</pre>
 
===== Sharing /home/tester directory =====
<pre>
root@testing-harness:~# mkdir -p /home/tester
root@testing-harness:~# echo '/home/tester 192.168.1.0/24 (crossmnt,ro,root_squash,sync,no_subtree_check)' >> /etc/exports
</pre>
 
==== Setup DNS cache and DHCP server for AFT net ====
DNSmasq provides two services, either of which can be used independently.
# DNS service
# DHCP service
 
A local DNS cache can speed up internet browsing because the user's applications will not need to access a domain name server when it looks up a domain name the computer has visited before.
 
===== How to install dnsmasq ? =====
To install dnsmasq these are the required packages...
<pre>
root@testing-harness:~# aptitude  install dnsmasq
The following NEW packages will be installed:
  dns-root-data{a} dnsmasq dnsmasq-base{a}
0 packages upgraded, 3 newly installed, 0 to remove and 459 not upgraded.
Need to get 0 B/329 kB of archives. After unpacking 886 kB will be used.
Do you want to continue? [Y/n/?
</pre>
At the sametime we have set up a simple DNS server. To test it, use your favorite DNS lookup tool pointed at localhost
<pre>
root@testing-harness:~# nslookup yoctoproject.org localhost
Server: localhost
Address: 127.0.0.1#53
 
Non-authoritative answer:
Name: yoctoproject.org
Address: 140.211.169.56
</pre>
 
===== Configure DHCP server =====
To enable the DHCP server of AFT net, you will need to give it a range of IP addresses to hand out. The AFT net server would hand out 92 address starting at 192.168.1.2 and ending at 192.168.1.99.
<pre>
root@testing-harness:~# echo 'dhcp-range=192.168.1.2,192.168.1.99,10m' >> /etc/dnsmasq.conf
</pre>
 
To tell dnsmasq which ethernet interface it can and cannot listen on.
<pre>
root@testing-harness:~# echo 'interface=eno1' >> /etc/dnsmasq.conf
</pre>
During the creation of this document the interface eno1 is the unique one connected to AFT net.
 
===== AFT and its relation with dnsmasq.leases =====
As of dhcp server is up and running. AFT shall utilize dhcp-server's active ip leasing information to determine device IP address of PC-devices over AFT net. By default it is found upon /var/lib/misc/dnsmasq.leases
<pre>
root@testing-harness:~# cat /var/lib/misc/dnsmasq.leases
 
1417132679 78:c5:e5:b4:4d:07 192.168.1.99 minox-fbe390b0bb404da *
1417134678 20:54:76:e4:d8:a5 192.168.1.57 minoy-ab6e5d0a524c9c7d *
......
.......
........ and so on...
</pre>
Above a common dnsmasq.leases file.

Latest revision as of 18:06, 14 December 2016