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: Mon, 15 Sep 2008 17:41:53 +0530 [thread overview]
Message-ID: <ff71fbf20809150511g6db0b772o9ebf7fdf54325dac@mail.gmail.com> (raw)
In-Reply-To: <D8C9BC7FFCF8154FB7141EB8DB609C1721726062EC@SGPAPHQ-EXSCC01.dc01.fujixerox.net>
[Screenshots]
Looks like nothing is wrong.
Another possibility is that your gateway's netmask isn't defined properly.
When you want to contact the server, the client issues an ARP request
to find out the Mac address of the destination, since the destination
is on the same network as the client (source). It is quite possible
that the gateway's netmask (something other than 255.255.255.0) makes
it respond to this ARP, thinking that it should route this packet to
the destination.
In fact, try this one too:
* From the client, access the webpage
* From the server, check the access logs, and see which IP had
accessed the particular webpage you did in the previous step.
The two should be equal.
But, what continues to baffle me is the fact that no requests were
coming from your client's ethernet interface!
--
Vimal
next prev parent reply other threads:[~2008-09-15 12:11 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 [this message]
2008-09-16 3:45 ` Xu, Qiang (FXSGSC)
2008-09-16 3:52 ` Vimal
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=ff71fbf20809150511g6db0b772o9ebf7fdf54325dac@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