All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mdpeters" <michael.peters@lazarusalliance.com>
To: Daniel Chemko <dchemko@smgtec.com>,
	Jason Opperisano <opie@817west.com>,
	netfilter@lists.netfilter.org
Subject: Re: transparent bridge troubles?
Date: Fri, 7 Jan 2005 17:01:47 -0500	[thread overview]
Message-ID: <005101c4f504$7be50f20$3e0010ac@esonet18> (raw)
In-Reply-To: 7C9884991ADAE0479C14F10C858BCDF591E3AC@alderaan.smgtec.com

Both host and target have no information about the bridge | firewall in the 
middle.


----- Original Message ----- 
From: "Daniel Chemko" <dchemko@smgtec.com>
To: "mdpeters" <michael.peters@lazarusalliance.com>; "Jason Opperisano" 
<opie@817west.com>; <netfilter@lists.netfilter.org>
Sent: Friday, January 07, 2005 4:38 PM
Subject: RE: transparent bridge troubles?


mdpeters wrote:
> Du'oh!
>
> I changed it and this is what I see so far. I'm running a Nessus scan
> on one side of the bridge and the target system is at the other side
> of the bridge.
>
> PRE QUEUEIN=safetynet0 OUT=safetynet0 PHYSIN=eth2 PHYSOUT=eth1
> SRC=68.16.185.132 DST=68.16.185.130 LEN=41 TOS=0x00 PREC=0x00 TTL=64
> ID=3072 PROTO=TCP SPT=3133 DPT=45495 WINDOW=2048 RES=0x00 ACK URGP=0
>
> POST QUEUEIN=safetynet0 OUT=safetynet0 PHYSIN=eth2 PHYSOUT=eth1
> SRC=68.16.185.132 DST=68.16.185.130 LEN=41 TOS=0x00 PREC=0x00 TTL=64
> ID=3072 PROTO=TCP SPT=3133 DPT=45495 WINDOW=2048 RES=0x00 ACK URGP=0

Ok, since there was no return traffic, I'm assuming that the destination
host doesn't know the firewall's in between the two PC's. In
68.16.185.130's arp table, does it have 68.16.185.132 mapped to your
firewall's eth1 interface? Is proxyARPing setup on both firewall
interfaces? This is leaving my knowledge realm, so if someone else can
help..




  reply	other threads:[~2005-01-07 22:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 21:38 transparent bridge troubles? Daniel Chemko
2005-01-07 22:01 ` mdpeters [this message]
2005-01-07 22:18   ` Jason Opperisano
2005-01-08  0:40     ` mdpeters
2005-01-08  2:00       ` Jason Opperisano
2005-01-08  3:53         ` mdpeters
2005-01-08  4:15           ` Jason Opperisano
2005-01-08 12:12             ` mdpeters
  -- strict thread matches above, loose matches on Subject: below --
2005-01-07 20:42 Daniel Chemko
2005-01-07 20:44 ` Jason Opperisano
2005-01-07 20:55   ` mdpeters
2005-01-07 21:01     ` Jason Opperisano
2005-01-07 21:16       ` mdpeters
2005-01-07 21:35       ` mdpeters
2005-01-07 20:24 Daniel Chemko
2005-01-07 20:36 ` mdpeters
2005-01-07 20:14 mdpeters
2005-01-07 18:53 mdpeters
2005-01-07 19:44 ` Jason Opperisano
2005-01-07 21:53 ` Jason Opperisano
2005-01-07 22:02   ` mdpeters

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='005101c4f504$7be50f20$3e0010ac@esonet18' \
    --to=michael.peters@lazarusalliance.com \
    --cc=dchemko@smgtec.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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.