IP Tables port blocking

I am trying to block all connections to the MySQL port 3306 on our server besides connections from one IP address.  I managed to black all the traffic using the rule below through webmin on our server

Reject If protocol is TCP and destination port is 3306

I've also added the rule

Accept If protocol is TCP and source is 88.208.221.101 and destination port is 3306

However no matter which rule is first in the list it will not allow the specified server to connect.
albyhAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BlazCommented:
The rules should work if the rule "... and source is 88.208.221.101 ..." is first in the list. Did you restart iptables after changing rule order?

Otherwise you could try with a single rule:
Reject If protocol is TCP and source is not 88.208.221.101 and destination port is 3306
0
albyhAuthor Commented:
Yes i restarted the IP tables and it made no difference.

I've just tried setting up the rule

Reject If protocol is TCP and source is not 88.208.221.101 and destination port is 3306

but unfortunately that doesnt work either
0
BlazCommented:
Could you post all your current rules?

Either from webmin interface (a copy/paste or screenshot) or better in terminal issue command:
/sbin/iptables -L -nvx
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

albyhAuthor Commented:
Chain INPUT (policy ACCEPT 121 packets, 11462 bytes)
    pkts      bytes target     prot opt in     out     source               destination        
     121    11462 PORTSEN    all  --  *      *       0.0.0.0/0            0.0.0.0/0          
       0        0 ACCEPT     tcp  --  *      *       88.208.221.101       0.0.0.0/0           tcp dpt:3306
       0        0 REJECT     tcp  --  *      *      !88.208.221.101       0.0.0.0/0           tcp dpt:3306 reject-with icmp-port-unreachable

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Chain OUTPUT (policy ACCEPT 153 packets, 138487 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Chain PORTSEN (1 references)
    pkts      bytes target     prot opt in     out     source               destination        
       0        0 DROP       all  --  *      *       59.56.111.79         0.0.0.0/0          
       0        0 LOG        all  --  *      *       59.56.111.79         0.0.0.0/0           LOG flags 0 level 4 prefix `portsentry attack alert'
       0        0 DROP       all  --  *      *       205.209.161.228      0.0.0.0/0          
       0        0 LOG        all  --  *      *       205.209.161.228      0.0.0.0/0           LOG flags 0 level 4 prefix `portsentry attack alert'
0
BlazCommented:
By the look of the counters it seems that all the packets were accepted by the firewall

121    11462 PORTSEN    all  --  *      *       0.0.0.0/0            0.0.0.0/0          

121 packets (and 11462 bytes) were received by INPUT chain for processing.

Chain INPUT (policy ACCEPT 121 packets, 11462 bytes)

121 packets (11462 bytes) were ACCEPTED by the INPUT chain rules.

However if you did try to initiate a connection to port 3306 (after last change of rules) it is very strange that rules:
0        0 ACCEPT     tcp  --  *      *       88.208.221.101       0.0.0.0/0           tcp dpt:3306
0        0 REJECT     tcp  --  *      *      !88.208.221.101       0.0.0.0/0           tcp dpt:3306 reject-with icmp-port-unreachable

have counts of 0 - no packet matched those rules.

Try to initiate a mySQL connection and see if these counters grow.
0
albyhAuthor Commented:
Chain INPUT (policy ACCEPT 1022 packets, 97820 bytes)
    pkts      bytes target     prot opt in     out     source               destination        
    1025    98000 PORTSEN    all  --  *      *       0.0.0.0/0            0.0.0.0/0          
       0        0 ACCEPT     tcp  --  *      *       88.208.221.101       0.0.0.0/0           tcp dpt:3306
       3      180 REJECT     tcp  --  *      *      !88.208.221.101       0.0.0.0/0           tcp dpt:3306 reject-with icmp-port-unreachable

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Chain OUTPUT (policy ACCEPT 1300 packets, 1391507 bytes)
    pkts      bytes target     prot opt in     out     source               destination        

Chain PORTSEN (1 references)
    pkts      bytes target     prot opt in     out     source               destination        
       0        0 DROP       all  --  *      *       59.56.111.79         0.0.0.0/0          
       0        0 LOG        all  --  *      *       59.56.111.79         0.0.0.0/0           LOG flags 0 level 4 prefix `portsentry attack alert'
       0        0 DROP       all  --  *      *       205.209.161.228      0.0.0.0/0          
       0        0 LOG        all  --  *      *       205.209.161.228      0.0.0.0/0           LOG flags 0 level 4 prefix `portsentry attack alert'
0
BlazCommented:
OK. Now the counters are nonzero:
0        0 ACCEPT     tcp  --  *      *       88.208.221.101       0.0.0.0/0           tcp dpt:3306
3      180 REJECT     tcp  --  *      *      !88.208.221.101       0.0.0.0/0           tcp dpt:3306 reject-with icmp-port-unreachable

3 packets were recived for port 3306 and were rejected since they did not come from IP 88.208.221.101.

Did you try from this IP (which should work) or did you test from some other IP? Is the IP written correctly?
0
albyhAuthor Commented:
They were requests from a script on that server (88.208.221.101), the IP is definately correct.
0
BlazCommented:
Perhaps there is some kind of NAT between the servers?

Try to LOG the packets to see what IP the request comes from:
Run chain LOG If protocol is TCP and destination port is 3306

Put this rule on top of other rules. Then (after trying the connection from 88.208.221.101) check log /var/log/messages for iptables entries. Post the relevant entries here - the entries are in the form:
Jul  1 6:14:13 servername kernel: IN=eth0 OUT= MAC= SRC=88.208.221.101 DST=88.208.221.154 LEN=233 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=50234 DPT=3306 LEN=213

0
albyhAuthor Commented:
I've checked the log /var/log/messages its logged the IP table changes but how do I get it to log the port request?
0
arnoldCommented:
Did you configure mysql to accept connection from the remote host as well.
You can run strace on the mysql process to see if it sees a connection request.

If I am not mistaken, the 3 packets were rejected.
Try using the source as 88.208.221.101/32 in the accept rule.
0
albyhAuthor Commented:
Yeah if the rules are set to accept then the mysql requests comes through no problem.

I've just tried adding the /32 but unfortunately that hasnt worked either :-(
0
arnoldCommented:
Could you once again post the output of iptables -L
If you have a local web server, access it from the system with Ip 88.208.221.101 and see what IP is reflected in the web server's log for the access.
Look at the netstat -rn on the 88.208.221.101 system.  It might have two network interfaces and instead of taking the 88.208.221.x path it is taking the other path altering the source IP.
0
BlazCommented:
> I've checked the log /var/log/messages
> its logged the IP table changes but how
> do I get it to log the port request?

If you add the rule:
Run chain LOG If protocol is TCP and destination port is 3306

You should get a packet log in messages file - for every attempt of connection. The log entry should be like:
Jul  1 6:14:13 servername kernel: IN=eth0 OUT= MAC= SRC=88.208.221.101 DST=88.208.221.154 LEN=233 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=50234 DPT=3306 LEN=213

Post the lines from the log here. And please post again iptables rules for us to see if the logging rule is there:
iptables -L -nvx
and:
iptables -t nat -L -nvx

PS: Maybe there is a more oficial syntax for logging packets in webmin, but I found suggestions that the posted rule should work.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
albyhAuthor Commented:
The problem was sorted by a server engineer.

Thanks for your help guys
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.