Random Disconnect Issues
-
Still no disconnect even with same subnet and gateway. If you could post or pm me your firewall and nat -rules i'll clone your setup :)
-
Alright, we are swamped at work right now so i will try to find a free minute, or i'll post my setup later this evening..
I will add that even with leaving all the rules set to the default routes, and not installing any additional packages, i still got the disconnect issues.
-
Well right now, i have nothing setup on the firewall, simply the default rule for the lan connection. No packages installed or anything. No port forwarding rules, or special traffic shaping rules, etc. Basically the default install of pfsense. The dns forwarder is enabled for the wireless interface, as is dhcp relay, but thats it…
-
I haven't had a chance to setup a replica of your environment yet but will soon (hopefully tonight, but no promises).
Keep posting back with updates when you have them.
-
Well another update.
I had an old pentium 3 computer laying around at home, so i went ahead and threw pfsense on it, along with a few extra nic's.
Set it up for 1 lan interface and 3 wan interfaces. Right off the bat, i started experiencing those same messages in the firewall logs, and experiencing disconnection issues during the same time frame.
The internet service providers are (if it helps at all, since the bluegrass isn't to far away from the buckeye haha):
Time Warner (Road Runner), and Cincinnati Bell (Zoomtown).
We are also working off a t1 line at my other job but right now that is running off a pix, which i personally don't like haha (pfsense migration soon hopefully).Both pfsense boxes connecting to road runner and cincinnati bell are both operating off of dhcp leases, nothing is static. Both pfsense boxes are running intel nic's.
-
:o ::) Now wan2 also is the default gateway ups!! thought that the default gateway was locked to the wan interface
-
yah that threw me for a loop in the beginning. The gateway floats to all three interfaces for me if if leave it to default, unless i set it to wan2 or wan3.
-
Well because of all the disconnect issues i had to throw an additional 2 pfsense boxes into the network for now. Would make my life easier if they would break down and just pay a few additional bucks for a few static addresses but that would be too easy i guess? I still have the box running with 3 wan interfaces for some more testing. If it would help the dev's out at all, if it appears to be more than just me having the problem, i would be willing to give remote access to the box if that would be helpful. Lemme know
-
What I have seen here is that SnapShot 06-06-2007 works perfectly without any disconnects.
-
Yah, and i know others have as well… and i am certainly not suggesting a bug. I'm the last person who should be thinking that, since i don't have half as much knowledge about this as you all... I'm just totally clueless because i duplicated it with two different isp's and diff. hardware.
-
Hey Mr. cmb, just checking up, wondering if you have found time to clone my setup yet?
thanks,
-
Well i have an update… I'm an idiot for overlooking this, but it appears there is a problem when using the built in ethernet adapter as the default wan adapter...
I re-installed pfsense without enabling the built-in ethernet adapter and that seems to have fixed it on both boxes i have pfsense installed on.. I still get the, kernel: arp: 72.49.176.xxx is on dc0 but got reply from xx:xx:xx:xx:xx:xx on dc1, once every 4 hours, but it no longer drops the connection.
Does this seem normal? but boxes are dell's, with built in intel chips, so i figured that would be fine?
-
Which type of built in Intel chips?
See this google search: http://www.google.com/search?q=dcgdis.ThisIsZip&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a
-
I'll try that patch tonight see if it helps at all.
In the one machine, it's a dell dimension 9100, with an onboard nic of: Intel (R) PRO/100 VE
The other machine, is actually not an intel chip.
Dell dimension 8400, with an onboard nic of: Broadcom 57XX -
Glad to hear ;)
Everyone note that this ONLY effects an 82573 NIC, so make sure of
that before anything else.Don't apply the patch before you have confirmed it's that one you have :)
There ain't anything wrong with that arp messages….i posted a link sometime ago
-
Yah, i just realized that right after i made that post haha…
Looks like it's time to invest in a couple dual port intel chip... to make up for the stupid onboard chip...
Yah as long as i dont get d/c'd, i could give a hoot less about the arp messages :-D.
-
I know you all are getting sick of my posts.. Figured i would post this to help someone in the future even tho i know it has already been suggessted once before.
One of the machines at are work experiencing the issue, just had a bios update released for the motherboard, so we figured what the hell. After the bios update, the disconnection issues went away! So another thing to keep in mind. Thanks again for all your help fellas