I have two connections to Comcast through two different modems (their voip capable modem and their business modem - static IPs) at my house and have _never_ had an issue with the connection. The Comcast user with issues is likely a hardware issue.
I'm not sure I have anything more to add to David's issue though - it's obviously not hardware. Question for Chris on the trace. Does it show the upstream router sending arp requests for the local IP and getting a response? Not sure if there's a way to force a gratuitous arp in FreeBSD without installing some third party tool like nemesis, but that might be worth looking at I 'spose. --Bill On 9/3/07, Sean Cavanaugh <[EMAIL PROTECTED]> wrote: > > > David, > > sorry, I was referencing Lance in my response. Personally I am using a Dlink > DCM-202 on my comcast service. I also have it set up at another persons > house running on the small square ?motorola? cable modem with no issues > (actually used it to replace a crappy linksys router) also on comcast but in > a different county/service area. > > -Sean > > ----- Original Message ----- > From: Tortise > To: [email protected] > > Sent: Monday, September 03, 2007 4:33 PM > Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, > Intel Pro/1000GT NICs with 370M RAM > > > Sean > > I guess you saw we've gone down that road, the cards I am currently using > are in the subject line and would seem to be of the type you advocate, > however perhaps you were inquiring the NIC types used by Lance? Are you > also behind a Motorola SB 51xx cable modem? > > The fix I posted has now proven to perform the necessary rescue several > times. It is such a refreshing change to be off site running a terminal > session, to be cut out, and to know it will come back within a minute! > (Assuming the issue is the one that is the subject of this thread!) Its not > perfect but it is a significant advance! > > If I knew how to reference and extract the WAN driver type (e.g. em0) I > could have the script fully cross machine, so it might then be considered > for the image. So I don't have to add it in manually with every upgrade! > Even if it is there so that the appropriate CRON line would only remain to > be added or commented in. > > Kind regards > David Hingston > > ----- Original Message ----- > > > From: Sean Cavanaugh > To: [email protected] > Sent: Tuesday, September 04, 2007 8:11 AM > Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, > Intel Pro/1000GT NICs with 370M RAM > > > considering smoothwall is based on linux whereas pfSense is based on > FreeBSD, I lean towards it being a driver issue with your setup. using > cheapo cards like the linksys or Netgear ones can cause this. try and get a > higher level card like a 3com 3c905c or intel card. I personally run the > gigabit Netgear card with hardware offloading internally and a 3com WAN side > and it runs with zero issue. > > -Sean > > ----- Original Message ----- > From: Lance Peterson > To: [email protected] > Sent: Monday, September 03, 2007 2:28 PM > Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, > Intel Pro/1000GT NICs with 370M RAM > > > I'm a home user with a cable modem connected to a small firewall computer > built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense > installed. I started experiencing connection problems with computers > attached to this small network within 24 hours. I reloaded, reconfigured, > started and stopped services, etc. and nothing permanently fixed my > connection issues. Then I formatted and installed Smoothwall Express using > all the same hardware -- problem solved -- no more lost connections. > Definately seems like a PFSense problem, in my opinion. > > Sorry if this is a little off topic or already discussed, I just scanned > though these replies and wanted to post my experience with lost connections. > > > On 9/3/07, Bill Marquette <[EMAIL PROTECTED]> wrote: > > On 9/2/07, Tortise <[EMAIL PROTECTED]> wrote: > > > Thanks Bill > > > > > > They are static IP's, so I assume (you may know better?) DHCP lease > times are (or should be?) irrelevant. > > > > > > Not sure if this what you mean but this might answer? > > > > No worries, if it's static assigned and not a dhcp static assignment > > then you won't have the files I was looking for. Honestly not sure > > what else to look at here. This doesn't appear to be due to traffic > > inactivity. I'm not sure how any other system would work any better > > :-/ > > > > --Bill > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
