public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: John Buswell <johnb@linuxcast.org>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: netfilter + 2.4.0-test10 causes connect:invalid argument
Date: Sun, 31 Dec 2000 16:06:16 -0800	[thread overview]
Message-ID: <3A4FC9F8.F6036182@linux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012272311290.22827-100000@bloatfish.opaquenetworks.net> <20001231192213.C3307@coruscant.gnumonks.org>

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Harald Welte wrote:

> On Wed, Dec 27, 2000 at 11:12:18PM -0500, John Buswell wrote:
> > 1. running 2.4.0-test10 with netfilter/iptables 1.1.2 ping/telnet gives
> > you invalid argument when connecting to ports on local interfaces.
>
> This is a _very_ strange problem. Nobody has erver reported this behaviour
> to us (the netfilter developers).
>
> I've never heared about it and never encountered it by myself. Sounds like
> it is a configuration issue.

Is dev lo up and running?

-d


[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 274 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;;;;;
version:2.1
email;internet:david@blue-labs.org
title:Blue Labs Developer
note;quoted-printable:GPG key: http://www.blue-labs.org/david@nifty.key=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard

      parent reply	other threads:[~2001-01-01  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28  4:12 PROBLEM: netfilter + 2.4.0-test10 causes connect:invalid argument John Buswell
2000-12-31 18:22 ` Harald Welte
2000-12-31 22:34   ` Justin
2001-01-01  0:06   ` David Ford [this message]

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=3A4FC9F8.F6036182@linux.com \
    --to=david@linux.com \
    --cc=johnb@linuxcast.org \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@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