From owner-freebsd-net@FreeBSD.ORG Fri Jun 17 13:41:13 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 19D6B16A41F for ; Fri, 17 Jun 2005 13:41:13 +0000 (GMT) (envelope-from meno.abels@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B237D43D5D for ; Fri, 17 Jun 2005 13:41:12 +0000 (GMT) (envelope-from meno.abels@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so732408wri for ; Fri, 17 Jun 2005 06:41:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UsRdu3Ahs1IL/GKW3jWR3M1gTwc/NMViGJ3JC5bJ9sr6XgbxAqCDPDBzJKCV5WJ0xezouVwZ6NHR7T9jkmDi0m6lqLJefFACLThzaW+rNbNS72wEYoPtmwXFMDDlrlJbz9dGHIFbDM6LvlbvhfD3gokK1Y+HdcyveVZXaaCx0wQ= Received: by 10.54.39.1 with SMTP id m1mr1102883wrm; Fri, 17 Jun 2005 06:41:11 -0700 (PDT) Received: by 10.54.25.64 with HTTP; Fri, 17 Jun 2005 06:41:09 -0700 (PDT) Message-ID: <344de2870506170641695a9385@mail.gmail.com> Date: Fri, 17 Jun 2005 14:41:09 +0100 From: Meno Abels To: Gleb Smirnoff , meno.abels@adviser.com, freebsd-net@freebsd.org In-Reply-To: <344de28705061706121fcf5040@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <344de287050617043219810b3@mail.gmail.com> <20050617125049.GB45094@cell.sick.ru> <344de28705061706121fcf5040@mail.gmail.com> Cc: Subject: Re: FreeBSD 5.4 802.1q and linux stalls X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: meno.abels@adviser.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 13:41:13 -0000 Sorry i doesn't saw your question regarding tcpdump. First thats quite complex to do there are usally 5000 packets per second out of the spread traffic. This causes tcpdump to real trouble it starts to drop alot of packets i tried but I found nothing. Which not mean there is nothing but....=20 I think the problem is not directly the switch on of the vlan, i think that the switch on of the vlan causes that the freebsd frames will be look different from that machine. I had a look to that but found also not anything reasonable. But the questi= on is where i should look. To the spread udp-broadcast's to the ganglia multicasts or the carp multicasts or the generic arp traffic or the generic tcp traffic. I have no idea. I'am also not very happy about my prediction about that the receiving of arp doesn't work. This based on tcpdump where i see that the linux is sending arp packets awa= y=20 but not receiving them. But if i look on the answering freebsd there is a answer packet generated and send out. Also i tried to setup arp static but that doesn't brings up the communication again. So there could be a different problem. On the other hand the linux is still working if there is no arp timeout/retry(aging) or arp -d done by hand. So the facts are still not really prooven. Meno 2005/6/17, Meno Abels : > no nothing like that. >=20 > Meno >=20 > 2005/6/17, Gleb Smirnoff : > > Meno, > > > > On Fri, Jun 17, 2005 at 12:32:37PM +0100, Meno Abels wrote: > > M> i have here a very strange problem which is in real a linux problem > > M> but it is triggered by freebsd. I run a lan on which are linux 2.6.8= (debian) and > > M> freebsd 5.4 systems are connected to a unmanaged gigabit switch. All= systems > > M> uses this gigabit adapter: > > M> Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet > > M> Everything works fine until i do on one freebsd box the following: > > M> ifconfig vlan0 172.20.21.1 netmask 255.255.255.0 vlan 2 vlandev re0 > > M> i just do this, there is nowhere any configuration for 802.1q on a= ny other > > M> machine on this lan. > > M> What is happen now the freebsd continues to run without any problem,= but > > M> all linuxs are stopping to understand any arp responses from a freeb= sd > > M> nor an other linux. > > M> So they stop to work over the time on this lan anymore. If I do > > M> "ifconfig vlan0 unplumb" > > M> it takes up to 10 minutes and the linux's are return to the working > > M> status as before > > M> the ifconfig vlan0... > > M> I didn't not have any clue which network packet could cause these be= havior in > > M> a linux but there has to be one. Does anybody as any idea? > > > > Try to tcpdump on linux when you create vlan on FreeBSD. Any unusual pa= cket > > at this moment? > > > > M> On that lan there is UDP-Broadcast(spread) and multicast traffic(gan= glia) > > M> also there are around 120 carp addresses configured on the 10 freebs= d boxes. > > M> Everything else is standard tcpip/nfs traffic. There is no firewall > > M> rules on the interfaces on thes linuxs or the freebsds. > > > > Any routing software? RIP or OSPF? > > > > -- > > Totus tuus, Glebius. > > GLEBIUS-RIPN GLEB-RIPE > > _______________________________________________ > > 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" > > >