From owner-freebsd-bugs Fri Jul 6 7: 6:52 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.dwec.ru (mail.dwec.ru [194.84.175.18]) by hub.freebsd.org (Postfix) with ESMTP id 80DAC37B403 for ; Fri, 6 Jul 2001 07:06:45 -0700 (PDT) (envelope-from o.ivanov@dwec.ru) Received: (from root@localhost) by mail.dwec.ru (8.9.3/8.9.3) id SAA02858 for freebsd-bugs@FreeBSD.ORG.AVP; Fri, 6 Jul 2001 18:06:43 +0400 Received: from admin (gatekeeper.dwec.ru [194.84.175.20]) by mail.dwec.ru (8.9.3/8.9.3) with SMTP id SAA02842; Fri, 6 Jul 2001 18:06:42 +0400 Message-ID: <004901c10624$c7471bc0$080ba8c0@dwec.ru> Reply-To: "Oleg Y. Ivanov" From: "Oleg Y. Ivanov" To: "Donskoy V." Cc: References: <200107061042.f66Agow06507@vspu.ru> Subject: Re: kern/28768 : The system doesn't get connects on one of his addreses. Date: Fri, 6 Jul 2001 18:03:10 +0400 Organization: Daewoo Electronics, Moscow MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You must break your network into subnets or use bridging . It's not FreeBSD , you must read more about IP basics. ----- Original Message ----- From: Donskoy V. To: Cc: Donskoy V. Sent: Friday, July 06, 2001 2:42 PM Subject: kern/28768: The system doesn't get connects on one of his addreses. > > >Number: 28768 > >Category: kern > >Synopsis: The system doesn't get connects on one of his addreses. > >Confidential: no > >Severity: serious > >Priority: high > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Jul 06 03:50:01 PDT 2001 > >Closed-Date: > >Last-Modified: > >Originator: Donskoy V. > >Release: FreeBSD 4.3-STABLE i386 > >Organization: > VSPU > >Environment: > System: FreeBSD bsd.vspu.ru 4.3-STABLE FreeBSD 4.3-STABLE #3: Thu May 17 16:36:47 MSD 2001 root@bsd.vspu.ru:/usr/src/sys/compile/VSPU i386 > Network card: Intel EtherExpress 100+, Allied Telesyn AT-2500TX (on Realtek 8139). > > >Description: > > We have router on FreeBSD 4.3-stable with 2 network cards (IP only). > The networks are divided on two parts: one card (fxp0) has addreses from > 1 to 126, the other card (rl0) has addreses from 129 to 254. The first > interface has address .2, the second card has .129. > > fxp0: flags=8843 mtu 1500 > inet xxx.xxx.xxx.129 netmask 0xffffff80 broadcast xxx.xxx.xxx.127 > ether 00:a0:c9:6e:dc:80 > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX > rl0: flags=8843 mtu 1500 > inet xxx.xxx.xxx.2 netmask 0xffffff80 broadcast xxx.xxx.xxx.127 > ether 00:a0:d2:a4:19:f9 > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX > > Routing tables > Internet: > Destination Gateway Flags Refs Use Netif Expire > default xxx.xxx.xxx.5 UGSc 43 7708 rl0 > 127.0.0.1 127.0.0.1 UH 2 9310 lo0 > xxx.xxx.xxx/25 link#2 UC 1 0 rl0 => > xxx.xxx.xxx.2/32 0:a0:d2:a4:19:f9 ULS2c 1 0 lo0 > xxx.xxx.xxx.5/32 0:4:27:19:82:e0 ULS2c 1 0 rl0 > xxx.xxx.xxx.127 ff:ff:ff:ff:ff:ff UHLWb 0 348 rl0 > xxx.xxx.xxx.128 ff:ff:ff:ff:ff:ff UHLWb 0 1 fxp0 => > xxx.xxx.xxx.128/25 link#1 UC 2 0 fxp0 => > xxx.xxx.xxx.129/32 0:a0:c9:6e:dc:80 ULS2c 0 0 lo0 > xxx.xxx.xxx.132/32 0:a0:d2:a4:1a:4b ULS2c 1 4 fxp0 > xxx.xxx.xxx.255 ff:ff:ff:ff:ff:ff UHLWb 1 1039 fxp0 > > > Using the computer (address .132) we don't meet any mistakes in > connecting with other addresses on network 1-126 (and at Internet). When > we connect to the router (address .2, other network cards) we don't > meet any problems in connecting too. When we are trying to connect to > the router on address his interface (.129), we can not do this. Ping on > .129 work, but any TCP connect was fail. > > When I used a network scaner I noticed that the control sum in the packet > of the router wasn't correct (we always get mistake in the control sum if > the packet goes out from the address 129. The control sum of address .2 > is correct and computer connects). > > I changed the network cards by places but the mistake appears again > (address .129 isn't connected). > > Before upgrading of the system (4.3-release) we had no problems. > In May after first cvs there were no nistakes. But after June cvs the > system isn't work. > > Of course I made changes in system and kernel every time after cvs. Now > we have working system after cvs (with changes on current date) but > having old kernel and new modules. > > The cvs protocols have a lot of changes in network part. But I can't > believe that somebody could brake something in such place like the > routing and nobody could notice that... > > >How-To-Repeat: > I have only one router, so I don't know it. > > >Fix: > I don't know. > >Release-Note: > >Audit-Trail: > >Unformatted: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message