PPPOE DIE even on 3.13

sorry but i think you did not read our posts . the problem is not “pppoe disconnects”. the problem is : user is connect but no transfer and when user disconnect by hand and again connect the problem solves until next time . next time may be 30 seconds later or 1 day later.

The problem is solved when layer2 requests , already it is by means of neighbor, mac telnet, mac-winbox, etc. Of so many things that probe, a temporary, serious solution to arm(assemble) a programmed script who does a mac-ping every 5 second to the mac of every client, forcing to routeros to continue the communication in the layer2. The topic is that from console I believe that the mac-ping is not supported. We hope that this problem can be fixed, since our clients complain and it worsens the image of our company.

saludossss

I am not currently seeing this problem but I will throw a few observations in here. If I have a wireless client with a real crudy connection that drops a lot of packets I will see this problem where the PPPoE connection freezes. Typically you need to drop and restart the PPPoE client to solve it. Never looked into it extensively because a client with a very poor wireless connection like that needs it fixed anyway.

Perhaps thats what is being seen here?

Matt

It is supposed that on having done downgrade I lose the whole configuration? Maybe the momentary solution this in to use her 3.0rc14 … but theoretically we are losing all the propernesses up to(even) her(it) v3.13

Regards

pd: 3.0rc14 runs well on rb433ah? I have understood that alone works from the version 3.0

Hello
I’m having the same PROBLEM!!! and I said its in other post!!. Is exactly like all of you say, I client can work perfect and when it start have a lot of connections, the PPPoE Server close that connections, and the only way to solve this problems is to reconnect the user, but imagine, to explain it to all you client, they will kill as!!
Today I take our my PPPoE Server, that was an IBM Server, with all you want. And I remplace its with a RB 433 AH, and I solved that problems. The pppoe server doesn´t die, but a new problem appears. Its start assing IP that are used in other clients!! I solve a problem to go to another!!. The post of that problem is:

http://forum.mikrotik.com/t/pppoe-cant-assing-ip-it-alway-uses-ip-that-are-used/23551/1

For that that have the problem of PPPoE Die, please try changing the server for some RB. In my experience I have a RB433 AH, without change, with 130 simoultaneous clients, and the processor is in 35%, but with IP problems!!!
Well I hope it can help to solve the problem to MKT team, and MKT users
Thank, and if somenone know hao to solve the IP problems, please help me
Rafael Lore

I believe that it is not a problem of hardware. I have one rb433ah and one rb532r5 both with the version 3.13 and the two has the same problem. The pppoe client dies. It covers some perfectly, and others must reconnect. We say that to work with ip fixes in the troubled clients up to(even) so much one finds a solution. This produces a security breach, since we have to assign ip hinge to interface wireless and generally not all the clients support wpa. For which it is necessary to work without encript or with wep that already we know poor that is.

saludosss

Hello, I made some changes but the problem is still present but I’ve noticed some special things:
around 4 to 5 clients remain connected all the time ( 24Hours now) other disconnects frequently, but the clients that today remained connected yesterday did NOT, it seems that the first 4 to 6 clients that will connect first, remain connected without problems, independently of client brand or setups.
Now I am going to disconnect all clients and reconnect them manually in another order; the disconnections takes place in the hottest ours of the day ( from 11 to 16 local time )
Regards
Alessandro

No no!!
This reemplace only extended the agony by three hours, and the crashed!!! If I restarted the RB, died again, so I came back to my old configuration!!
The problems appears to me, when I use Public IP Address, but if I give my client Private IP Address and then make a masquerade in the Server, it works PERFECTLY!! But whrn I tried to work with Public IP Address it crash!!! I clarified that I’m ussing in both case the RouterOS v 3.13
This problems appear to you when you are working with public or private IP?
He Normis, its is possible that can be a problems in this version of RouterOS, or we contineous trying to solve it?
Thanks
Rafael Lore

As i said before , this problem occurs very randomize . maybe it does not happen in a day and some times it happen each 30 seconds . so if you think you could solve the problem , please wait 2 or 3 days and if problem really does not came back then say your solution here .

3.14rc1 is out now

Thanks but nothing about pppoe problems in Changelog . so what does it mean !!!

Normis ¿ they have patched the kernel? If it is not this way, that are extracted the new version, it was sounding nicely but it does not change anything. That seems to be troublesome, but it is worrying to have this problem and mas when there are people who pays for our services. :slight_smile:

Regards

That is true!! there is not solution to ower problem!! If you want normis I give full access to a MKT that present its problems. I think that the problems is the communication between MKT and Radius Server
Thanks
Rafael Lore

Already probe disabling the autentificacion radius and the accounting from ppp aaa and nevertheless the problem persists, I believe definitively that the current kernel has problems with the tunnels ppp.

regards

pd: rafa mi msn es lucho_012@hotmail.com … saludos
Santa Cruz
Caleta Olivia

My setup

Ros: v3.11
Intel Pentium Dual Core: 3000 Mhz (set multi-cpu =YES)
RAM= 1Gb
PPPoE Secrets = 372.
Licencie = Level 5
Max simultaneously PPPOE users = about 211

I’ve not major problems. Everything is OK, but sometimes
%CPU overhead (each 2 o 3 days), and PPPoE server begins
to disconnect users or get random fails (but no Ros CRASH).

I restart ROS when this happens, and everything is OK for
2 or 3 days.

I’m not using RADIUS over my PPPoE server, but I want to
use FREE RADIUS soon!

best regards
andres.
pppoe_cpu.png
pppoe.png

also see this another topic before doing the job unregister_netdevice problem . maybe it stops you .

hello I installed ROS 3.14rc1 but the problem is still present, but I noticed the disconnections happens MORE frequently than before so I immediately downgraded to ROS 3.13.
For your info I changed previous RB333 with RB433 with no success, same problem.
Regards
Alessandro

Hello Mtik team, I am thinking about that maybe the Virtual AP on the same interface of PPPoE that is causing the problem.
I’ve noticed the overall ACK timeout of the interface decreasing from about 350 usec to 50 usec if I disable the VAP interface; at the same time the overall tx CCQ increases from about 30/60% to about 90%.
At this point I left VAP disabled and now I am watching if some PPPoE client disconnects, after about 2 ours nobody has disconnected, I will let you informed.
Regards
Alessandro

Maybe in your case the virtual ap is an attenuant. At my case I am not being employed with th and nevertheless I have the problem that they all.

regards

Hello
I don’t have any VAP, in the server where I have PPPoE, is only PPPoE Server with a public interface and an internal interface. I have done this configuration to other people and works perfectly!!!. And when I do to my network its CHASH :open_mouth: . I think that are some situation that occurs that cause its. So it will be extremelly difficult to found!!! :frowning:
The different that happened to me when I try v 3.11 and 3.13, is that with 3.13 didn’t crash, but it have problem to assing IP, the server tried to assing IP that was in use in other user, the server didn’t crash, but some clients couldn’t connect. So I prefered to be near the server to restarted it, that have some clients called me every minute!!
And something that I don’t understand, is with this happen me when I use public IP Address. If I use private IP Address, with NAT, works PERFECTLY!!, but I want to use my range of Public IP!!! :confused: I’m paying for its IP!!!
And Andres do you remember that I have that problem that you have when I configured my Server with multi-cpu =YES, so I disabled its, and solved my problems. And in different of the CPU used with its and no, was nothing!! So I recommend to disable its!!
Thanks
Rafael Lore