IETF Logo Mail Archive

Re: [BEHAVE] [v6ops] protocols without need for ALG ?

Mark Smith <markzzzsmith@gmail.com> Fri, 31 July 2015 05:40 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E208D1B3111; Thu, 30 Jul 2015 22:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level:
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0aSi2uqzbCGG; Thu, 30 Jul 2015 22:40:25 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E4851B3118; Thu, 30 Jul 2015 22:40:25 -0700 (PDT)
Received: by igbpg9 with SMTP id pg9so25319171igb.0; Thu, 30 Jul 2015 22:40:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WEvRNGV4XYFlnXfR3WZlJ4xbS4LuvdL7XJ9TOJjdugE=; b=FZp4ZKD08y/4HsTgcYyyP0Fo15c7PP9Re47+6jvrBSpI7DH+m79eR9gXoyhCLNVfqf ffFCXWBQ4MJpVWbeQYsBmss+iNug48KZ+tLgYpFPSG2kCO0QzyTJwoEWubDRQ2AyAcaR CTwoLIDX2BsvhjdFQ3Z6pnTWfv2JnEwJziX72EC5D+Mc3c5IV8CUmFNE3lf4Lm7RXQrW dNtCjjCDuhbx+kpQlWFOSBM2Zaj+ycox7OQMYGTAnd5Z+EYz0A5O80wy6r1vhgLNdZRl fmyBHhbxPi2pNallZaAFvJzlAQ8z7F6288E12QTGxWiUbDXZtaYOjtsF1JhJwJnLOmrB +j8A==
MIME-Version: 1.0
X-Received: by 10.50.88.65 with SMTP id be1mr2474058igb.95.1438321225035; Thu, 30 Jul 2015 22:40:25 -0700 (PDT)
Received: by 10.107.169.143 with HTTP; Thu, 30 Jul 2015 22:40:24 -0700 (PDT)
Received: by 10.107.169.143 with HTTP; Thu, 30 Jul 2015 22:40:24 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1507310706240.11810@uplift.swm.pp.se>
References: <20150730205806.GI1667@cisco.com> <33A0B18B-5C9D-4DC3-9E0B-736D7ECA404F@delong.com> <alpine.DEB.2.02.1507310706240.11810@uplift.swm.pp.se>
Date: Fri, 31 Jul 2015 15:40:24 +1000
Message-ID: <CAO42Z2zH4A71B82TL3=tbagqXU1mbnt4eMDFGmuVa94gAj2-vA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary="089e013d0dd6b0f475051c25414d"
Archived-At: <http://mailarchive.ietf.org/arch/msg/behave/yMO8QQxonT-ve8atQq8DtHnGi_c>
X-Mailman-Approved-At: Fri, 31 Jul 2015 11:16:34 -0700
Cc: Owen DeLong <owen@delong.com>, v6ops list <v6ops@ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] [v6ops] protocols without need for ALG ?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 05:40:27 -0000

On 31 Jul 2015 3:11 pm, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:
>
> On Thu, 30 Jul 2015, Owen DeLong wrote:
>
>>>   SSH/SCP - OK
>>>   syslog  - OK
>>>   TFTP    - OK ?
>>
>>
>> Should be OK, depending on which side is client. (client has to be the
>> private address/translated side of the connection).
>
>
> There are ALGs for TFTP from multiple vendors, and I seem to remember I
had problem performing TFTP download from behind a NAT, but I could be
mistaken. This should be investigated further.
>

I'm pretty sure you'd need an ALG for TFTP over NAT, as the file transfer
itself takes place over unspecified and unpredictable ports. This caused me
some grief in the past when trying to have a TFTP file transfer hold up a
dial on demand link.

Regards,
Mark.

> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email