[SOLVED]PPPoE unstable in 2.0-RC2
-
does the connection drop soradically or under heavy load?
try setting the mtu to 1492 on the interface the modem is connected to.
-
does the connection drop soradically or under heavy load?
try setting the mtu to 1492 on the interface the modem is connected to.
I see the connection drop under heavy load mostly..
I always set the MTU to 1492 by manual according to ISP's regulation. -
how is memory usage and cpu utilization when you saturate the dsl line? is enough memory and cpu left?
I used pfsense 2.0 beta and 2.0RC1 with a 16/1 dsl line over pppoe for about 4 months and it worked flawlessly.
what brand is the ethernet port your dsl modem is connected to? do you have the possibiity to try out a different interface brand (e.g. Intel)?
-
After I exchange the ADSL modern with my ISP, it seems everything working fine now.
I have tried to use the new modern with heavy load traffice for serveral hours and there is no disconnect and a little packet loss.
So I think the problem is due to ADSL modem..
Thanks for your time a lot:)
-
ADSL modern
or
ADSL modem?
-
Good for you, I replaced my modem and thought things were fine and dandy. Three days later multiple disconnects, your problem may be fixed but PPPoE is not. Someone recently on twitter went back to 1.2.3 because of these PPPoE disconnects. I just wished I could of helped the developers better on this issue, and I am sure we all wished that. It seems like this error is a show stopper for people so they quickly make a change because it is too risky to troubleshoot in a production environment.
Version 1.2.3 works in all PPPoE environments 2.0 still has the issue.
I still love pfSense and would not think of using anything else, I just hope we can get to the bottom of this.PPPoE issues:(
https://twitter.com/germanshepherd/status/84476628671016962
https://twitter.com/germanshepherd/status/84695254736969728
https://twitter.com/germanshepherd/status/84694304290906112 -
-
Good for you, I replaced my modem and thought things were fine and dandy. Three days later multiple disconnects, your problem may be fixed but PPPoE is not. Someone recently on twitter went back to 1.2.3 because of these PPPoE disconnects. I just wished I could of helped the developers better on this issue, and I am sure we all wished that. It seems like this error is a show stopper for people so they quickly make a change because it is too risky to troubleshoot in a production environment.
Version 1.2.3 works in all PPPoE environments 2.0 still has the issue.
I still love pfSense and would not think of using anything else, I just hope we can get to the bottom of this.PPPoE issues:(
https://twitter.com/germanshepherd/status/84476628671016962
https://twitter.com/germanshepherd/status/84695254736969728
https://twitter.com/germanshepherd/status/84694304290906112I am having the same problem with RC3. When will this get fixed?
-
I also have been dealing with this problem for months of PPPoE being unstable. This is why in a previous post I mention that I am switching to static DSLs so I can be done with PPPoE connections.
I would like to note however that the October 18th snapshot worked with my PPPoE connections perfectly. The problem came back for me when I upgraded to the latest snapshot in early June and the old problem of PPPoE from earlier than October 18th came back again. I would have switched back to the older snapshot but could not find it. So for weeks I updated to the latest snapshot last month trying to fix the problem, with no luck, hence deciding to change my DSL connections with the ISP.
My posts often are about load balancing but the essential problem is that PPPoE has been unstable making the loadbalancing to not function.
1 problem is they appear to go down and another is they are constantly gathering data on the dashboard.
I am adding this so people know others are having issues with PPPoE as well, but as I said I am switching my connections so I don't use PPPoE anymore.
-
I would like to note however that the October 18th snapshot worked with my PPPoE connections perfectly. The problem came back for me when I upgraded to the latest snapshot in early June and the old problem of PPPoE from earlier than October 18th came back again.
And that is why it pays to keep up to date with snapshots. If you could point at one specific snapshot that supposedly broke something, it's much easier to find a problem than somewhere in the vast difference between October and June. Thousands of commits and changes between there, and no easy way for anyone to reproduce it makes it that much harder.
-
I understand and I apologize, I got everything working and left it alone for 6 months. Did not know until a few weeks ago.
