Linux Netfilter discussions
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: Jong Hian Zin <mail.zin@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Firewall blocking Java applet?
Date: Wed, 22 Jun 2005 21:02:32 -0500	[thread overview]
Message-ID: <200506222102.32991.rob0@gmx.co.uk> (raw)
In-Reply-To: <cb82de59050622183613989c5f@mail.gmail.com>

On Wednesday 22 June 2005 20:36, Jong Hian Zin wrote:
> http://202.188.95.52:8080/speedometer/
>
> The bandwidth test Java applet can be loaded, but unable to start the

Does it work if not going through the OpenWRT?

>   iptables -A INPUT -m state --state INVALID -j DROP
>   iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

You could consolidate these INPUT rules with the ones in FORWARD and 
OUTPUT. I use a chain named "State" which I call from INPUT and 
FORWARD. (I don't do OUTPUT filtering, seems pointless to me.)

>   iptables -A INPUT -p tcp --dport 22 -j ACCEPT

You're DNAT'ing your 22/tcp, so that would hit the FORWARD chain.

>   iptables -A INPUT -j input_rule

These "*_rule" chains do not appear to be used for anything.

> Any idea what is blocking the bandwidth test Java applet?

Not from what you posted. iptables-save(8) would be easier to follow. 
But you can probably troubleshoot this on your own by putting in -j LOG 
rules for -s/-d 202.188.95.52 traffic. Try it and see what you get. Is 
the openwrt capable of normal logging? Or maybe to a remote syslog 
server?
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header


  reply	other threads:[~2005-06-23  2:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23  1:36 Firewall blocking Java applet? Jong Hian Zin
2005-06-23  2:02 ` /dev/rob0 [this message]
2005-06-23  2:31   ` Jong Hian Zin
2005-06-28  2:26     ` Jong Hian Zin

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=200506222102.32991.rob0@gmx.co.uk \
    --to=rob0@gmx.co.uk \
    --cc=mail.zin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox