Random Disconnect Issues
-
Well after i swapped out all of my wan nic's with 10/100 Mb intel nics, i still experienced the same issue..
The problem is definitely somewhere within my pfsense box.When i plug into the unmanaged switch in front of the pfsense box, i am able to lease public ip addresses from isp without a problem, and experience 0 disconnect issues.
When i run pfsense with a single wan interface, still behind the unmanaged switch, i all experience 0 disconnect issues.
As soon as i put two additional wan interfaces in, i start experiencing d/c issues. One thing im not sure if i mentioned or not was that i had to set both my lan and wireless interface to send all traffic through my opt3 (WAN3) interface, since the default routing would float between the 3 different wan interfaces, although i doubt that will help you out any…
I dunno, im out of ideas... Anymore ideas?
Also, might i mention, i tried installed the most recent snapshot released yesterday (june 4th).
-
Still no disconnect here. http://www.mail-archive.com/support@pfsense.com/msg09832.html uses the same modem as i.
If you have a spare router you could add it in front of pfsense
+–---router1---- wan2
|
modem-----switch---+---------------- wan
|
+-----router2---- wan3Else i only see a move to static ip's
-
May i ask how your setup is for your multi-wan setup? Does your modem have multiple ethernet ports or do you have a router or switch in front of pfsense?
-
Got a hub in front
+–-wan
|
modem ---- hub---+---wan2 -
Does it sound possible that:
The hub i have in front of my pfsense box works fine if i plug clients directly into it? They get public ip addresses without disconnect issues.
So could the hub be too crappy to be able to handle what im trying to do with pfsense?
-
Well hub sucks :) but I wouldn't bet that much on it to be the problem. How many clients do you have in you lan?
What does your system show in status -> interfaces
wan
In/out errors 0/0
Collisions 220wan2
In/out errors 0/0
Collisions 638Did you test with a router in front?
-
Agreed, dumb switches suck, but since we only have dynamic addresses coming it, it has to do for now…
For all three interfaces:
In/out errors: 0/0
Collisions: 0/0
i have approximately 20 clients on our lan/wireless.
I believe we have an old linksys router laying around somewhere, that i could hook up in front of it. I'll do that later tonight after everyone gets off..
Thanks again Perry
-
I'm beginning to wonder if there are issues with multiple interfaces plugged into the same broadcast domain.
Just to make 100% sure I understand what's happening, bgbearcatfan, you have multiple WAN interfaces all plugged into the same switch, right? And if you only use 1 WAN you have no problems, but if you bring up those multiple WAN's, you have issues with it disconnecting, right?
-
You got it!
GO BEARCATS! haha…
-
Ok, I'm going to attempt to replicate this problem because it seems you're not the first that's having it.
GO BEARCATS! haha…
;D For context for others, this is in reply to a PM. Bearcats + he's coming from uc.edu IP space, I PM'd him that he's lucky we'll support a UC fan. :) pfsense "headquarters" (where the two founders live) is in Louisville, and we're both louisville.edu fans. For those out of the loop on US college athletics, Cincinnati and Louisville have a rivalry dating back before any of us were alive, especially basketball, and (American) football. :)
-
Haha, but since you all made such a wonderful product, i suppose us uc fans can forgive you haha.
Hey let me know if you want me to test anything for you. Tonight i just threw a different hub in front of the firewall, a bit higher quality one, so we'll see if it returns the same results.. Again let me know if u need anything from me mate.
-
Quick update. As of yesterday around 11 p.m. or so, we have had no disconnect issues, since replacing the unmanaged switch (glorified hub, blah). It's still to early to say the problem has been resolved, but, normally we would have experienced atleast 15 disconnects within that time frame… Doesn't make much sense to me, but yah...
An additional update, i am still seeing those kernel: arp: messages in the system logs but i am working remotely this afternoon so i can't tell if they are disconnecting though or not, can let you know later this evening.
-
Well the new switch seemed to make a difference at first, but then back to it's old tricks again. I'm gonna try throwing a cheap router in front of pfsense tonight to see if that helps at all or not.
Sorry to bug you all with all these posts,,,i'm sure your getting annoyed. After throwing a router in front of the pfsense box, i'm still getting the same results… So i am all out of ideas... Let me know if anyone else has any ideas or input on this.
-
I have the same problem but I am only wit 2 interfaces (le0->WAN and le1->LAN).
kernel: arp: 192.x.x.x is on le0 but got reply from 00:0c:29:da:90:a2 on le1I don't have problem with chat software such as: kopete, game and skype but I have issue with loading of lots of web sites.
When I try to open www.dir.bg (as an example) my status bar of my browser load to 80% round and so freeze.This is my configuration.
My box is Opensuse 10.2 in which there is VMware server.
On this VMware server there are 2 machines - pfsense and Windows XP. NIC adapters on these machines are bridged into the Opensuse 10.2 adapter on the same vmnet switch.pfsense is the router who have 2 adapters le0->WAN(the same subnet with main outgoing router of the company) and le1->LAN(the same subnet with internal network).
My real box with Opensuse and virtual Windows XP use pfsense for router and DNS.
The interesting is that Windows XP doesn't have any problems with Internet but linux does.
I'm sure there is no hardware problem, no DNS problem but I don't know where is the problem. This is my situation. Pleas help if you can. Thanks in advance! -
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