From: Vimal <j.vimal@gmail.com>
To: "Xu, Qiang (FXSGSC)" <Qiang.Xu@fujixerox.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: iptables not prevent access
Date: Tue, 16 Sep 2008 09:22:54 +0530 [thread overview]
Message-ID: <ff71fbf20809152052x163607e4k8bcba0590c997502@mail.gmail.com> (raw)
In-Reply-To: <D8C9BC7FFCF8154FB7141EB8DB609C17217260693A@SGPAPHQ-EXSCC01.dc01.fujixerox.net>
> This is a good idea. I think you are probably right. The request received by the server perhaps does't come from 119 in the server's eyes, although the webpage IS opened from 119. But the server is a linux environment, and tailored quite a bit to run embedded system software. So apache is not in "usr/local". I've got to try to locate the access log in the printer first.
> :-)
I haven't yet read your previous mails about the routing tables. But,
if you could give this a try, then we can confirm the hypothesis.
Just like you blocked client 119 and it failed, and then you tried 120
and it worked; block the gateway and unblock 120. If it works from
120, but it doesn't work from 119 (now), it means that the request is
coming from the gateway for 119.
--
Vimal
next prev parent reply other threads:[~2008-09-16 3:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 7:02 iptables not prevent access Xu, Qiang (FXSGSC)
2008-09-15 7:33 ` Rob Sterenborg
2008-09-15 7:53 ` Xu, Qiang (FXSGSC)
2008-09-15 10:42 ` Vimal
2008-09-15 11:14 ` Xu, Qiang (FXSGSC)
2008-09-15 11:26 ` Simon Gray
2008-09-16 1:36 ` Xu, Qiang (FXSGSC)
2008-09-16 1:49 ` Vimal
2008-09-15 12:06 ` Vimal
2008-09-16 1:56 ` Xu, Qiang (FXSGSC)
[not found] ` <D8C9BC7FFCF8154FB7141EB8DB609C1721726062EC@SGPAPHQ-EXSCC01.dc01.fujixerox.net>
2008-09-15 12:11 ` Vimal
2008-09-16 3:45 ` Xu, Qiang (FXSGSC)
2008-09-16 3:52 ` Vimal [this message]
2008-09-16 4:14 ` Xu, Qiang (FXSGSC)
2008-09-16 7:28 ` Xu, Qiang (FXSGSC)
2008-09-15 10:44 ` Rob Sterenborg
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=ff71fbf20809152052x163607e4k8bcba0590c997502@mail.gmail.com \
--to=j.vimal@gmail.com \
--cc=Qiang.Xu@fujixerox.com \
--cc=netfilter@vger.kernel.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