From owner-freebsd-net@FreeBSD.ORG Sat Jun 22 10:26:33 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 72596D20 for ; Sat, 22 Jun 2013 10:26:33 +0000 (UTC) (envelope-from carsten@innolan.dk) Received: from mail.innomanslan.tf (0126800067.1.fullrate.dk [95.166.204.165]) by mx1.freebsd.org (Postfix) with ESMTP id EE46C16F5 for ; Sat, 22 Jun 2013 10:26:32 +0000 (UTC) Received: from [192.168.44.228] (unknown [192.168.44.228]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: carsten@thehawk.dk) by mail.innomanslan.tf (Postfix) with ESMTPSA id 3B7CC12C2CA3; Sat, 22 Jun 2013 12:18:25 +0200 (CEST) Message-ID: <51C579F0.3020701@innolan.dk> Date: Sat, 22 Jun 2013 12:18:24 +0200 From: Carsten Sonne Larsen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130611 Thunderbird/17.0.6 MIME-Version: 1.0 To: Adam Hunt Subject: Re: Flapping WAN with axe interface References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, wpaul@windriver.com X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 10:26:33 -0000 I used to run a setup with a D-Link DUB-E100 ver. B adapter on pfSense also using it for a DCHP WAN connection. I had a similar issues. Every time I unplugged the DUB-E100 things would work smoothly again. Now Im using the D-Link adapter on a 8.3-RELEASE and am still having issues once in a while. Im not a hardware guy but I think the D-Link simply just have a buggy hardware or somehow have some hardware restriction preventing it to be used as nothing else but an extra NIC in a laptop - I remember one of the issues was the NIC not being able to allocate buffer space. /carsten On 06/22/2013 03:11, Adam Hunt wrote: > I just replaced my old WRT54GS running DD-WRT at home with a proper pfSense > firewall. The only real problem I've had is my WAN link to Comcast goes > down at least every twelve hours. I used to think it was almost exactly > every twelve hours (leading me to think Comcast's DHCP server hated me) but > I have since noticed that the WAN flaps at less predictable intervals. I > can't figure out if it's related to DHCP or not. I can say that nothing out > of the ordinary was going on on my network when this happens. It happens > whether or not anyone is actively using any of the systems on the network. > It can happen when I'm working, browsing, and streaming Netflix or it can > happen everyone in the house is asleep and most everything is down or idle. > > One thing that I have learned since I starting this adventure is that it's > in some way related to my D-Link DUB-E100 rev B1 USB NIC. I know that USB > isn't the preferred interface for networking but it's what I had. I'm > currently using a 3.4 GHz P4 Prescott Dell OptiPlex GX620 "ultra small form > factor" desktop for my firewall and it doesn't have any PCI/PCIe expansion > so I'm left with USB. For some reason I had a D-Link DUB-E100 ver. B > (AX88772) adapter laying in a box, since it was on the 8.3 HCL I decided to > give it a try. > > Below you'll find the my system, dhcp, and gateway logs for the time that > the link goes down. If you need any other logs or other information I'll be > more than happy to provide it. > > system.log:http://pastebin.com/mxuXd55w > dhcp.log:http://pastebin.com/tvAihELQ > gateways.log:http://pastebin.com/2cZqjJBa > > > So, after watching the logs, thinking, talking on IRC, checking with the > pfSense forums I decided to perform a simple experiment. I swapped the > interfaces, I connected my DOCSIS bridge to the bge0 onboard interface, and > hung my LAN off the USB NIC. Ever since swapping the interfaces everything > has been quiet. I haven't seen a single error in any of my logs. > > What are your thoughts? Is is a Comcast issue, an issue with the DOCSIS > bridge, an axe bug, a USB bug, some combination of issues, or something > different entirely? I realize I could just leave everything as is but I'd > like to help solve this little mystery. Also, years ago I was taught it's > bad form not to report potential bugs. > > Thanks for your help. > > --adam > _______________________________________________ > 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"