Tag Info

New answers tagged

0

Almost every access list is by default ended with deny all all. When you enable ufw width any rules to allow some traffic all is in deny state. Status: active To Action From -- ------ ---- 69 ALLOW Anywhere 53 ALLOW Anywhere 22 ...


0

There is a /usr/share/ufw/check-requirements script that checks for everything needed for ufw to work. You'll get hints about what's missing. ufw is not meant to work without the full iptables/netfilter build in the kernel or loaded by modules. If you can't build a new kernel, you're in for some trouble. The post you linked tries to go around these ...


1

Here is an example iptables rule set script for my guess as to what you need / want. I have guessed at some addresses, you will have to edit for what you really need. #!/bin/sh FWVER=0.01 # # Mazzy Example 2015.02.20 Ver:0.01 # Only port 80. echo "Loading Mazzy Example iptables rules set. version $FWVER..\n" # The location of the iptables program # ...


0

In case iptables is not installed or the binary is missing, try installing/re-installing it: sudo apt-get install --reinstall iptables


0

Iptables operates on incoming or outgoing packets by matching the packet against the set of rules of Iptables. It does not have to do anything with whether a port is open or not. If the ssh traffic is blocked via the following rule in iptables, -A INPUT -i eth0 -p tcp --dport 22 -j DROP then when a packet arrives destined for port 22 will be dropped by ...


1

Solution By MadHatter, http://serverfault.com/questions/666696/ubuntu-apache2-cannot-open-port-443/666713?noredirect=1#comment814308_666713 don't know much about ufw, but in this case I think it will be completely ineffective on INPUT traffic, because the rules that implement it come after a blanket DROP (the fifth rule in the INPUT chain). You can see ...


1

Remove the IP Address from NameVirtualHost 92.243.16.14:443 (you practically have binded all VirtualHosts on that IP Address) in order to listen on port 443 on all network interfaces (IPs): NameVirtualHost *:443 Then you can differentiate domain by binding the VirtualHost on a specific IP address like so: VirtualHost 1.2.3.4:443 VirtualHost 1.2.3.5:443 ...


0

Apache is running and port 443 is also open, here you need to check for the IP 92.243.16.14 is configured or not using ifconfig command. because 443 is running on default interface.


1

From what I can tell dnsmasq uses port 53 tcp/udp, as well as port 67/udp dhclient by default uses port 68/udp So a generic way to get this setup would be sudo ufw allow to any port 53 sudo ufw allow to any port 67 proto udp sudo ufw allow to any port 68 proto udp Or if you want to just open these ports for a particular IP address (not sure if you ...


1

in command sudo ssh -gL 80:127.0.0.1:8080 localhost option -g - Allows remote hosts to connect to local forwarded ports option -L - [bind_address:]port:host:hostport Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. This works by allocating a ...


1

You need to use the OUTPUT chain as the packets meant for the loopback interface do not pass via the PREROUTING chain. The following should work: iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8080


1

NAT Table: This table should only be used for NAT (Network Address Translation) on different packets. In other words, it should only be used to translate the packet's source field or destination field. Filter Table: The filter table is mainly used for filtering packets. We can match packets and filter them in whatever way we want. This is the place ...


0

PREROUTING: This chain is used to make any routing related decisions before (PRE) sending any packets. Always remember that in PREROUTING/POSTROUTING i.e. NAT table the ACCEPT/DROP/REJECT etc targets of the default FILTER table will not work. The NAT table is only used for taking routing decisions. You should use PREROUTING when taking any routing decisions ...



Top 50 recent answers are included