New answers tagged ufw
It seems I have solved it. 16.04 was installed over a disk containing an earlier version and for some reason it a) did not remove earlier kernels, and b) did not install the 16.04 4.4 kernel. solution - I deleted all earlier kernels from /boot and all directories referring to modules for earlier kernels, and reinstalled. That got rid of the problem.
Since Ubuntu 14.10, the xrdp package provided by Ubuntu (Ubuntu repositories) allow you to reconnect to the same session. firewall wise, you should only need the port 3389 as the xrdp software is acting as a proxy. When you connect to port 3389, in your xrdp.ini file, you can see that additional connection is done through the ip 127.0.0.1 (itself) We ...
I have the same problem as Mookey but I can confirm that the solution by 2707974 is working for me! Let's see this step by step. If have Gufw set to incomming:deny and outgoing:allow with logging on. Then if I switch VPN on, the first contact to my VPN provider is allowed normally without any rules. When the VPN provider is calling back his call is ...
Command for deny whole 126.96.36.199/8 network is sudo ufw deny from 188.8.131.52/8 when you list rules sudo ufw status you will see To Action From -- ------ ---- ... Anywhere DENY 184.108.40.206/8 This will deny any traffic from ip's witch start with 91.x.x.x But I recommend ...
Check your Iptables, maybe there are some rules that aswell block your VPN connection. iptables -L ACCEPT VPN connections for INPUT aswell to OUTPUT at Iptables. iptables -A INPUT -p tcp --dport 47 -j ACCEPT iptables -A OUTPUT -p tcp --dport 47 -j ACCEPT If VPN connection works, then save rules iptables-save
PPTP vpn user port 47 aka GRE. To allow this traffic edit /etc/ufw/before.rules and add at the end of file sudo nano /etc/ufw/before.rules this # gre -A ufw-before-input -p 47 -j ACCEPT -A ufw-before-output -p 47 -j ACCEPT Then disable, enable ufw sudo ufw disable sudo ufw enable EDIT 1 Rules must placed in /etc/ufw/before.rules before segment # ...
This might not answer your question directly, however... Why not use PFsense or IPfire rather? They can do all you need and more. PFSense Ipfire
Hops (Firewalls) along the route could filter icmp packets in between ping source and ping destination. Use mtr / traceroute instead of ping (or Ping next hop then after next hop...) Ping different destination and see if this works Ping from different source network
Top 50 recent answers are included