Re: Shorewall and MySQL problem - solved
- From: Bit Twister <BitTwister@xxxxxxxxxxxxxxxx>
- Date: Sun, 11 Feb 2007 12:07:10 -0600
On Sun, 11 Feb 2007 19:41:58 +0200, tj wrote:
Here are the lines I added that solved this problem (First shorewall and
last mysql):
rules
-----
ACCEPT net:[ip,ip,ip] fw all
Well, now the system accepts any connection besides mysql for ip,ip,ip
It is a solution for mysql, but your server is now more at risk from
[ip,ip,ip]
When your server is cracked from [ip,ip,ip] and used to attack other
systems, YOU are to blame for not setting a tighter rule.
Do take just a minute to read the /troubleshooting/ link found at
http://www.shorewall.net/Documentation_Index.html
/Connection Problems/ is where I would like to see the minute spent.
interface
---------
net eth0 detect dhcp
Now you can add some net options and get a tighter wall. I'll suggest
routefilter,tcpflags
shorewall.conf
--------------
Did you look in that file to see where your shorewall log messages are sent.
ps. Thanks to BiTwster for the advice and for kicking my arse for being
rude...
Anytime. 8-)
.
- Follow-Ups:
- References:
- Shorewall and MySQL problem
- From: tj
- Re: Shorewall and MySQL problem - solved
- From: tj
- Shorewall and MySQL problem
- Prev by Date: Re: Shorewall and MySQL problem - solved
- Next by Date: Re: Shorewall and MySQL problem - solved
- Previous by thread: Re: Shorewall and MySQL problem - solved
- Next by thread: Re: Shorewall and MySQL problem - solved
- Index(es):
Relevant Pages
|