All of lore.kernel.org
 help / color / mirror / Atom feed
From: Navneet Choudhary <navneetkc@gmail.com>
To: Askar <askarali@gmail.com>
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: Linux as router (Gateway Server)
Date: Sun, 13 Feb 2005 21:36:08 +0530	[thread overview]
Message-ID: <1dceb0120502130806545fe363@mail.gmail.com> (raw)
In-Reply-To: <a0f69e505021200153e017d6c@mail.gmail.com>

> dude add this rule to yur iptables script
> iptables -A INPUT -p tcp -s 0/0 --dport 80 -j ACCEPT

tried this, problem still exists.

> second "squid squid[3720]: Squid Parent: child process 3722
> exited due to signal 6" is not iptables related, better place to check
> is squid mailing list.

Didn't i mentioned in my original mail

"Since, process will NOT die if I disable/flush my rules?"

> You are running squid in interception mode?
so , what

> remember when squid is running in interception packets destined fro
> squid machine not hit FORWARD chain but INPUT. :)

Then, allowing INPUT to port 80 should have worked?
Since, i've already allowed local loopback in my rules.
 
> Note: which version of squid you are using, what cache.log say?
> solution try to upgrade your squid with never version.

squid-2.5.STABLE7  at the time installation latest one.
upgrade? anyperticular strong reason for that?
 
> I hope this will help
> 
> regards
> 
> On Sat, 12 Feb 2005 13:18:25 +0530, Navneet Choudhary
> <navneetkc@gmail.com> wrote:
> > hi list,
> >
> > i require further co-operation from yours side.
> >
> > Squid Server is serving as Proxy server, Gateway & Firewall
> >
> > Problem:
> > Squid daemon dies at startup.
> >
> > Here is log output of  /var/log/messages
> >
> > Feb 12 09:15:25 squid squid[3652]: Squid Parent: child process 3654 started
> > Feb 12 09:15:25 squid (squid): Cannot open HTTP Port
> > Feb 12 09:15:29 squid squid[3720]: Squid Parent: child process 3722
> > exited due to signal 6
> > Feb 12 09:15:32 squid squid[3720]: Squid Parent: child process 4385 started
> > Feb 12 09:15:32 squid squid[3720]: Squid Parent: child process 4385
> > exited with status 1
> > Feb 12 09:15:33 squid (squid): Cannot open HTTP Port
> >
> > Why my iptables rule blocking squid to open HTTP port.
> >
> > Note: existing rule being attached at the end of mail
> >
> > Since, process will not die if I disable/flush my rules?
> >
> > Squid being started from /etc/rc.local
> >
> > Where i am doing mistakes?
> >
> > Please suggest since its causing startup hiccup
> >
> > Thanks & regards,
> >
> > Navneet Choudhary
> >
> > Updates & quick recap
> >
> > 1.> Basically I want clients to be able to :
> >
> >  a). Send and receives mails from mail.ISP.net [X.X.X.160] and
> > sometimes from X.X.X.78
> > Status: Working
> > b). Browse the net through squid [3128]
> > Status: Working
> >
> > c). Use Jabber [??], MSN [1863] and Yahoo [5050]
> > Status: Working
> >
> > d) Down and upload data using ftp from 202.134.192.21 & 221.171.85.41
> >
> > Status: Working
> > e) Down and upload data using SONICMQ [IP & Port?]
> >
> > Status: Require HELP
> > e) Allow SSH connection to this system [eth0].
> > Status: Working
> > f) We can ping/trace route by domain name i.e. ping yahoo.com
> > Status:  Working
> >
> > 2.What i am using?
> >
> > My network configuration is as follows: -
> >
> >           WAN
> >              |
> >           eth1
> >   (172.21.0.133/28)
> >              |
> >              |
> >       Red Hat 9
> > [Squid Proxy, Gateway ,firewall & FTP]
> >              |
> >              |
> >              |
> >     (133.147.0.0/16)
> >            eth0
> >               |
> > ---- SWITCH----------
> >               |
> >               |
> >               |
> >           LAN
> >
> > where:-
> > eth0-Intel Corp. 82557/8/9 [Ethernet Pro 100]
> > eth1-Broadcom Corporation NetXtreme BCM5702 Gigabit Ethernet
> >
> > Kernel 2.4.20-8
> >
> > iptables  v1.2.7a
> >
> > 3.What I have done:-
> >
> > a)Enabled IP forwarding by adding
> > vi  /etc/sysctl.conf
> >
> >  # Controls IP packet forwarding
> > net.ipv4.ip_forward = 1
> >
> > b)Automatic loading of modules by adding
> > vi  /etc/rc.local
> >
> > /sbin/insmod ip_nat_ftp
> > /sbin/insmod ip_conntrack_ftp
> >
> > b)Firewall rules as follows:-
> > # Generated by iptables-save v1.2.7a on Thu Feb 10 20:02:43 2005
> > *mangle
> > :PREROUTING ACCEPT [1308:428675]
> > :INPUT ACCEPT [1308:428675]
> > :FORWARD ACCEPT [0:0]
> > :OUTPUT ACCEPT [1273:553710]
> > :POSTROUTING ACCEPT [1273:553710]
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG
> > FIN,PSH,URG -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG
> > FIN,PSH,URG -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG
> > FIN,PSH,URG -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG
> > FIN,PSH,URG -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
> > -A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
> > COMMIT
> > # Completed on Thu Feb 10 20:02:43 2005
> > # Generated by iptables-save v1.2.7a on Thu Feb 10 20:02:43 2005
> > *nat
> > :PREROUTING ACCEPT [10233:846887]
> > :POSTROUTING ACCEPT [71:4821]
> > :OUTPUT ACCEPT [67:4688]
> > -A POSTROUTING -s 133.147.0.0/255.255.0.0 -o eth1 -j SNAT --to-source
> > 172.21.0.132
> > COMMIT
> > # Completed on Thu Feb 10 20:02:43 2005
> > # Generated by iptables-save v1.2.7a on Thu Feb 10 20:02:43 2005
> > *filter
> > :INPUT DROP [0:0]
> > :FORWARD DROP [0:0]
> > :OUTPUT DROP [0:0]
> > -A INPUT -s 127.0.0.1 -j ACCEPT
> > -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
> > -A INPUT -i eth0 -p tcp -m tcp --sport 1024:65535 --dport 3128
> > --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A INPUT -i eth0 -p tcp -m tcp --sport 1024:65535 --dport 22
> > --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A INPUT -i eth0 -p tcp -m tcp --sport 1024:65535 --dport 21
> > --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A INPUT -i eth0 -p tcp -m tcp --sport 1024:65535 --dport 20
> > --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A INPUT -p udp -j DROP
> > -A INPUT -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j DROP
> > -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
> > -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p udp -m udp --sport 1024:65535 --dport 53 -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p tcp -m tcp --sport 1024:65535 --dport 25
> > --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p tcp -m tcp --sport 1024:65535 --dport
> > 110 --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p tcp -m tcp --sport 1024:65535 --dport 21 -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p tcp -m tcp --sport 1024:65535 --dport 20 -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p tcp -m tcp --sport 1024:65535 --dport
> > 1863 --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A FORWARD -i eth0 -o eth1 -p tcp -m tcp --sport 1024:65535 --dport
> > 5050 --tcp-flags SYN,RST,ACK SYN -j ACCEPT
> > -A FORWARD -p icmp -m icmp --icmp-type 8 -j ACCEPT
> > -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
> > -A OUTPUT -p udp -m udp --sport 1024:65535 --dport 53 -j ACCEPT
> > -A OUTPUT -o eth1 -p tcp -m tcp --sport 1024:65535 --dport 80
> > --tcp-flags SYN,RST,ACK SYN  -m owner --uid-owner squid -j ACCEPT
> > -A OUTPUT -o eth1 -p tcp -m tcp --sport 1024:65535 --dport 443
> > --tcp-flags SYN,RST,ACK SYN -m owner --uid-owner squid -j ACCEPT
> > -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
> > COMMIT
> > # Completed on Thu Feb 10 20:02:43 2005
> >
> >
> 
> --
> I love deadlines. I like the whooshing sound they make as they fly by.
> Douglas Adams
>


  reply	other threads:[~2005-02-13 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1dceb012050211233357e23dd4@mail.gmail.com>
2005-02-12  7:48 ` Fwd: Linux as router (Gateway Server) Navneet Choudhary
2005-02-12  8:15   ` Askar
2005-02-13 16:06     ` Navneet Choudhary [this message]
2005-02-12 14:01   ` Fwd: " Jason Opperisano
2005-02-12 22:02     ` Josh Nerius
2005-02-13  2:13       ` Georgi Alexandrov
2005-02-13  2:33         ` Josh Nerius
2005-02-13 11:55           ` Georgi Alexandrov
2005-02-13 17:34             ` Navneet Choudhary
2005-02-13 17:26           ` Navneet Choudhary
     [not found]           ` <420F4010.7050609@hotpop.com>
2005-02-13 21:38             ` Josh Nerius
2005-02-14 22:15               ` Jason Opperisano
2005-02-15  2:32                 ` Josh Nerius
2005-02-13 17:21         ` Navneet Choudhary
2005-02-13 17:19       ` Navneet Choudhary
2005-02-13 17:04     ` Navneet Choudhary
2005-01-19 14:37 Navneet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1dceb0120502130806545fe363@mail.gmail.com \
    --to=navneetkc@gmail.com \
    --cc=askarali@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.