Message from discussion
https problem one server, two url, two ip addresses (eth0 and eth0:0)
Received: by 10.66.87.73 with SMTP id v9mr6370731paz.46.1351776293919;
Thu, 01 Nov 2012 06:24:53 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.68.201.133 with SMTP id ka5ls10212812pbc.3.gmail; Thu, 01 Nov
2012 06:24:42 -0700 (PDT)
Received: by 10.66.77.131 with SMTP id s3mr13215824paw.24.1351776282851;
Thu, 01 Nov 2012 06:24:42 -0700 (PDT)
Received: by 10.66.77.131 with SMTP id s3mr13215823paw.24.1351776282842;
Thu, 01 Nov 2012 06:24:42 -0700 (PDT)
Return-Path: <i...@bnoordhuis.nl>
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48])
by gmr-mx.google.com with ESMTPS id uz6si1598826pbc.0.2012.11.01.06.24.42
(version=TLSv1/SSLv3 cipher=OTHER);
Thu, 01 Nov 2012 06:24:42 -0700 (PDT)
Received-SPF: pass (google.com: domain of i...@bnoordhuis.nl designates 209.85.160.48 as permitted sender) client-ip=209.85.160.48;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of i...@bnoordhuis.nl designates 209.85.160.48 as permitted sender) smtp.mail=i...@bnoordhuis.nl
Received: by mail-pb0-f48.google.com with SMTP id wy7so1544365pbc.7
for <nodejs@googlegroups.com>; Thu, 01 Nov 2012 06:24:42 -0700 (PDT)
d=google.com; s=20120113;
h=mime-version:x-originating-ip:in-reply-to:references:date
:message-id:subject:from:to:content-type:x-gm-message-state;
bh=/cblI92vqGs1VEtZDE0m53kzOsDW76CzckCo7xvAC+Q=;
b=Dj+88300bx5aK8OivPAZRoNnrDaiSey1JjirYGtTwiyga7+fZ1K/cyqCvF13TeyGi1
M3cTLEC4RQUw0k7vT6fcAI69TmsNSnnJSxbvq89yZDYW2lzGqlPhIpI+P9k708WSfNP6
3qhU0tHtu6YdT5B4eOy4QRnvgncRCEvCFRaOJM0SZ2iG01wGMkJdszeJjHYWWmYJaNvO
1ClR2AvC9aI2DumeyvfNDK8DncHSJfiJI9Ex0gKSOhHdynO6dY/zAKd3QW2koeZx/o7v
ppiS1KCCZOuMmD2GVLO54jwfM07j7CmBCpzcbToh3xmS8JRTZX2CBrEXFmWO8FUrywXV
Yb8Q==
MIME-Version: 1.0
Received: by 10.68.248.70 with SMTP id yk6mr121733837pbc.160.1351776281951;
Thu, 01 Nov 2012 06:24:41 -0700 (PDT)
Received: by 10.68.51.42 with HTTP; Thu, 1 Nov 2012 06:24:41 -0700 (PDT)
X-Originating-IP: [87.214.96.125]
In-Reply-To: <3a650e67-802c-4dab-a3ee-2e99985da926@googlegroups.com>
References: <09b0649c-0bfc-4baf-8008-e780c0ba7909@googlegroups.com>
<CAHQurc9vfap54Y-4SkyNRH97ZEDx_dn=ue8DeO76=coibRk...@mail.gmail.com>
<ad143126-00c8-4f96-ab5e-d36aa930be43@googlegroups.com>
<dcb87647-e7f5-436c-ac83-ea84c17eeb75@googlegroups.com>
<f54ddf11-6da3-4c9f-85e6-a6dd2aae8c2b@googlegroups.com>
<CAHQurc-2fYTAcYi4W_zTChqvVfmsw=j+PKEMariq7Vy85EY...@mail.gmail.com>
<59dddb43-066b-4848-b89a-782244e90a1a@googlegroups.com>
<3a650e67-802c-4dab-a3ee-2e99985da926@googlegroups.com>
Date: Thu, 1 Nov 2012 14:24:41 +0100
Message-ID: <CAHQurc-if65BNbuHbn1pb4QKk1NvqdrzrrHPyhfoyGs7wJC...@mail.gmail.com>
Subject: Re: [nodejs] https problem one server, two url, two ip addresses
(eth0 and eth0:0)
From: Ben Noordhuis <i...@bnoordhuis.nl>
To: nodejs@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQl4ckipc/+d1SC1Lm2vf1nZDy6FKxVdSW5eGgMgPamoJ67QmtW27x6K6cPl/4SQNB0ap2J5
On Thu, Nov 1, 2012 at 11:37 AM, Karl <klru...@gmail.com> wrote:
> I made filtered version with tcpdump/wireshark of the relevant packages
> like so: ip.addr == xx.xxx.xx.39 and tcp and ! tcp.port eq 22
> should I dump that here on the list or mail it? sort of long
The blob you posted doesn't show anything obviously wrong, there's
traffic going to port 3445. I didn't see any traffic to port 443 but
maybe you don't log from the REDIRECT rule.
One potential pitfall is that iptables doesn't support virtual
interfaces: you have eth0 and eth0:0 but iptables only sees eth0.
Then again, you're matching on destination address and port so I guess
it shouldn't matter.
tl;dr I don't know either. :-)