On 3 June 2013 13:32, Marek Marczykowski
Yes this should be the reason. I had have this problem before, but
wasn't able to reproduce it...
Then this problem has not occured for a long time and just forget about it...
You can check it inside your net/firewall vm:
WiFi:~/ $ sudo iptables -L -n -t nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
PR-QBS all --
0.0.0.0/0 0.0.0.0/0
PR-QBS-SERVICES all --
0.0.0.0/0 0.0.0.0/0
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
ACCEPT all --
0.0.0.0/0 0.0.0.0/0
ACCEPT all --
0.0.0.0/0 0.0.0.0/0
MASQUERADE all --
0.0.0.0/0 0.0.0.0/0
^^^^^^^^^^^^^^^^^^^^^
--
Zrubi