From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 21 06:50:22 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B8B416A4CE for ; Sat, 21 Feb 2004 06:50:22 -0800 (PST) Received: from chaos.evolve.za.net (chaos.evolve.za.net [196.34.172.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9B6143D2D for ; Sat, 21 Feb 2004 06:50:21 -0800 (PST) (envelope-from cole@opteqint.net) Received: from root by chaos.evolve.za.net with scanned-ok (Exim 3.36 #1) id 1AuYSS-0004po-00 for hackers@freebsd.org; Sat, 21 Feb 2004 16:50:20 +0200 Received: from [196.39.126.250] (helo=stalker) by chaos.evolve.za.net with asmtp (TLSv1:RC4-MD5:128) (Exim 3.36 #1) id 1AuYSR-0004pd-00 for hackers@freebsd.org; Sat, 21 Feb 2004 16:50:20 +0200 Message-ID: <002501c3f88a$91413190$4206000a@stalker> From: "Cole" To: Date: Sat, 21 Feb 2004 16:54:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by Opteq - www.optec.co.za Subject: Vlan Problem/Bug maybe X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 14:50:22 -0000 Hey I run freebsd 4.9-Stable. And i also use vlans and a program called freevrrp for redundancy. For freevrrpd to function, it needs to change the ether MAC addresses of the interfaces it is told to use. I found that if i assign it only to a vlan interfaces such as vlan0 or whatever, that it changes the ether MAC adddress of it fine. The problem then, is that no traffic is ever picked up by that interface after that. After a few dumps and stuff, i realised that it is using the new ether MAC address in the packets it sends out, which is now different from the parent NIC's ether MAC address. So somewhere along when the responses are sent back, they are not being handed back to the Vlan device. As soon as i changed the NIC's ether MAC address to match that of the new vlan ether MAC address, everything works fine again. Now this isnt really a feasible option. So i would like to know if there is anyone that could possibly help with some sort of patch to the vlan driver if_vlan.c so that when it has its ether MAC address updated, it also updates the ether MAC address of the parent device. Ive done a bit of looking and i see that somewhere in the vlan_start function inside if_vlan.c the ether MAC is being changed there, but i would also like to know how to send the new ether MAC address to the parent device driver and have it update itself. If there is a better list to send this too or if anyone could possibly help, it would be much appreciated. Thanx /Cole