Support & information center

How can I tell that my test’s network profile is working?

If you are familiar with the iptables rules, you can see the actual rules in the test’s ‘Nightwatch logs’ tab (in the session level).

You should see something like:

iptables_flush_2 --------------------------
iptables_flush_1 --------------------------
iptables_list-OUT: -P INPUT DROP
iptables_list-OUT: -P FORWARD DROP
iptables_list-OUT: -P OUTPUT DROP
iptables_list-OUT: -A INPUT -i lo -j ACCEPT
iptables_list-OUT: -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables_list-OUT: -A INPUT -i eth0 -m state --state INVALID -j DROP
iptables_list-OUT: -A INPUT -i eth0 -p udp -m udp --sport 53 -j ACCEPT
iptables_list-OUT: -A INPUT -i eth0 -p tcp -m tcp --sport 53 -j ACCEPT
iptables_list-OUT: -A INPUT -i eth0 -p tcp -m multiport --sports 80,443 -j ACCEPT
iptables_list-OUT: -A INPUT -i eth0 -p tcp -m multiport --dports 22,2376,5900,5901,5902,5903,5904 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables_list-OUT: -A INPUT -i eth0 -p tcp -m multiport --sports 22,2376,5900,5901,5902,5903,5904 -m state --state ESTABLISHED -j ACCEPT
iptables_list-OUT: -A OUTPUT -o lo -j ACCEPT
iptables_list-OUT: -A OUTPUT -o eth0 -m state --state ESTABLISHED -j ACCEPT
iptables_list-OUT: -A OUTPUT -o eth0 -p udp -m udp --dport 53 -j ACCEPT
iptables_list-OUT: -A OUTPUT -o eth0 -p tcp -m tcp --dport 53 -j ACCEPT
iptables_list-OUT: -A OUTPUT -o eth0 -p tcp -m multiport --dports 80,443 -j ACCEPT
iptables_list-OUT: -A OUTPUT -o eth0 -p tcp -m multiport --sports 22,2376,5900,5901,5902,5903,5904 -m state --state ESTABLISHED -j ACCEPT
iptables_list-OUT: -A OUTPUT -o eth0 -p tcp -m multiport --dports 22,2376,5900,5901,5902,5903,5904 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables_list --------------------------

 

Another way to check the rules actual operation, is by using services like Jitsi.

While in a middle of a Jitsi session (connect using VNC to one of the probes) you can click on the left box at the bottom of the page and see details about the connection, such as the actual connection bandwidth, protocol and port.

Here are screenshots from Jitsi from sessions we run using testRTC. In Jitsi no FW.png you can see that the session uses UDP connection and in Jitsi HTTP and HTTPS allowed.png you can see that the session uses HTTPS connection (TCP port 443).

Article Attachments

Was this article helpful?

Related Articles