http_port 192.168.0.67:3128 transparent
iptables -t nat -A PREROUTING -i eth1 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 3128
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
/sbin/iptables -t nat -L
lambda wrote:iptables is not a service. stop calling it that!
wow, not only don't you understand what a "service" is, you don't even know what a "daemon" is. how'd you get so far without learning that?x2oxen wrote:What would you like to call it a Daemon?
tell me, ox, if it's a service (or a daemon, whatever you prefer), what process runs continuously when you use iptables?ok it is not a service then in RHEL why we say
# service iptables start/stop/restart
is there any difference between Daemon/Service ????
who cares what rhel/rhce/fedora say about linux? redhat is not the only linux distribution out there! i don't need to consult any "books" because i've used linux and unix since before redhat existed as a company! you know NOTHING!You need to consult your RHCE books again about which am sure you are not certified!
you are incorrect. /sbin/iptables is not a daemon. when you set some rules using iptables, and then you run "ps auxww", do you see iptables running in the background?mudasir wrote:To clear somethings up..
iptables ---> is the service
/sbin/iptables ---> is the deamon.
who cares what rhel/rhce/fedora say about linux? redhat is not the only linux distribution out there! i don't need to consult any "books" because i've used linux and unix since before redhat existed as a company! you know NOTHING!
tell me, ox, if it's a service (or a daemon, whatever you prefer), what process runs continuously when you use iptables?
why don't you come out and actually define what a daemon (or service) is on linux? can you do that? no, you CAN'T.
as if squid on rhel is any different from squid on any other distribution. irrelevant!x2oxen wrote:I think you should know 1st we are discussing about RHEL squid issue here but not any other distribution.
again with the stupid redhat definitions. just because redhat considers anything you start or stop using the "service" command a service doesn't mean it's actually a service. you can run "service ntpdate start" but there is no ntpdate service, just like there's no iptables service. you could also run "/etc/init.d/ntpdate start", because that's all that "service ntpdate start" does -- would you still claim it's a service? (knowing your lack of a logical approach to problems, probably yes.)In edition for your information Red Hat is calling iptables a SERVICE
as per my signature, you're not worth arguing with any more.Who cares you mind that
Users browsing this forum: No registered users and 0 guests