I haven't closely followed this particular thread, but a couple months
back I got some pcap files from one of the people with this issue. It
got buried in my inbox, and I never got back around to it until now.
The capture from that time, with the same issue, shows ARP working fine,
traffic going out fine, but it never sees any responses. SYN's go out
and never see a SYN ACK, ICMP echo requests go out and never see a
reply. As is typical with cable modems, there were over 100,000 ARP
requests are replies in the capture (with a couple dozen non-ARP frames).
So I have no idea what's happening - it definitely looks like an ISP
issue since the traffic is going out properly and never sees replies,
ARP is working fine, and the cable modem is obviously up and the NIC is
receiving traffic from it fine given the amount of ARP frames in the
capture. Rebooting does temporarily fix it, which makes absolutely no
sense. Given that it's limited to this one particular ISP, and there
doesn't seem to be any other ISP in the world that has the same problem,
it definitely looks like something strange with their network. The
captures don't show anything to indicate what that might be.
Tortise wrote:
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 <mailto:[EMAIL PROTECTED]>
*To:* [email protected] <mailto:[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 <mailto:[EMAIL PROTECTED]>
*To:* [email protected] <mailto:[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]
<mailto:[EMAIL PROTECTED]>> wrote:
On 9/2/07, Tortise <[EMAIL PROTECTED]
<mailto:[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]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
