From owner-freebsd-net@FreeBSD.ORG Sun Apr 6 06:12:49 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C156737B401; Sun, 6 Apr 2003 06:12:49 -0700 (PDT) Received: from grosbein.pp.ru (www2.svzserv.kemerovo.su [213.184.65.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5544643F85; Sun, 6 Apr 2003 06:12:46 -0700 (PDT) (envelope-from eugen@grosbein.pp.ru) Received: from grosbein.pp.ru (smmsp@localhost [127.0.0.1]) by grosbein.pp.ru (8.12.7/8.12.7) with ESMTP id h36DCee1086636; Sun, 6 Apr 2003 21:12:40 +0800 (KRAST) (envelope-from eugen@grosbein.pp.ru) Received: (from eugen@localhost) by grosbein.pp.ru (8.12.7/8.12.7/Submit) id h36DC4pg086609; Sun, 6 Apr 2003 21:12:04 +0800 (KRAST) Date: Sun, 6 Apr 2003 21:12:04 +0800 From: Eugene Grosbein To: bug-followup@freebsd.org Message-ID: <20030406211204.A509@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i cc: peter@freebsd.org cc: net@freebsd.org Subject: Re: bin/45760: pppd(8) incoreectly handles timeouts after long run [PATCH] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Apr 2003 13:12:50 -0000 Hi! I've found the source of this behavour. pppd 2.3.5 violates RFC1548, section 5.8 that states: Echo-Request and Echo-Reply packets may only be sent in the LCP Opened state. Echo-Request and Echo-Reply packets received in any state other than the LCP Opened state SHOULD be silently discarded. pppd 2.3.5 will schedule one extra LCP Echo for each incident when it detects via LCP Echos that peer has disconnected. So my the solution was to patch lcp.c: --- usr.sbin/pppd/lcp.c.orig Sun Apr 6 21:05:21 2003 +++ usr.sbin/pppd/lcp.c Sun Apr 6 21:05:36 2003 @@ -1737,6 +1737,8 @@ fsm *f; { LcpSendEchoRequest (f); + if (f->state != OPENED) + return; /* * Start the timer for the next interval. I've checked pppd 2.4.1 and found that it contains exactly this code. Please apply the patch. Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Sun Apr 6 13:41:33 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E34037B401 for ; Sun, 6 Apr 2003 13:41:33 -0700 (PDT) Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D479D43FAF for ; Sun, 6 Apr 2003 13:41:32 -0700 (PDT) (envelope-from hsu@FreeBSD.org) Received: from FreeBSD.org (adsl-63-193-112-125.dsl.snfc21.pacbell.net [63.193.112.125])h36KfVHo005994; Sun, 6 Apr 2003 13:41:31 -0700 (PDT) Message-Id: <200304062041.h36KfVHo005994@mta7.pltn13.pbi.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= In-Reply-To: Message from JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Apr 2003 13:44:00 -0700 From: Jeffrey Hsu cc: Craig Boston cc: net@FreeBSD.org Subject: Re: IPv6 MTU bug? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Apr 2003 20:41:33 -0000 > Yes, this is a bug of the IPv6 code, and has been fixed in KAME > snapshots. The fix should eventually be merged to the freebsd > repository, but I'm not a committer and thus cannot tell when. > > JINMEI, Tatuya If you make a patch relative to -current, I'd be glad to commit it for you. Jeffrey From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 11:02:17 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7698937B404 for ; Mon, 7 Apr 2003 11:02:17 -0700 (PDT) Received: from yama.openaccess.org (ns1.openaccess.org [216.57.214.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9596043FBF for ; Mon, 7 Apr 2003 11:02:14 -0700 (PDT) (envelope-from michael@staff.openaccess.org) Received: from [192.168.1.2] (mfdAP.bcs.openaccess.org [216.57.214.35]) by yama.openaccess.org (8.12.3/8.11.6) with ESMTP id h37HfXr9077061 for ; Mon, 7 Apr 2003 10:41:33 -0700 (PDT) (envelope-from michael@staff.openaccess.org) User-Agent: Microsoft-Entourage/10.0.0.1309 Date: Mon, 07 Apr 2003 11:01:54 -0700 From: Michael DeMan To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 18:02:17 -0000 Hi All, Is there a way to do secure syslog, via SSH or something? We have wireless routers we need to syslog to a central server and are concerned about sniffing/spoofing. - mike Michael F. DeMan Director of Technology OpenAccess Internet Services 1305 11th St., 3rd Floor Bellingham, WA 98225 Tel 360-647-0785 x204 Fax 360-738-9785 michael@staff.openaccess.org From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 11:05:14 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0271637B401 for ; Mon, 7 Apr 2003 11:05:14 -0700 (PDT) Received: from laptop.tenebras.com (laptop.tenebras.com [66.92.188.18]) by mx1.FreeBSD.org (Postfix) with SMTP id 79BAB43FB1 for ; Mon, 7 Apr 2003 11:05:13 -0700 (PDT) (envelope-from kudzu@tenebras.com) Received: (qmail 79063 invoked from network); 7 Apr 2003 18:05:10 -0000 Received: from sapphire.tenebras.com (HELO tenebras.com) (192.168.188.241) by 0 with SMTP; 7 Apr 2003 18:05:10 -0000 Message-ID: <3E91BDD5.4070509@tenebras.com> Date: Mon, 07 Apr 2003 11:05:09 -0700 From: Michael Sierchio User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael DeMan References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 18:05:14 -0000 Michael DeMan wrote: > Hi All, > > Is there a way to do secure syslog, via SSH or something? > > We have wireless routers we need to syslog to a central server and are > concerned about sniffing/spoofing. IPSec? SKIP? From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 11:14:44 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95BED37B401 for ; Mon, 7 Apr 2003 11:14:44 -0700 (PDT) Received: from yama.openaccess.org (ns1.openaccess.org [216.57.214.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A61B43F3F for ; Mon, 7 Apr 2003 11:14:44 -0700 (PDT) (envelope-from michael@staff.openaccess.org) Received: from [192.168.1.2] (mfdAP.bcs.openaccess.org [216.57.214.35]) by yama.openaccess.org (8.12.3/8.11.6) with ESMTP id h37Hs0r9077237; Mon, 7 Apr 2003 10:54:03 -0700 (PDT) (envelope-from michael@staff.openaccess.org) User-Agent: Microsoft-Entourage/10.0.0.1309 Date: Mon, 07 Apr 2003 11:14:24 -0700 From: Michael DeMan To: Michael Sierchio Message-ID: In-Reply-To: <3E91BDD5.4070509@tenebras.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 18:14:45 -0000 Yes, those would work except I'd rather not set up another VPN just for syslog. Too many units. On 4/7/03 11:05 AM, "Michael Sierchio" wrote: > Michael DeMan wrote: >> Hi All, >> >> Is there a way to do secure syslog, via SSH or something? >> >> We have wireless routers we need to syslog to a central server and are >> concerned about sniffing/spoofing. > > IPSec? > SKIP? > > Michael F. DeMan Director of Technology OpenAccess Internet Services 1305 11th St., 3rd Floor Bellingham, WA 98225 Tel 360-647-0785 x204 Fax 360-738-9785 michael@staff.openaccess.org From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 11:21:24 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC7637B405 for ; Mon, 7 Apr 2003 11:21:24 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB02F43FDD for ; Mon, 7 Apr 2003 11:21:22 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.9/8.11.6) with SMTP id h37ILLxs031932; Mon, 7 Apr 2003 20:21:21 +0200 Received: (nullmailer pid 99144 invoked by uid 1000); Mon, 07 Apr 2003 18:21:19 -0000 Date: Mon, 7 Apr 2003 20:21:19 +0200 From: Mark Santcroos To: Michael DeMan Message-ID: <20030407182119.GB744@laptop.6bone.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Handles: MS6-6BONE, MS18417-RIPE cc: freebsd-net@freebsd.org Subject: Re: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 18:21:24 -0000 On Mon, Apr 07, 2003 at 11:01:54AM -0700, Michael DeMan wrote: > Is there a way to do secure syslog, via SSH or something? You can do it indeed using ssh port forwarding. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 11:29:14 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E21D37B401 for ; Mon, 7 Apr 2003 11:29:14 -0700 (PDT) Received: from balin.ap.univie.ac.at (balin.ap.univie.ac.at [131.130.11.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C4A043F3F for ; Mon, 7 Apr 2003 11:29:13 -0700 (PDT) (envelope-from ulrich.kiermayr@univie.ac.at) Received: from univie.ac.at (localhost [127.0.0.1])h37ITD3C1296796; Mon, 7 Apr 2003 20:29:13 +0200 (CEST) Message-ID: <3E91C376.9090309@univie.ac.at> Date: Mon, 07 Apr 2003 20:29:10 +0200 From: Ulrich Kiermayr Organization: Vienna University Computer Center User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313 X-Accept-Language: en-us, en, de-at MIME-Version: 1.0 To: Michael DeMan References: In-Reply-To: X-Enigmail-Version: 0.74.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 18:29:14 -0000 Hi Michael, > Hi All, > > Is there a way to do secure syslog, via SSH or something? > > We have wireless routers we need to syslog to a central server and are > concerned about sniffing/spoofing. I use syslog-ng (to remote-log over tcp) and stunnel for encryption. lG uk -- ------------------------------------------------------------------------ Ulrich Kiermayr Zentraler Informatikdienst der Universitaet Wien Network Security Universitaetsstrasse 7, 1010 Wien, Austria ------------------------------------------------------------------------ eMail: ulrich.kiermayr@univie.ac.at Tel: (+43 1) 4277 / 14104 Hotline: security.zid@univie.ac.at Fax: (+43 1) 4277 / 9140 ------------------------------------------------------------------------ GPG Key fingerprint = BF0D 5749 4DC1 ED74 AB67 7180 105F 491D A8D7 64D8 From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 13:07:11 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B90337B404 for ; Mon, 7 Apr 2003 13:07:11 -0700 (PDT) Received: from bill.infodev.ca (bill.infodev.ca [216.191.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C07343FAF for ; Mon, 7 Apr 2003 13:07:10 -0700 (PDT) (envelope-from dpageau@infodev.ca) Received: from localhost (localhost.infodev.ca [127.0.0.1]) by bill.infodev.ca (Postfix) with ESMTP id ECF2A2EB31 for ; Mon, 7 Apr 2003 16:14:14 -0400 (EDT) Received: from bill.infodev.ca ([127.0.0.1]) by localhost (bill.infodev.ca [127.0.0.1:10024]) (amavisd-new) with ESMTP id 22130-09 for ; Mon, 7 Apr 2003 16:14:14 -0400 (EDT) Received: from infodev.ca (rd-03.lan [192.168.42.127]) by bill.infodev.ca (Postfix) with ESMTP id 7A7AE2EB2E for ; Mon, 7 Apr 2003 16:14:14 -0400 (EDT) Message-ID: <3E91DBEC.5080602@infodev.ca> Date: Mon, 07 Apr 2003 16:13:32 -0400 From: "D.Pageau" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: Can't bind IP to my bridge at boot time X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 20:07:11 -0000 If I uncomment #net.link.ether.bridge=1 in sysctl.conf my IP is not bind to rl1 but if I leave it commented and type "sysctl net.link.ether.bridge=1" at command prompt everything work fine. Need help! Thanks $cat /etc/rc.conf ... ifconfig_rl0="inet 192.168.42.2 netmask 255.255.255.0" ifconfig_rl1="inet 216.1.1.2 netmask 255.255.255.240" #ifconfig_rl2 Bridge to rl1 ... $cat /etc/sysctl.conf net.link.ether.bridge_cfg=rl1,rl2 net.link.ether.bridge_ipfw=1 #net.link.ether.bridge=1 $uname -a FreeBSD x.x.x 5.0-RELEASE FreeBSD 5.0-RELEASE #7: Mon Apr 7 13:35:54 EDT 2003 -- Dominic Pageau From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 14:29:54 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57F7F37B401 for ; Mon, 7 Apr 2003 14:29:54 -0700 (PDT) Received: from yama.openaccess.org (ns1.openaccess.org [216.57.214.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5D5D43FA3 for ; Mon, 7 Apr 2003 14:29:53 -0700 (PDT) (envelope-from michael@staff.openaccess.org) Received: from [192.168.5.253] (internal.openaccess.org [216.57.214.120]) by yama.openaccess.org (8.12.3/8.11.6) with ESMTP id h37L9Bn0079853 for ; Mon, 7 Apr 2003 14:09:11 -0700 (PDT) (envelope-from michael@staff.openaccess.org) User-Agent: Microsoft-Entourage/10.0.0.1309 Date: Mon, 07 Apr 2003 14:29:51 -0700 From: Michael DeMan To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: IPSec + NAT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 21:29:54 -0000 Hi All, We need a solution for VPN + NAT for wireless clients. We use ipfilter/ipnat for all our boxes but have been forced I am concerned about the long term management/maintenance issues with some boxes running NATD and others IPNAT, including having staff need to know how to support and debug different configurations and such. Does anybody know of a way to utilize IPSec and IPNAT together? We assign each box two IP addresses, one for the tunnel end point and the other for the tunnel I noticed in the kernel code that I could swap where IPSec and IPFilter does its processing and have IPFilter do its work after IPSec in bound, and before IPSec outbound. I'm not too thrilled with that either since we'd have to fork from the BSD tree and upgrades would start getting tricky. - Mike Michael F. DeMan Director of Technology OpenAccess Internet Services 1305 11th St., 3rd Floor Bellingham, WA 98225 Tel 360-647-0785 x204 Fax 360-738-9785 michael@staff.openaccess.org From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 15:35:58 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3431B37B401 for ; Mon, 7 Apr 2003 15:35:57 -0700 (PDT) Received: from brainlink.com (mail.brainlink.com [66.228.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEED843F85 for ; Mon, 7 Apr 2003 15:35:56 -0700 (PDT) (envelope-from anthonyv@brainlink.com) Received: from [24.185.4.7] (account anthonyv HELO brainlink.com) by brainlink.com (CommuniGate Pro SMTP 3.5.3) with ESMTP id 19071618 for net@freebsd.org; Mon, 07 Apr 2003 17:35:56 -0500 Message-ID: <3E91FD46.1030402@brainlink.com> Date: Mon, 07 Apr 2003 18:35:50 -0400 From: Anthony Volodkin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Establishing an IPSEC link with Lucent (and other) devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 22:35:58 -0000 Hi, I'd like to know if anyone had any degree of success establishing a link with a Lucent VPN Brick device or any other device that requires parameters such as a 'username', 'password' and a 'group password' (my guess this is another way to call a pre-shared key). I've looked at the racoon docs and I see no place to put those in. I also looked at OpenBSD's isakmpd docs and didnt find anything that would specifically set these parameters. Thanks, Anthony Volodkin From owner-freebsd-net@FreeBSD.ORG Tue Apr 8 00:01:56 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A4CA37B405 for ; Tue, 8 Apr 2003 00:01:56 -0700 (PDT) Received: from tokyo.ccrle.nec.de (tokyo.ccrle.nec.de [195.37.70.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1EE343F93 for ; Tue, 8 Apr 2003 00:01:54 -0700 (PDT) (envelope-from Martin.Stiemerling@ccrle.nec.de) Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.9/8.12.8) with ESMTP id h3871mVI027542; Tue, 8 Apr 2003 09:01:48 +0200 (CEST) Received: from ccrle.nec.de (n-stiemerling.office [10.1.1.109]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 9F63E9A225; Tue, 8 Apr 2003 08:58:54 +0200 (CEST) Message-ID: <3E9273DC.9040700@ccrle.nec.de> Date: Tue, 08 Apr 2003 09:01:48 +0200 From: Martin Stiemerling Organization: NEC -- Network Labs Europe User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc3) Gecko/20020619 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "D.Pageau" References: <3E91DBEC.5080602@infodev.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Can't bind IP to my bridge at boot time X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 07:01:56 -0000 As far as I know you can assign only one IP address when you are using bridging. This means only one interface is allowed to be configured with an IP address. Martin D.Pageau wrote: > If I uncomment #net.link.ether.bridge=1 in sysctl.conf my IP is not bind > to rl1 but if I leave it commented and type "sysctl > net.link.ether.bridge=1" at command prompt everything work fine. > > Need help! > > Thanks > > $cat /etc/rc.conf > ... > ifconfig_rl0="inet 192.168.42.2 netmask 255.255.255.0" > ifconfig_rl1="inet 216.1.1.2 netmask 255.255.255.240" > #ifconfig_rl2 Bridge to rl1 > ... > > $cat /etc/sysctl.conf > net.link.ether.bridge_cfg=rl1,rl2 > net.link.ether.bridge_ipfw=1 > #net.link.ether.bridge=1 > > $uname -a > FreeBSD x.x.x 5.0-RELEASE FreeBSD 5.0-RELEASE #7: Mon Apr 7 13:35:54 > EDT 2003 > -- Martin Stiemerling NEC Europe Ltd. -- Network Laboratories Stiemerling@ccrle.nec.de IPv4: http://www.ccrle.nec.de IPv6: http://www.ipv6.ccrle.nec.de From owner-freebsd-net@FreeBSD.ORG Tue Apr 8 06:29:34 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2B2937B401 for ; Tue, 8 Apr 2003 06:29:34 -0700 (PDT) Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DA7443F85 for ; Tue, 8 Apr 2003 06:29:34 -0700 (PDT) (envelope-from steve@nomad.tor.lets.net) Received: from nomad.lets.net (H74.C220.tor.velocet.net [216.138.220.74]) by spitfire.velocet.net (Postfix) with SMTP id A8A1B4B7E3F for ; Tue, 8 Apr 2003 09:29:32 -0400 (EDT) Received: (qmail 17969 invoked by uid 1008); 8 Apr 2003 13:34:19 -0000 Date: Tue, 8 Apr 2003 09:34:19 -0400 From: Steve Shorter To: freebsd-net@freebsd.org Message-ID: <20030408133419.GA17964@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: poll stalled? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 13:29:35 -0000 Howdy! I have a server, FreeBSD 4.6.2, with 3 fxp network interfaces, polling enabled, kern.polling.user_frac is 50, and kernel compiled with Hz = 1000. It became inaccessable over the network and when I logged in over the console the following message(s) were written to it... : poll [14322] stalled in phase 2 poll [14323] stalled in phase 2 : etc.. What causes this? Is it a bug or an indication for tuning? The only tunables for polling that I know of is Hz and the user_frac sysclt Is there a fix for this? thanx - steve From owner-freebsd-net@FreeBSD.ORG Tue Apr 8 06:50:23 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9615437B401 for ; Tue, 8 Apr 2003 06:50:23 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDB6643F3F for ; Tue, 8 Apr 2003 06:50:22 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.8p1/8.12.3) with ESMTP id h38DoMBp004606; Tue, 8 Apr 2003 06:50:22 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.8p1/8.12.3/Submit) id h38DoM58004605; Tue, 8 Apr 2003 06:50:22 -0700 (PDT) (envelope-from rizzo) Date: Tue, 8 Apr 2003 06:50:22 -0700 From: Luigi Rizzo To: Steve Shorter Message-ID: <20030408065022.A4568@xorpc.icir.org> References: <20030408133419.GA17964@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030408133419.GA17964@nomad.lets.net>; from steve@nomad.tor.lets.net on Tue, Apr 08, 2003 at 09:34:19AM -0400 cc: freebsd-net@freebsd.org Subject: Re: poll stalled? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 13:50:24 -0000 inaccessibility is (possibly) coming from a bug in setting the watchdog in the fxp (and other) drivers, long since fixed I believe. On top of this, the '...stalled' messages come out when some interrupt handlers take longer than one timer tick, something that happens frequently e.g. when there is a change in the PHY of the medium, and also for other reasons. cheers luigi On Tue, Apr 08, 2003 at 09:34:19AM -0400, Steve Shorter wrote: > Howdy! > > I have a server, FreeBSD 4.6.2, with 3 fxp network interfaces, > polling enabled, kern.polling.user_frac is 50, and kernel > compiled with Hz = 1000. > > It became inaccessable over the network and when I logged in > over the console the following message(s) were written to it... > > : > poll [14322] stalled in phase 2 > poll [14323] stalled in phase 2 > : > > etc.. > > What causes this? Is it a bug or an indication for tuning? > The only tunables for polling that I know of is Hz and the user_frac sysclt > > > Is there a fix for this? > > thanx - steve > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Apr 8 06:58:44 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BFBA37B401 for ; Tue, 8 Apr 2003 06:58:44 -0700 (PDT) Received: from bill.infodev.ca (bill.infodev.ca [216.191.3.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF18843FB1 for ; Tue, 8 Apr 2003 06:58:43 -0700 (PDT) (envelope-from dpageau@infodev.ca) Received: from localhost (localhost.infodev.ca [127.0.0.1]) by bill.infodev.ca (Postfix) with ESMTP id C0D102EB34 for ; Tue, 8 Apr 2003 10:05:50 -0400 (EDT) Received: from bill.infodev.ca ([127.0.0.1]) by localhost (bill.infodev.ca [127.0.0.1:10024]) (amavisd-new) with ESMTP id 80320-05 for ; Tue, 8 Apr 2003 10:05:50 -0400 (EDT) Received: from infodev.ca (rd-03.lan [192.168.42.127]) by bill.infodev.ca (Postfix) with ESMTP id 5356D2EB31 for ; Tue, 8 Apr 2003 10:05:50 -0400 (EDT) Message-ID: <3E92D716.9040803@infodev.ca> Date: Tue, 08 Apr 2003 10:05:10 -0400 From: "D.Pageau" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <3E91DBEC.5080602@infodev.ca> <3E9273DC.9040700@ccrle.nec.de> In-Reply-To: <3E9273DC.9040700@ccrle.nec.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: Re: Can't bind IP to my bridge at boot time X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 13:58:44 -0000 Only one IP for the bridge (two interfaces). "If you want to be able to telnet into the bridge from the network, it is OK to assign one of the network cards an IP address. The consensus is that assigning both cards an address is a bad idea." Handbook I'm ok with that, two IP for the bridge is probably a bad idea. What about my third interface that is a default route for my nated network? This interface need a IP. BTW I have commented out the ifconfig_rl0 line so I only have one IP and this IP should be setup at boot time on the bridge and it's not working. Martin Stiemerling wrote: > As far as I know you can assign only one IP address when you are using > bridging. This means only one interface is allowed to be configured with > an IP address. > > Martin > > D.Pageau wrote: > >> If I uncomment #net.link.ether.bridge=1 in sysctl.conf my IP is not >> bind to rl1 but if I leave it commented and type "sysctl >> net.link.ether.bridge=1" at command prompt everything work fine. >> >> Need help! >> >> Thanks >> >> $cat /etc/rc.conf >> ... >> ifconfig_rl0="inet 192.168.42.2 netmask 255.255.255.0" >> ifconfig_rl1="inet 216.1.1.2 netmask 255.255.255.240" >> #ifconfig_rl2 Bridge to rl1 >> ... >> >> $cat /etc/sysctl.conf >> net.link.ether.bridge_cfg=rl1,rl2 >> net.link.ether.bridge_ipfw=1 >> #net.link.ether.bridge=1 >> >> $uname -a >> FreeBSD x.x.x 5.0-RELEASE FreeBSD 5.0-RELEASE #7: Mon Apr 7 13:35:54 >> EDT 2003 >> > > -- Dominic Pageau From owner-freebsd-net@FreeBSD.ORG Tue Apr 8 15:15:49 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D94A37B401; Tue, 8 Apr 2003 15:15:49 -0700 (PDT) Received: from mail8-sh.home.nl (mail8.home.nl [213.51.128.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39C1B43F93; Tue, 8 Apr 2003 15:15:48 -0700 (PDT) (envelope-from nascar24@home.nl) Received: from home.nl ([217.120.167.10]) by mail8-sh.home.nl (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030408221546.ERBX958.mail8-sh.home.nl@home.nl>; Wed, 9 Apr 2003 00:15:46 +0200 Message-ID: <3E934A11.3050305@home.nl> Date: Wed, 09 Apr 2003 00:15:45 +0200 From: Marcel Dijk User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org, net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 22:15:49 -0000 Hello all, I am trying to get ISDN4BSD to work, thusfar, no luck. I live in Europe. I use my ISDN adapter (Teles 16.3 ISA non-PnP) to dial in to my ISP. But if I start ppp and dial I get all kind of error from isdnd wich I cannot understand. This is my isdnd.rc: # SYSTEM section: isdnd global configuration parameters system # accounting acctall = on # generate info for everything acctfile = /var/log/isdnd.acct # name & location of accounting file useacctfile = yes # generate accouting info to file isdntime = on monitor-allowed = no # global switch: monitor on/off # User-ppp example entry name = userppp0 usrdevicename = rbch usrdeviceunit = 0 isdncontroller = 0 isdnchannel = 1 local-phone-incoming = 0505267744 remote-phone-incoming = * local-phone-dialout = 0505267744 # This *MUST* be your local number remote-phone-dialout = 1234567 # ppp(8) will override this remdial-handling = first dialin-reaction = ignore dialout-type = normal b1protocol = hdlc idletime-incoming = 900 # Should be larger than ppp's timeout idletime-outgoing = 900 # Should be larger than ppp's timeout unitlength = 0 unitlengthsrc = conf dialretries = 1 dialrandincr = on recoverytime = 1 # Should be smaller than ppp's redial usedown = off downtries = 2 downtime = 30 entry name = userppp1 usrdevicename = rbch usrdeviceunit = 1 isdncontroller = 0 isdnchannel = 2 local-phone-incoming = 1234567 remote-phone-incoming = * local-phone-dialout = 0505267744 # This *MUST* be your local number remote-phone-dialout = 1234567 # ppp(8) will override this remdial-handling = first dialin-reaction = accept dialout-type = normal b1protocol = hdlc idletime-incoming = 900 # Should be larger than ppp's timeout idletime-outgoing = 900 # Should be larger than ppp's timeout unitlength = 0 unitlengthsrc = conf dialretries = 1 dialrandincr = on recoverytime = 1 # Should be smaller than ppp's redial usedown = off downtries = 2 downtime = 30 ---- I filled it in according to the example in /usr/share/examples/isdn. And here is my ppp.conf default: set phone ISP_NUMBER # Replace this with your ISPs phone number set authname MY_USERNAME # Replace these with your login name & password. set authkey MY_PASS # This profile assumes you're using PAP or CHAP. # set enddisc mac # Assuming you have a LAN (dont have a LAN on the ISDN PC) enable lqr set reconnect 3 5 set redial 3 10 set lqrperiod 45 disable pred1 deflate mppe deny pred1 deflate mppe set timeout 60 300 # The minimum charge period is 5 minutes, so don't # hangup before then # We have no chat scripts in the ISDN world (yet) set dial set login set logout set hangup set device /dev/i4brbch0 /dev/i4brbch1 # Raw B-channel devices set speed sync # ISDN is synchronous enable dns # Ask the peer what to put in resolv.conf # Take a wild guess at an IP number and let the other side decide set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0 add! default hisaddr # set mrru 1500 # Multilink mode please set mru 1504 # Room for the MP header # clone 1,2 # Two new links # link deflink rm # And get rid of the original one # link * set mode auto # Automatically manage the second link # set autoload 10 80 30 # Down @10% usage, up at 80%, 30s sample set server /var/run/ppp/ppp-isdn "" 0177 # The diagnostic port (-rw-------) --- Also filled in according to the example. I also have an alternative ppp.conf wich gives the same errors: default: set device /dev/i4brbch0 /dev/i4brbch1 set speed sync set dial set logout set hangup hetnet: set phone ISP_NUMBER # Replace this with your ISPs phone number set login set authname THE_NAME # Replace these with your login name & password. set authkey THE_PASS # This profile assumes you're using PAP or CHAP. ifaddr 0.0.0.0 add default HISADDR enable dns # set enddisc mac # Assuming you have a LAN # enable lqr # set reconnect 3 5 # set redial 3 10 # set lqrperiod 45 # disable pred1 deflate mppe # deny pred1 deflate mppe # set timeout 60 300 # The minimum charge period is 5 minutes, so don't # hangup before then # enable dns # Ask the peer what to put in resolv.conf # Take a wild guess at an IP number and let the other side decide #set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0 #add! default hisaddr # set mrru 1500 # Multilink mode please #set mru 1504 # Room for the MP header # clone 1,2 # Two new links # link deflink rm # And get rid of the original one # link * set mode auto # Automatically manage the second link # set autoload 10 80 30 # Down @10% usage, up at 80%, 30s sample # set server /var/run/ppp/ppp-isdn "" 0177 # The diagnostic port (-rw-------) ---------- I can't give you the errors ISDND gives, I simply forgot them. It were unintelligable errors to me. The errors came from isdnd, not from ppp. Sorry for the mega e-mail but I thought I could best be as verbose as possible. Hope someone can help. Gr. Marcel. From owner-freebsd-net@FreeBSD.ORG Wed Apr 9 06:34:26 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F25337B404 for ; Wed, 9 Apr 2003 06:34:26 -0700 (PDT) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with SMTP id D747F43F93 for ; Wed, 9 Apr 2003 06:34:24 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 24592 invoked from network); 9 Apr 2003 13:32:22 -0000 Received: from unknown (HELO pipeline.ch) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 9 Apr 2003 13:32:22 -0000 Message-ID: <3E942121.7A3647EB@pipeline.ch> Date: Wed, 09 Apr 2003 15:33:21 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org, tmm@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Bug in ARP requests X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2003 13:34:26 -0000 Hello, There is a nasty bug in the ARP request code in 4.8-STABLE regarding the target hardware address field which is left unset. tmm fixed this in rev 1.97 in -CURRENT 3 month ago but forgot to MFC it back to -STABLE since (despite his MFC in two weeks comment). I got hit by this pretty hard when I connected a FreeBSD/Zebra box to AMSIX. Appearently the Cisco and Juniper boxes don't answer to broken ARP requests if the target hardware address field is not set to NULL but filled with random memory junk. While debugging this we got really confused by the tcpdumps... Ethereal saved the day because it has a much nicer display than tcpdump. Anyway, please MFC to fix -STABLE. -- Andre From owner-freebsd-net@FreeBSD.ORG Wed Apr 9 06:51:41 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EC6037B401 for ; Wed, 9 Apr 2003 06:51:41 -0700 (PDT) Received: from musique.teaser.net (musique.teaser.net [213.91.2.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 317CB43F85 for ; Wed, 9 Apr 2003 06:51:40 -0700 (PDT) (envelope-from e-masson@kisoft-services.com) Received: from notbsdems.interne.kisoft-services.com (unknown [195.6.126.253]) by musique.teaser.net (Postfix) with ESMTP id 9128B72517 for ; Wed, 9 Apr 2003 15:51:38 +0200 (CEST) Received: by notbsdems.interne.kisoft-services.com (Postfix, from userid 1001) id 663905BB68; Wed, 9 Apr 2003 15:51:11 +0200 (CEST) To: Mailing List FreeBSD Network From: Eric Masson X-Operating-System: FreeBSD 4.8-RC i386 Date: Wed, 09 Apr 2003 15:51:11 +0200 Message-ID: <86znmzvkxc.fsf@notbsdems.interne.kisoft-services.com> User-Agent: Gnus/5.090018 (Oort Gnus v0.18) XEmacs/21.4 (Common Lisp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: mpd & nullmodem link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2003 13:51:41 -0000 Hello, mpd-3.13 FreeBSD 4.8-RELEASE I've googled for pointers about establishing a nullmodem link beetween 2 mpd enabled boxes (mpd doc seems to say that it's possible). So far, I haven't found anything. Has anyone experience regarding $subject ? TIA Regards Eric Masson -- B> Pourquoi pas à l'aide d'un cheval de troyes, c'est du ressort de B> tout le monde. La specialite du Troyes c'est l'andouillette, pas le cheval. -+- B in www.le-gnu.net - saucisson de cheval -+- From owner-freebsd-net@FreeBSD.ORG Wed Apr 9 07:16:54 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A275237B401 for ; Wed, 9 Apr 2003 07:16:54 -0700 (PDT) Received: from apollo.laserfence.net (apollo.laserfence.net [196.44.69.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id E26C843F3F for ; Wed, 9 Apr 2003 07:16:52 -0700 (PDT) (envelope-from will@unfoldings.net) Received: from localhost ([127.0.0.1]) by apollo.laserfence.net with esmtp (Exim 4.10) id 193GNS-000KSm-00; Wed, 09 Apr 2003 16:16:38 +0200 Received: from prometheus-p0.datel.laserfence.net ([192.168.255.1] helo=prometheus.home.laserfence.net) by apollo.laserfence.net with esmtp (Exim 4.10) id 193GNE-000KSZ-00; Wed, 09 Apr 2003 16:16:25 +0200 Received: from phoenix.home.laserfence.net ([192.168.0.2]) by prometheus.home.laserfence.net with esmtp (Exim 4.10) id 193GN9-000AOB-00; Wed, 09 Apr 2003 16:16:19 +0200 Received: from will by phoenix.home.laserfence.net with local (Exim 4.10) id 193GN8-0001Pc-00; Wed, 09 Apr 2003 16:16:18 +0200 From: Willie Viljoen To: Eric Masson , Mailing List FreeBSD Network Date: Wed, 9 Apr 2003 16:16:18 +0200 User-Agent: KMail/1.5.1 References: <86znmzvkxc.fsf@notbsdems.interne.kisoft-services.com> In-Reply-To: <86znmzvkxc.fsf@notbsdems.interne.kisoft-services.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304091616.18432.will@unfoldings.net> Sender: Willie Viljoen X-Spam-Score: (/) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *193GNE-000KSZ-00*4371M1p8OwQ* X-Virus-Scanned: by AMaViS snapshot-20020422 Subject: Re: mpd & nullmodem link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2003 14:16:55 -0000 On Wednesday 09 April 2003 15:51, someone, possibly Eric Masson, typed: > Hello, > > mpd-3.13 > FreeBSD 4.8-RELEASE > > I've googled for pointers about establishing a nullmodem link beetween 2 > mpd enabled boxes (mpd doc seems to say that it's possible). > Why use mpd for this? pppd(8) will do just fine. Here's a quick example, all needed is a pppd on both ends, end for the cable to be plugged in: #/etc/ppp/options on pc1 cuaa0 #FreeBSD: COM1 in DOS 115200 crtscts lock local #Use nullmodem mode instead of modem lines deflate #Compression # IP address for this end : IP address for other end 192.168.254.1:192.168.254.1 netmask 255.255.255.255 #/etc/ppp/options on pc2 #Same as above, except 192.168.254.2:192.168.254.1 #If the other machine is Linux, cuaa0 is ttyS0. Now just start pppd on both ends and once it syncs, you will be able to have the machines talk IP to each other. To start pppd automatically and have it restarted if it dies, add this to /etc/ttys: cuaa0 "/usr/sbin/pppd cuaa0 -detach" unknown on This can also be done in Linux, check man inittab. Hope this helps. Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) will@unfoldings.net From owner-freebsd-net@FreeBSD.ORG Wed Apr 9 23:01:06 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9C1937B401 for ; Wed, 9 Apr 2003 23:01:06 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1CA843F85 for ; Wed, 9 Apr 2003 23:01:05 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: from blossom.cjclark.org (12-234-159-107.client.attbi.com[12.234.159.107]) by sccrmhc02.attbi.com (sccrmhc02) with ESMTP id <20030410060104002006uic8e>; Thu, 10 Apr 2003 06:01:05 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.8p1/8.12.3) with ESMTP id h3A613ki002312; Wed, 9 Apr 2003 23:01:03 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.8p1/8.12.8/Submit) id h3A60pPc002311; Wed, 9 Apr 2003 23:00:51 -0700 (PDT) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Wed, 9 Apr 2003 23:00:51 -0700 From: "Crist J. Clark" To: Mark Santcroos Message-ID: <20030410060051.GA2082@blossom.cjclark.org> References: <20030407182119.GB744@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030407182119.GB744@laptop.6bone.nl> User-Agent: Mutt/1.4.1i X-URL: http://people.freebsd.org/~cjc/ cc: freebsd-net@freebsd.org Subject: Re: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Crist J. Clark" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 06:01:07 -0000 On Mon, Apr 07, 2003 at 08:21:19PM +0200, Mark Santcroos wrote: > On Mon, Apr 07, 2003 at 11:01:54AM -0700, Michael DeMan wrote: > > Is there a way to do secure syslog, via SSH or something? > > You can do it indeed using ssh port forwarding. When did, a) SSH gain the ability to do port forwarding of UDP? Or, b) Did the FreeBSD syslogd(8) gain the ability to talk over TCP? -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org From owner-freebsd-net@FreeBSD.ORG Wed Apr 9 23:05:19 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA86937B401 for ; Wed, 9 Apr 2003 23:05:19 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C94B43F3F for ; Wed, 9 Apr 2003 23:05:18 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: from blossom.cjclark.org (12-234-159-107.client.attbi.com[12.234.159.107]) by sccrmhc01.attbi.com (sccrmhc01) with ESMTP id <2003041006051700100ogkmme>; Thu, 10 Apr 2003 06:05:17 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.8p1/8.12.3) with ESMTP id h3A65Gki002333; Wed, 9 Apr 2003 23:05:16 -0700 (PDT) (envelope-from crist.clark@attbi.com) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.8p1/8.12.8/Submit) id h3A65CeO002332; Wed, 9 Apr 2003 23:05:12 -0700 (PDT) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Wed, 9 Apr 2003 23:05:12 -0700 From: "Crist J. Clark" To: "D.Pageau" Message-ID: <20030410060512.GB2082@blossom.cjclark.org> References: <3E91DBEC.5080602@infodev.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E91DBEC.5080602@infodev.ca> User-Agent: Mutt/1.4.1i X-URL: http://people.freebsd.org/~cjc/ cc: freebsd-net@freebsd.org Subject: Re: Can't bind IP to my bridge at boot time X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Crist J. Clark" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 06:05:20 -0000 On Mon, Apr 07, 2003 at 04:13:32PM -0400, D.Pageau wrote: > If I uncomment #net.link.ether.bridge=1 in sysctl.conf my IP is not bind > to rl1 but if I leave it commented and type "sysctl > net.link.ether.bridge=1" at command prompt everything work fine. > > Need help! > > Thanks > > $cat /etc/rc.conf > ... > ifconfig_rl0="inet 192.168.42.2 netmask 255.255.255.0" > ifconfig_rl1="inet 216.1.1.2 netmask 255.255.255.240" > #ifconfig_rl2 Bridge to rl1 > ... > > $cat /etc/sysctl.conf > net.link.ether.bridge_cfg=rl1,rl2 > net.link.ether.bridge_ipfw=1 > #net.link.ether.bridge=1 > > $uname -a > FreeBSD x.x.x 5.0-RELEASE FreeBSD 5.0-RELEASE #7: Mon Apr 7 13:35:54 > EDT 2003 What messages pop up on the console during boot when this interface should be configured? -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org From owner-freebsd-net@FreeBSD.ORG Wed Apr 9 23:48:01 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6F2237B401; Wed, 9 Apr 2003 23:48:01 -0700 (PDT) Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AC4943FA3; Wed, 9 Apr 2003 23:48:01 -0700 (PDT) (envelope-from suz@crl.hitachi.co.jp) Received: from s30.crl.hitachi.co.jp (orange.kame.net [3ffe:501:4819:2000:203:47ff:fea5:3085]) by orange.kame.net (Postfix) with ESMTP id 47CD97020; Thu, 10 Apr 2003 15:48:00 +0900 (JST) Date: Thu, 10 Apr 2003 15:47:15 +0900 Message-ID: From: SUZUKI Shinsuke To: Jeffrey Hsu X-cite: xcite 1.33 In-Reply-To: <200304062041.h36KfVHo005994@mta7.pltn13.pbi.net> References: <200304062041.h36KfVHo005994@mta7.pltn13.pbi.net> User-Agent: User-Agent: Wanderlust/2.11.3 (Wonderwall) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: Network Systems Research Dept., Central Research Laboratory, Hitachi, Ltd, Japan MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII cc: Craig Boston cc: net@freebsd.org Subject: Re: IPv6 MTU bug? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 06:48:02 -0000 Hello, >>>>> On Sun, 06 Apr 2003 13:44:00 -0700 >>>>> hsu@freebsd.org(Jeffrey Hsu) said: > Yes, this is a bug of the IPv6 code, and has been fixed in KAME > snapshots. The fix should eventually be merged to the freebsd > repository, but I'm not a committer and thus cannot tell when. hsu> If you make a patch relative to -current, I'd be glad to commit hsu> it for you. Actually there are too many diffs between -current and KAME. So I'm now listing up items to be merged (considering the IETF status and code maturity) to prevent conflicts among KAME-to-freebsd feedbacks. And I'd like to commit the above fix in this feedback activity. I'll call for a review when I finished this list-up (planning to be done in May at the latest) Thanks, ---- SUZUKI, Shinsuke @ Hitachi / KAME Project From owner-freebsd-net@FreeBSD.ORG Thu Apr 10 00:47:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB9B437B401 for ; Thu, 10 Apr 2003 00:47:53 -0700 (PDT) Received: from corpmail.outblaze.com (202-77-223-51.outblaze.com [202.77.223.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id E13FA43F93 for ; Thu, 10 Apr 2003 00:47:50 -0700 (PDT) (envelope-from yusufg@outblaze.com) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by corpmail.outblaze.com (Postfix) with ESMTP id 95B1F7D2E for ; Thu, 10 Apr 2003 07:55:05 +0000 (GMT) Received: from yusufg.portal2.com (202-77-223-125.outblaze.com [202.77.223.125]) by corpmail.outblaze.com (Postfix) with SMTP id 6D18A520CD for ; Thu, 10 Apr 2003 07:55:05 +0000 (GMT) Received: (qmail 19534 invoked by uid 500); 10 Apr 2003 07:46:47 -0000 Date: Thu, 10 Apr 2003 15:46:47 +0800 From: Yusuf Goolamabbas To: freebsd-net@freebsd.org Message-ID: <20030410074647.GA19450@outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.6; VAE: 6.19.0.3; VDF: 6.19.0.6; host: corpmail.outblaze.com) Subject: What's the timeout value for connections in FIN_WAIT2 state X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 07:47:54 -0000 Hi, According to this page http://httpd.apache.org/docs/misc/fin_wait_2.html FreeBSD from ver 2.0 onwards has a timeout for FIN_WAIT2 state, what is the timeout for this state, is there a sysctl to control this On a loaded mailserver running 4.7-stable, I am seeing a lot of connections in FIN_WAIT2 state, and they don't seem to be going away even after 0.5 hr, other than a reboot is there any to get rid of them. My understanding is that lots of these FIN_WAIT2 states will just take up space in kernel tables Regards, Yusuf From owner-freebsd-net@FreeBSD.ORG Thu Apr 10 01:38:07 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FF2037B401; Thu, 10 Apr 2003 01:38:07 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22AF143FB1; Thu, 10 Apr 2003 01:38:06 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.9/8.11.6) with SMTP id h3A8c4tF023839; Thu, 10 Apr 2003 10:38:04 +0200 Received: (nullmailer pid 37791 invoked by uid 1000); Thu, 10 Apr 2003 08:38:00 -0000 Date: Thu, 10 Apr 2003 10:37:59 +0200 From: Mark Santcroos To: "Crist J. Clark" Message-ID: <20030410083759.GA14765@laptop.6bone.nl> References: <20030407182119.GB744@laptop.6bone.nl> <20030410060051.GA2082@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030410060051.GA2082@blossom.cjclark.org> User-Agent: Mutt/1.4.1i X-Handles: MS6-6BONE, MS18417-RIPE cc: freebsd-net@freebsd.org Subject: Re: Syslog over SSH X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 08:38:07 -0000 On Wed, Apr 09, 2003 at 11:00:51PM -0700, Crist J. Clark wrote: > b) Did the FreeBSD syslogd(8) gain the ability to talk over TCP? As mentioned by someone else already he can use the syslog_ng port for that. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM From owner-freebsd-net@FreeBSD.ORG Thu Apr 10 12:27:38 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE0C637B404 for ; Thu, 10 Apr 2003 12:27:37 -0700 (PDT) Received: from rigel.cs.pdx.edu (rigel.cs.pdx.edu [131.252.208.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FBAD43F85 for ; Thu, 10 Apr 2003 12:27:34 -0700 (PDT) (envelope-from sashi@cs.pdx.edu) Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [131.252.208.57]) by rigel.cs.pdx.edu (8.12.8/8.12.8) with ESMTP id h3AJRXjw017011 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 10 Apr 2003 12:27:33 -0700 (PDT) Received: from sirius.cs.pdx.edu (sashi@localhost [127.0.0.1]) by sirius.cs.pdx.edu (8.12.8/8.12.8) with ESMTP id h3AJRX2J027018 for ; Thu, 10 Apr 2003 12:27:33 -0700 (PDT) Received: from localhost (sashi@localhost)h3AJRWcA027015 for ; Thu, 10 Apr 2003 12:27:32 -0700 (PDT) Date: Thu, 10 Apr 2003 12:27:32 -0700 (PDT) From: Sashikiran Rachakonda To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Question Regarding IP Alias X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 19:27:38 -0000 Hi,i have a question regarding the IP Alias. If i bind my interface to 2 ip addresses say 1) ifconfig xl0 add w.x.y.z netmask 255.255.255.0 2) ifconfig xl0 add p.q.r.s netmask 255.255.0.0 Is there a way that i can force the packets coming-out of this interface to have ipSrc = p.q.r.s and not w.x.y.z. My question is is there a way that you can tell the interface to have the IPsrc set to the one we want to, for all packets coming out of this interface. Thanx in Advance, --Sashi. From owner-freebsd-net@FreeBSD.ORG Thu Apr 10 14:10:29 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEAE537B401 for ; Thu, 10 Apr 2003 14:10:28 -0700 (PDT) Received: from thalia.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C89C943F93 for ; Thu, 10 Apr 2003 14:10:26 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-a137.otenet.gr [212.205.215.137]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h3ALAE72013102; Fri, 11 Apr 2003 00:10:16 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.9/8.12.9) with ESMTP id h3ALAEKD097836; Fri, 11 Apr 2003 00:10:14 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.9/8.12.9/Submit) id h3AL0CKs084911; Fri, 11 Apr 2003 00:00:12 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Fri, 11 Apr 2003 00:00:12 +0300 From: Giorgos Keramidas To: Sashikiran Rachakonda Message-ID: <20030410210012.GA84656@gothmog.gr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-net@freebsd.org Subject: Re: Question Regarding IP Alias X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 21:10:30 -0000 On 2003-04-10 12:27, Sashikiran Rachakonda wrote: > > Hi,i have a question regarding the IP Alias. If i bind my interface to 2 > ip addresses say > > 1) ifconfig xl0 add w.x.y.z netmask 255.255.255.0 > 2) ifconfig xl0 add p.q.r.s netmask 255.255.0.0 > > Is there a way that i can force the packets coming-out of this > interface to have ipSrc = p.q.r.s and not w.x.y.z. My question is is > there a way that you can tell the interface to have the IPsrc set to > the one we want to, for all packets coming out of this interface. The default IP address that is used for packets that aren't explicitly set to something different is the first address of the interface, IIRC. 'First' here being something that depends heavily on the order of the ifconfig commands and the running kernel's code. Instead of relying on factors like this that you cannot control reliably, your programs should explicitly bind() a sockaddr_in structure with the p.q.r.s address. Then all outgoing packets of that socket will have the correct address. - Giorgos From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 00:11:08 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34F6C37B401; Fri, 11 Apr 2003 00:11:08 -0700 (PDT) Received: from cow.home.mshindo.net (203.60.138.210.bn.2iij.net [210.138.60.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id E090443F75; Fri, 11 Apr 2003 00:11:04 -0700 (PDT) (envelope-from mshindo@mshindo.net) Received: from localhost ([210.196.142.99]) by cow.home.mshindo.net (8.12.6/8.12.6) with ESMTP id h3B7ECkF077118; Fri, 11 Apr 2003 16:14:14 +0900 (JST) (envelope-from mshindo@mshindo.net) Date: Fri, 11 Apr 2003 16:10:56 +0900 (JST) Message-Id: <20030411.161056.71083042.mshindo@mshindo.net> To: oppermann@pipeline.ch From: Motonori Shindo In-Reply-To: <3E942121.7A3647EB@pipeline.ch> References: <3E942121.7A3647EB@pipeline.ch> X-Mailer: Mew version 4.0.51 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: tmm@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Bug in ARP requests X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 07:11:08 -0000 Hi, From: Andre Oppermann Subject: Bug in ARP requests Date: Wed, 09 Apr 2003 15:33:21 +0200 > I got hit by this pretty hard when I connected a FreeBSD/Zebra box > to AMSIX. Appearently the Cisco and Juniper boxes don't answer to > broken ARP requests if the target hardware address field is not set > to NULL but filled with random memory junk. While debugging this we > got really confused by the tcpdumps... Ethereal saved the day because > it has a much nicer display than tcpdump. I also came accross this problem when I was testing the equipment (wireless access point, in fact) made by the company I currently work for. At that time, I thought that it was specific my company's equipment, but now I'm amezed to know that there are so many networking equipments that don't accept such a bogus ARP Request. BTW, tcpdump prints out the target hardware address in ARP Request if it isn't all zero and that made me realized that the problem was caused by FreeBSD's ARP request. tcpdump saved a day for me:-) From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 00:26:51 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FEAE37B401; Fri, 11 Apr 2003 00:26:51 -0700 (PDT) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 540E743F3F; Fri, 11 Apr 2003 00:26:50 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from mail by mx.nsu.ru with drweb-scanned (Exim 3.35 #1 (Debian)) id 193swB-0006kD-00; Fri, 11 Apr 2003 14:27:03 +0700 Received: from iclub.nsu.ru ([193.124.215.97] ident=root) by mx.nsu.ru with esmtp (Exim 3.35 #1 (Debian)) id 193sw3-0006Xp-00; Fri, 11 Apr 2003 14:26:55 +0700 Received: from iclub.nsu.ru (fjoe@localhost [127.0.0.1]) by iclub.nsu.ru (8.12.9/8.12.9) with ESMTP id h3B7Pnud016738; Fri, 11 Apr 2003 14:25:49 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Received: (from fjoe@localhost) by iclub.nsu.ru (8.12.9/8.12.9/Submit) id h3B7Peoq016733; Fri, 11 Apr 2003 14:25:40 +0700 (NSS) Date: Fri, 11 Apr 2003 14:25:40 +0700 From: Max Khon To: Motonori Shindo Message-ID: <20030411142540.A14117@iclub.nsu.ru> References: <3E942121.7A3647EB@pipeline.ch> <20030411.161056.71083042.mshindo@mshindo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030411.161056.71083042.mshindo@mshindo.net>; from mshindo@mshindo.net on Fri, Apr 11, 2003 at 04:10:56PM +0900 X-Spam-Status: No, hits=-3.0 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01, USER_AGENT,USER_AGENT_MUTT version=2.43 X-Envelope-To: mshindo@mshindo.net, oppermann@pipeline.ch, tmm@freebsd.org, freebsd-net@freebsd.org cc: tmm@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Bug in ARP requests X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 07:26:51 -0000 hi, there! On Fri, Apr 11, 2003 at 04:10:56PM +0900, Motonori Shindo wrote: > From: Andre Oppermann > Subject: Bug in ARP requests > Date: Wed, 09 Apr 2003 15:33:21 +0200 > > > I got hit by this pretty hard when I connected a FreeBSD/Zebra box > > to AMSIX. Appearently the Cisco and Juniper boxes don't answer to > > broken ARP requests if the target hardware address field is not set > > to NULL but filled with random memory junk. While debugging this we > > got really confused by the tcpdumps... Ethereal saved the day because > > it has a much nicer display than tcpdump. > > I also came accross this problem when I was testing the equipment > (wireless access point, in fact) made by the company I currently work > for. At that time, I thought that it was specific my company's > equipment, but now I'm amezed to know that there are so many > networking equipments that don't accept such a bogus ARP Request. > > BTW, tcpdump prints out the target hardware address in ARP Request if > it isn't all zero and that made me realized that the problem was > caused by FreeBSD's ARP request. tcpdump saved a day for me:-) ok, rev 1.97 MFC'ed a few minutes ago /fjoe From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 10:14:25 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE9A237B401; Fri, 11 Apr 2003 10:14:25 -0700 (PDT) Received: from imo-r07.mx.aol.com (imo-r07.mx.aol.com [152.163.225.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE80E43F3F; Fri, 11 Apr 2003 10:14:24 -0700 (PDT) (envelope-from BelletJr@aol.com) Received: from BelletJr@aol.com by imo-r07.mx.aol.com (mail_out_v34.21.) id d.1dc.74b8b15 (3310); Fri, 11 Apr 2003 13:14:15 -0400 (EDT) From: BelletJr@aol.com Message-ID: <1dc.74b8b15.2bc851e7@aol.com> Date: Fri, 11 Apr 2003 13:14:15 EDT To: tlambert2@mindspring.com MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: AOL 5.0 for Windows sub 116 cc: current@freebsd.org cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 17:14:26 -0000 >Dans un e-mail dat=E9 du 11/04/03 00:23:16 Paris, Madrid (Heure d'=E9t=E9),= =20 tlambert2@mindspring.com a =E9crit : > >BelletJr@aol.com wrote: >> Why does not connect(2) return any error when trying to connect to a host >> unreachable because of an infinite loop in the routes? No time-out occurs= =20 and >> the value 0 is returned by connect(2). >> My test was done with TCP/IPv4. > >Because it can't detect an infinite routing loop. Then why can't it detect an infinite routing loop? :) It does not implement=20 the classic three-way handshake of a TCP connection establishment?? If this is the case, I think the man page is not precise enough. It states=20 "If the socket is of type SOCK_STREAM, this call attempts to make a=20 connection to another socket" and later on "The connect() function returns=20 the value 0 if successful". BTW we can imagine that the majority of programs aren't crafted to handle=20 this case. Have a look for example to the simple "daytime.c" program from th= e=20 developper handbook. It just doesn't do anything if time.nist.gov is=20 unreachable because of an infinite routing loop. Jerome From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 13:19:02 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 686BD37B401 for ; Fri, 11 Apr 2003 13:19:02 -0700 (PDT) Received: from web10402.mail.yahoo.com (web10402.mail.yahoo.com [216.136.130.94]) by mx1.FreeBSD.org (Postfix) with SMTP id 08F0943FAF for ; Fri, 11 Apr 2003 13:19:02 -0700 (PDT) (envelope-from opolyakov@yahoo.com) Message-ID: <20030411201901.98887.qmail@web10402.mail.yahoo.com> Received: from [67.112.212.200] by web10402.mail.yahoo.com via HTTP; Fri, 11 Apr 2003 13:19:01 PDT Date: Fri, 11 Apr 2003 13:19:01 -0700 (PDT) From: Oleg Polyakov To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1989487801-1050092341=:98618" Subject: RFC3390 implementation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 20:19:02 -0000 --0-1989487801-1050092341=:98618 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline Nice to see RFC3390 implemented. It looks like it worth mention in tuning(7). While we on it - there is section 2 in RFC: >2. Implementation Issues > > When larger initial windows are implemented along with Path MTU > Discovery [RFC1191], and the MSS being used is found to be too large, > the congestion window `cwnd' SHOULD be reduced to prevent large > bursts of smaller segments. Specifically, `cwnd' SHOULD be reduced > by the ratio of the old segment size to the new segment size. > So we need to take care of cwnd reduction in tcp_mtudisc function. Here is a patch attached. Or we may do it conditionally depending on tcp_do_rfc3390 variable. ---- Oleg __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com --0-1989487801-1050092341=:98618 Content-Type: text/plain; name="p3b.txt" Content-Description: p3b.txt Content-Disposition: inline; filename="p3b.txt" --- tcp_subr.c.orig Fri Apr 11 13:05:53 2003 +++ tcp_subr.c Fri Apr 11 13:06:27 2003 @@ -1449,6 +1449,14 @@ #endif if (so->so_snd.sb_hiwat < mss) mss = so->so_snd.sb_hiwat; + /* + * Follow suggestion in RFC 3390 to reduce the congestion + * window by the ratio of the old segment size to the new + * segment size. + */ + if (mss < tp->t_maxseg) + tp->snd_cwnd = max((tp->snd_cwnd / tp->t_maxseg) * + mss, mss); tp->t_maxseg = mss; --0-1989487801-1050092341=:98618-- From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 14:03:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86C4637B40A for ; Fri, 11 Apr 2003 14:03:53 -0700 (PDT) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9879343FBD for ; Fri, 11 Apr 2003 14:03:52 -0700 (PDT) (envelope-from pblok@inter.NL.net) Received: from bsdpc (ip503cf841.speed.planet.nl [80.60.248.65]) 2002))freebsd-net@freebsd.org; Fri, 11 Apr 2003 23:06:05 +0200 (MEST) Date: Fri, 11 Apr 2003 23:03:50 +0200 From: "Peter J. Blok" To: freebsd-net@freebsd.org Message-id: <200304112303.50839.pblok@inter.NL.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.5 Subject: routing a broadcast over a gif tunnel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 21:03:53 -0000 Hi, I need to fool a PC package. The package is searching for a server responding to a broadcast on port 56415. That server is across an ipsec/gif tunnel. How can I bridge that particular packet towards the segment at the other end. I have tried various ipfw fwd rules and ipfilter redirection, but none of them works (because the other segment is not locally available). Peter From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 14:21:28 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73D1C37B405; Fri, 11 Apr 2003 14:21:28 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43D2443F93; Fri, 11 Apr 2003 14:21:27 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0012.cvx22-bradley.dialup.earthlink.net ([209.179.198.12] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1945xc-0006dJ-00; Fri, 11 Apr 2003 14:21:25 -0700 Message-ID: <3E973187.239563@mindspring.com> Date: Fri, 11 Apr 2003 14:20:07 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: BelletJr@aol.com References: <1dc.74b8b15.2bc851e7@aol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4023478172c249d3e3a0fe231b5cb0e903ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 21:21:29 -0000 BelletJr@aol.com wrote: > >Because it can't detect an infinite routing loop. > > Then why can't it detect an infinite routing loop? :) It does not implement > the classic three-way handshake of a TCP connection establishment?? It sends SYN and waits for SYN/ACK before sending an ACK. The wait is indenfinite, unless the machine receives an ICMP "host unreachable" or similar connection reject packet. Most likely, ICMP is disabled somewhere between you and the other end. Probably at your firewall. You should look at a tcpdump of the traffic between the two endpoints which occurs during the connection request, to find out for sure. If you don't like raw tcpdump (or can't read it easily), then use "ethereal" from ports. As to why it can't detect it without the ICMP, it's because it's not possible to compute transitive closure over the graph of your local routing table, and all the routing tables between you and the other end, because the memory isn't local. 8-) 8-). > If this is the case, I think the man page is not precise enough. It states > "If the socket is of type SOCK_STREAM, this call attempts to make a > connection to another socket" and later on "The connect() function returns > the value 0 if successful". You're mixing up two different usages of connect(). > BTW we can imagine that the majority of programs aren't crafted to handle > this case. Probably not... the majority of programs probably assume that your network is set up correctly. 8-). > Have a look for example to the simple "daytime.c" program from the > developper handbook. It just doesn't do anything if time.nist.gov is > unreachable because of an infinite routing loop. I still don't know what you mean by "infinite routing loop"; there's really no such thing. If you try to insert one on a single host, the insertion attempt that would cause the loop will be rejected by the "route add". It's a radix tree; being hierarchical, it can't loop, since the idea of a loop is not supported by the data structure. The only purpose of the routing code is selection of "next hop", and that dictates "interface to use". And that's all it does. It's up to intermediate hosts to indicate route failures via ICMP messages (Internet Control Message Protocol). If you disable ICMP, be ready to have your foot shot off. -- Terry From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 15:20:59 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 015FC37B401 for ; Fri, 11 Apr 2003 15:20:59 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF4343FBF for ; Fri, 11 Apr 2003 15:20:58 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h3BMKudN049958; Fri, 11 Apr 2003 18:20:56 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h3BMKusM049957; Fri, 11 Apr 2003 18:20:56 -0400 (EDT) Date: Fri, 11 Apr 2003 18:20:56 -0400 From: Barney Wolff To: BelletJr@aol.com Message-ID: <20030411222056.GA49927@pit.databus.com> References: <1dc.74b8b15.2bc851e7@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1dc.74b8b15.2bc851e7@aol.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 22:20:59 -0000 On Fri, Apr 11, 2003 at 01:14:15PM -0400, BelletJr@aol.com wrote: > >> Why does not connect(2) return any error when trying to connect to a host > >> unreachable because of an infinite loop in the routes? No time-out occurs > and > >> the value 0 is returned by connect(2). > >> My test was done with TCP/IPv4. Well, after actually looking at this, I believe it's a bug, in both current and stable. The following patch appears to fix it: --- ip_input.c.orig Wed Apr 9 14:07:16 2003 +++ ip_input.c Fri Apr 11 17:54:11 2003 @@ -1696,7 +1696,7 @@ 0, EMSGSIZE, EHOSTDOWN, EHOSTUNREACH, EHOSTUNREACH, EHOSTUNREACH, ECONNREFUSED, ECONNREFUSED, EMSGSIZE, EHOSTUNREACH, 0, 0, - 0, 0, 0, 0, + 0, 0, EHOSTUNREACH, 0, ENOPROTOOPT, ECONNREFUSED }; I'll file a PR. By the way, the reason programs appear to do nothing after hitting the problem is that they get SIGPIPE when trying to write on the socket. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-net@FreeBSD.ORG Fri Apr 11 22:59:49 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFF7E37B401 for ; Fri, 11 Apr 2003 22:59:49 -0700 (PDT) Received: from usc.edu (usc.edu [128.125.253.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 350B443FBF for ; Fri, 11 Apr 2003 22:59:49 -0700 (PDT) (envelope-from kunchanl@pollux.usc.edu) Received: from pollux.usc.edu (kunchanl@pollux.usc.edu [128.125.7.29]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id WAA10187 for ; Fri, 11 Apr 2003 22:59:49 -0700 (PDT) Received: from localhost (kunchanl@localhost) by pollux.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id WAA04138 for ; Fri, 11 Apr 2003 22:59:48 -0700 (PDT) Date: Fri, 11 Apr 2003 22:59:48 -0700 (PDT) From: kunchanl To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: no carrier X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 05:59:50 -0000 Hi all, I'm trying to collect some trace on a campus network. However, I've been experiencing something strange and couldn't figure out what is the problem. I'm wondering if any of you can shed me some light. Here is the story: The network admin has mirrored the traffic on one of the unused ports on the switch for me. But after I connected the port on the switch to my network interface card with a fiber cable, I only saw the LED light (RX/TX) on the switch port flashing, but not theh LED light (LINK/DATA) on my interface card. I also didn't see the light come out from the other end of cable, which I was told I supposedly to see. Here is the output of my ifconfig vin# ifconfig -m ti0 ti0: flags=8843 mtu 1500 options=13 capability list: =13 inet6 fe80::2a0:ccff:fe73:3523%ti0 prefixlen 64 scopeid 0x4 inet 10.0.0.1 netmask 0xfffff000 broadcast 10.0.15.255 ether 00:a0:cc:73:35:23 media: Ethernet 1000baseSX (autoselect) status: no carrier supported media: media autoselect media 1000baseSX mediaopt full-duplex media 1000baseSX I'm sure my network card is working fine because I've used it before to collect other traffic. The network admin also told me there is nothing wrong with mirroring because he keeps seeing packet counts for that particular port increasing. the OS I'm running is FreeBSD 5.0 the network card is Netgear GA620 the switch is CABLETRON smartswitch 6000 I'm using a MTRJ-SC fiber optic cable like this one http://store.yahoo.com/fiberopticcables/mmdup625-mtsc.html to connect the switch port and my network card. The switch side is connected with MTRJ connector and the PC side is connected with a pair of SC connectors. Thanks Kun-chan From owner-freebsd-net@FreeBSD.ORG Sat Apr 12 04:19:25 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A270D37B404; Sat, 12 Apr 2003 04:19:25 -0700 (PDT) Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7768343FB1; Sat, 12 Apr 2003 04:19:24 -0700 (PDT) (envelope-from BelletJr@aol.com) Received: from BelletJr@aol.com by imo-d04.mx.aol.com (mail_out_v34.21.) id d.134.1e1ff9dc (18555); Sat, 12 Apr 2003 07:19:17 -0400 (EDT) From: BelletJr@aol.com Message-ID: <134.1e1ff9dc.2bc95035@aol.com> Date: Sat, 12 Apr 2003 07:19:17 EDT To: tlambert2@mindspring.com MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: AOL 5.0 for Windows sub 116 cc: current@freebsd.org cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 11:19:26 -0000 >Dans un e-mail dat=E9 du 11/04/03 23:21:55 Paris, Madrid (Heure d'=E9t=E9),= =20 tlambert2@mindspring.com a =E9crit : > >> >Because it can't detect an infinite routing loop. >>=20 >> Then why can't it detect an infinite routing loop? :) It does not impleme= nt >> the classic three-way handshake of a TCP connection establishment?? > >It sends SYN and waits for SYN/ACK before sending an ACK. The wait >is indenfinite, unless the machine receives an ICMP "host unreachable" >or similar connection reject packet. > >Most likely, ICMP is disabled somewhere between you and the >other end. Probably at your firewall. You should look at a >tcpdump of the traffic between the two endpoints which occurs >during the connection request, to find out for sure. If you >don't like raw tcpdump (or can't read it easily), then use >"ethereal" from ports. > >As to why it can't detect it without the ICMP, it's because it's >not possible to compute transitive closure over the graph of your >local routing table, and all the routing tables between you and >the other end, because the memory isn't local. 8-) 8-). > > >> If this is the case, I think the man page is not precise enough. It state= s >> "If the socket is of type SOCK_STREAM, this call attempts to make a >> connection to another socket" and later on "The connect() function return= s >> the value 0 if successful". > >You're mixing up two different usages of connect(). > > >> BTW we can imagine that the majority of programs aren't crafted to handle >> this case. > >Probably not... the majority of programs probably assume that >your network is set up correctly. 8-). > >> Have a look for example to the simple "daytime.c" program from the >> developper handbook. It just doesn't do anything if time.nist.gov is >> unreachable because of an infinite routing loop. > >I still don't know what you mean by "infinite routing loop"; there's >really no such thing. If you try to insert one on a single host, >the insertion attempt that would cause the loop will be rejected by >the "route add". It's a radix tree; being hierarchical, it can't >loop, since the idea of a loop is not supported by the data structure. > >The only purpose of the routing code is selection of "next hop", and >that dictates "interface to use". And that's all it does. > >It's up to intermediate hosts to indicate route failures via ICMP >messages (Internet Control Message Protocol). > >If you disable ICMP, be ready to have your foot shot off. > >-- Terry Thank you Terry for your instructive explanation (though Barney has found it= =20 seems to be a real bug ;-). The infinite loop that seems to exist when tracerouting happens while I try=20 to access an Internet host from my provider network without having=20 authenticate before. Not a usual set up, but it was just a test... In this case, after a few hops, traceroute seems to show packets exchanged=20 indefinitely between 2 interfaces. >You're mixing up two different usages of connect(). Honestly, I don't think so. The RETURN VALUES section relates to all socket=20 types that can be used, I hope :) From owner-freebsd-net@FreeBSD.ORG Sat Apr 12 04:19:30 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1661337B404 for ; Sat, 12 Apr 2003 04:19:30 -0700 (PDT) Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B23343F75 for ; Sat, 12 Apr 2003 04:19:29 -0700 (PDT) (envelope-from BelletJr@aol.com) Received: from BelletJr@aol.com by imo-d04.mx.aol.com (mail_out_v34.21.) id e.bb.3035e2d0 (18555); Sat, 12 Apr 2003 07:19:18 -0400 (EDT) From: BelletJr@aol.com Message-ID: Date: Sat, 12 Apr 2003 07:19:18 EDT To: barney@pit.databus.com MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: AOL 5.0 for Windows sub 116 cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 11:19:30 -0000 >Dans un e-mail dat=E9 du 12/04/03 00:21:06 Paris, Madrid (Heure d'=E9t=E9),= =20 barney@pit.databus.com a =E9crit : > >On Fri, Apr 11, 2003 at 01:14:15PM -0400, BelletJr@aol.com wrote: >> >> Why does not connect(2) return any error when trying to connect to a=20 host >> >> unreachable because of an infinite loop in the routes? No time-out=20 occurs=20 >> and >> >> the value 0 is returned by connect(2). >> >> My test was done with TCP/IPv4. > >Well, after actually looking at this, I believe it's a bug, in both >current and stable. The following patch appears to fix it: > >--- ip_input.c.orig Wed Apr 9 14:07:16 2003 >+++ ip_input.c Fri Apr 11 17:54:11 2003 >@@ -1696,7 +1696,7 @@ > 0, EMSGSIZE, EHOSTDOWN, EHOSTUNREACH, > EHOSTUNREACH, EHOSTUNREACH, ECONNREFUSED, ECONNREFUSED, > EMSGSIZE, EHOSTUNREACH, 0, 0, >- 0, 0, 0, 0, >+ 0, 0, EHOSTUNREACH, 0, > ENOPROTOOPT, ECONNREFUSED >}; > =20 >I'll file a PR. >By the way, the reason programs appear to do nothing after hitting the >problem is that they get SIGPIPE when trying to write on the socket. And if they just read from it, they just don't see anything (or perhaps they= =20 get a signal discarded by default, but I haven't verified that). From owner-freebsd-net@FreeBSD.ORG Sat Apr 12 09:49:25 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C45F937B401; Sat, 12 Apr 2003 09:49:25 -0700 (PDT) Received: from calis.blacksun.org (calis.blacksun.org [216.254.108.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2614243F3F; Sat, 12 Apr 2003 09:49:25 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1001) id B8DCC17060; Sat, 12 Apr 2003 12:52:48 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id B72341705E; Sat, 12 Apr 2003 12:52:48 -0400 (EDT) Date: Sat, 12 Apr 2003 12:52:48 -0400 (EDT) From: Don To: BelletJr@aol.com In-Reply-To: <134.1e1ff9dc.2bc95035@aol.com> Message-ID: <20030412123544.B4056@calis.blacksun.org> References: <134.1e1ff9dc.2bc95035@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: tlambert2@mindspring.com cc: current@freebsd.org cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 16:49:26 -0000 > Thank you Terry for your instructive explanation (though Barney has found it > seems to be a real bug ;-). > The infinite loop that seems to exist when tracerouting happens while I try > to access an Internet host from my provider network without having > authenticate before. Not a usual set up, but it was just a test... > In this case, after a few hops, traceroute seems to show packets exchanged > indefinitely between 2 interfaces. It is not the responsibility of TCP/UDP to report a routing problem. When the TTL on a packet reaches 0, (Due, for example, to a routing loop) an ICMP message is generated to report a "TTL Expired in Transit" message: ICMP Type 11. If the host does not receive this message, then the only thing connect() can do is timeout. In that case connect() should return -1 and errno should return [ETIMEDOUT] or [ENETUNREACH] (I have no idea which one). If you are allowing the necessary ICMP traffic, well, then there is a problem. Forgive me if I have no idea what I am talking about. -Don From owner-freebsd-net@FreeBSD.ORG Sat Apr 12 09:58:55 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 833AE37B404; Sat, 12 Apr 2003 09:58:55 -0700 (PDT) Received: from calis.blacksun.org (calis.blacksun.org [216.254.108.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0441943FBF; Sat, 12 Apr 2003 09:58:55 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1001) id DF8301705E; Sat, 12 Apr 2003 13:02:18 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id DBFF017054; Sat, 12 Apr 2003 13:02:18 -0400 (EDT) Date: Sat, 12 Apr 2003 13:02:18 -0400 (EDT) From: Don To: BelletJr@aol.com In-Reply-To: <20030412123544.B4056@calis.blacksun.org> Message-ID: <20030412125908.G4156@calis.blacksun.org> References: <134.1e1ff9dc.2bc95035@aol.com> <20030412123544.B4056@calis.blacksun.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 16:58:55 -0000 > ICMP Type 11. If the host does not receive this message, then the only > thing connect() can do is timeout. In that case connect() should return -1 > and errno should return [ETIMEDOUT] or [ENETUNREACH] (I have no idea which > one). Actually if ICMP is not working, it should return [ETIMEDOUT]. If ICMP is working, I am not sure which of those errno value would be returned. This is just a guess based on the information in connect(2). -Don From owner-freebsd-net@FreeBSD.ORG Sat Apr 12 19:32:59 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D20537B401 for ; Sat, 12 Apr 2003 19:32:59 -0700 (PDT) Received: from brainlink.com (mail.brainlink.com [66.228.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51FC143F75 for ; Sat, 12 Apr 2003 19:32:58 -0700 (PDT) (envelope-from anthonyv@brainlink.com) Received: from [24.185.4.7] (account anthonyv HELO brainlink.com) by brainlink.com (CommuniGate Pro SMTP 3.5.3) with ESMTP id 19155985 for net@freebsd.org; Sat, 12 Apr 2003 21:32:57 -0500 Message-ID: <3E98CC57.8010101@brainlink.com> Date: Sat, 12 Apr 2003 22:32:55 -0400 From: Anthony Volodkin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: net@freebsd.org References: <200304112303.50839.pblok@inter.NL.net> In-Reply-To: <200304112303.50839.pblok@inter.NL.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: routing a broadcast over a gif tunnel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2003 02:32:59 -0000 Peter J. Blok wrote: >Hi, > >I need to fool a PC package. The package is searching for a server responding >to a broadcast on port 56415. > >That server is across an ipsec/gif tunnel. How can I bridge that particular >packet towards the segment at the other end. > >I have tried various ipfw fwd rules and ipfilter redirection, but none of them >works (because the other segment is not locally available). > >Peter >_______________________________________________ >freebsd-net@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-net > > >To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > Hey, I recently implemented something similar in order to get games to work over a PPTP VPN setup. Check out my document here: http://non-standard.net/freebsd/game-vpn/game-vpn.html -Anthony From owner-freebsd-net@FreeBSD.ORG Sat Apr 12 20:21:47 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1714037B401 for ; Sat, 12 Apr 2003 20:21:47 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DBB043FBF for ; Sat, 12 Apr 2003 20:21:46 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h3D3LfA7042220; Sat, 12 Apr 2003 21:21:41 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 12 Apr 2003 21:20:59 -0600 (MDT) Message-Id: <20030412.212059.42399637.imp@bsdimp.com> To: barney@pit.databus.com From: "M. Warner Losh" In-Reply-To: <20030413030500.GA64896@pit.databus.com> References: <109.225ca595.2bc723f2@aol.com> <20030412.204912.76964336.imp@bsdimp.com> <20030413030500.GA64896@pit.databus.com> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2003 03:21:47 -0000 In message: <20030413030500.GA64896@pit.databus.com> Barney Wolff writes: : On Sat, Apr 12, 2003 at 08:49:12PM -0600, M. Warner Losh wrote: : > In message: <109.225ca595.2bc723f2@aol.com> : > BelletJr@aol.com writes: : > : Why does not connect(2) return any error when trying to connect to a host : > : unreachable because of an infinite loop in the routes? No time-out occurs and : > : the value 0 is returned by connect(2). : > : > Hmmmmm, you are correct. I was sure that you were nuts, but on : > -current the following program returns no error at all... Telnet : > shows the same behavior. This is clearly wrong. : : It's not just current; stable behaves exactly the same. The problem is : that the icmp time-exceeded packet gets translated into an error code : of 0, which confuses things. I've filed a PR with a suggested fix: : http://www.freebsd.org/cgi/query-pr.cgi?pr=50839 Ah. I see. I wonder if any of the net folks can review this... Warner