> I'm wondering why iptables logging and dropping packets
> from the particular src
> wouldn't work.
>
> I'm probably missing something basic here...
>
If you are hoping / trying to capture layer 2/3 data at layer 7 forget it. You
can't. You can install wireshark and capture TCP data to your h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PJ writes:
> Raj Mathur <[EMAIL PROTECTED]> writes:
>>
>> OK, let me rephrase -- even if you can have packets for two different
>> applications arriving on the same TCP port, actually doing so would be
>> going against one of the basic design tene
Raj Mathur <[EMAIL PROTECTED]> writes:
>
> OK, let me rephrase -- even if you can have packets for two different
> applications arriving on the same TCP port, actually doing so would be
> going against one of the basic design tenets of IP (the unique
> address/protocol/port identifier).
>
> I
On Friday 25 Jul 2008, PJ wrote:
> Raj Mathur <[EMAIL PROTECTED]> writes:
> > > How can I set up apache or iptables to log in incoming data
> > > packets while at the same time allow apache to serve web pages?
> >
> > You can't.
>
> I'm wondering why iptables logging and dropping packets from the
>
Raj Mathur <[EMAIL PROTECTED]> writes:
>
> > How can I set up apache or iptables to log in incoming data packets
> > while at the same time allow apache to serve web pages?
>
> You can't.
I'm wondering why iptables logging and dropping packets from the particular src
wouldn't work.
I'm probabl
Ssh tunneling or ssh port forwarding might help.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Sudev Barar
Sent: Wednesday, July 23, 2008 3:55 PM
Subject: [ilugd] Reading TCP packets
This may not be correct place but collective wisdom can perhaps point
On Wednesday 23 Jul 2008, Sudev Barar wrote:
> This may not be correct place but collective wisdom can perhaps point
> me to a good resource.
>
> I have a remote device that is generating data and is sending as a
> TCP packet to designated IP:Port. If I open and set a non standard
> port I am able
On 23/07/2008, Ashish Shukla आशीष शुक्ल <[EMAIL PROTECTED]> wrote:
> In case your service also sends data similar to HTTP requests, then
> you've to figure out some other way.
>
Fortunately not. Let me try this, thanks for pointers and help.
--
Regards,
Sudev Barar
Read http://blog.sudev.in fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sudev Barar writes:
> Thanks for info and pointers. My confusion is that with apache running
> web service on port 80 how will system distinguish between http
> request and tcp packet for listening.
You've two take one of the services (httpd, pop3d,
On 23/07/2008, Ashish Shukla आशीष शुक्ल <[EMAIL PROTECTED]> wrote:
> > I have a remote device that is generating data and is sending as a TCP
> > packet to designated IP:Port. If I open and set a non standard port I
> > am able to receive the packets using a listener. Problem is that the
> > ho
On Wed, Jul 23, 2008 at 3:55 PM, Sudev Barar <[EMAIL PROTECTED]> wrote:
> This may not be correct place but collective wisdom can perhaps point
> me to a good resource.
>
> I have a remote device that is generating data and is sending as a TCP
> packet to designated IP:Port. If I open and set a non
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sudev Barar writes:
> This may not be correct place but collective wisdom can perhaps point
> me to a good resource.
> I have a remote device that is generating data and is sending as a TCP
> packet to designated IP:Port. If I open and set a non stand
12 matches
Mail list logo
