Random Disconnect Issues
-
Are your wan ip's dynamic? most multi ip setup from one provide there would be only one physical line to pfsense with multi ip's that one can assign with virtual ip in pfsense.
The reason i said you should ping from pfsense was to check the line out but still keep every thing connected.
-
Ok,
After all last night, and early into today, i have not had one single disconnect issue when plugging directly into the modem, using both the usb port, and the ethernet port, so the modem appears to be functioning correctly.
As for your question Perry, yes, the wan ip's are dynamic. I have been unable to get logged into the gui while the connection dropped to see if pfsense can still ping out, but i will keep trying that.
-
Upgrade to a recent testing snapshot: http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/updates/
-
Alright i just upgraded to the lastest snapshot. Will keep you all updated.
Thanks again for all the great support. None of you all have to do this, so thanks again.
-
Ok,
I just upgraded to the most recent testing snapshot available, and still getting the same thing as before. Did i miss a step in configuring pfsense for a multiwan setup? I figured i could just add the two additional wan interfaces, and then route the traffic how i want using firewall rules.
-
Thought i would give an update, hopefully someone has a few more ideas for me to try. I took out the two nics that i was using for my multiple wans, and installed pfsense again using one interface for the lan, one for the wan, and one for my wireless network. After 2 days of this, i haven't had one disconnection issue. So the problem only occurs when running multiple wans.
-
I've changed my setup at home so i got 2 dynamic ip's from the same modem going to the pfsense box. Atm i do get a lot of those arp messages but no disconnect so fare. From what i can find on the web it shouldn't be a problem.
To get rid of the messages look here http://freebsdhowtos.com/102.html
Replace your wan nic's ( intel is best ).That is what i would do at this point.
-
Yah, i don't mind the messages haha. One thing i did realize was the two wan nic's i was using were both realtek gigabit nic's. So i'll throw in a couple 100Mb intel cards see if that fixes the issue.
-
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.