well, by that i meant getting a 2nd NIC + a 2nd firewall.
then i can use the 2nd firewall with another public ip, and forward all its traffic to 192.168.123.10.
you're saying its better to have iptables alone installed, just on the server?
why not have a firewall as an extra measurement of security....lets say that someone somehow breaks into the firewall and gets past its rules/filters....well, guess what, now they have another thing to break into...
i don't friggin believe this.
took me 2 weeks to figure out ONE line of code that was causing this issue.
all downloads were being forced to be transferred at the speed of 5megs/sec.
i'm soooo dumb.
lol, i know what iptables is. also, infact, i'm using it on the firewall as well.
unless i misunderstood what you said...there is no way that i'm connecting my server to the world without the firewall in the middle.
LOL
after reading that over and over, i still don't understand what you meant.
also, i don't have a router....during this thread, my router was my firewall...thats why i was saying that my "router" can only push through 1 ip.
here my setup.
world > switch > firewall > server.
i don't know much about mail and stuff but i've been having the same issue and i've learned a few things within the past week or so..
do you have whm/cpanel installed?
if so, go under whm, Tweak Settings, mail and find where it says:
"Track the origin of messages sent though the mail server...
no big man, its all good.
i havn't told the story completely as it ACTUALLY is either because i thought that it would make it more confusing.
so here is the deal:
i have about 5 static ips but i'm only using one of them. the one that i'm using goes INTO a HARDWARE firewall, and then the...
well, they are both the exact same type of nic....so i highly doubt that THATS the problem.
besides, i'm not near the server right now so i wouldn't be able to try that.
HAHAHA...appreciate the help guys
here is what you asked for:
# Logging:
# The home of the dedicated SSL protocol logfile. Errors are
# additionally duplicated in the general error log file. Put
# this somewhere where it cannot be used for symlink attacks on
# a real server (i.e...
in other words, apache is not detecting any 192.168.123.10 connections because there isn't anything being sent/forwarded to that ip. everything is going to "192.168.123.5".
haha, if you're thinking what i think you're thinking, then yes, you're right...(sorry for the confusing sentence :)
but just to make sure..
the router, is forwarding ALL port 80 and port 443 traffic to 192.168.123.5....its NOT and CANNOT forward anything to 192.168.123.10
and i don't know if...
ahhh man, i found out what the problem is and i was hoping that it wouldn't be thing. unless i did something wrong, ip addressing isn't for me.
so, what i did was basically..
with all NEW apache configuration for BOTH ips still in place, instead of forwading port 80 & 443 traffic to...
lol, i'm the same, everyone always think that i'm serious when really its just a joke...
you mentioned "eth0:0 and eth0:1" serveral times....i have eth0 and eth0:1.....that doesn't make a difference, does it?
and i did what you said..it doesnt work.
here is another thing i did, and the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.