[rbak-nsp] pppoe port-limit = 1 ?

Marcin Kuczera marcin at leon.pl
Wed May 21 10:37:28 EDT 2008


hello,

I found a little problem while testing SE100 with Mikrotik RB333

the problem is with pppoe session when I remove an ethernet cable from 
Mikrotik.
Just right after it has been connected back, it tries to re-establish pppoe 
connection again.
However, the port-limit=1 so, it is dropped. So, continously I can see 
something like that:

marcin.kuczera at wifi
        Circuit   2/2 vlan-id 800 pppoe 7991
        Internal Circuit   2/2:1023:63/6/2/24381
        Interface bound  pool
        Current port-limit 1
        ip pool pool (applied)
        dns primary 195.66.73.11 (applied from sub_default)
        dns secondary 195.66.73.4 (applied from sub_default)
        port-limit 1 (applied from sub_default)
        ip source-validation 1 (applied from sub_default)
        ip address 89.200.231.105 (applied from pool)
        qos rate inbound rate 4096 burst 1000000 (applied)
        qos rate outbound rate 4096 burst 1000000 (applied)
        qos-metering-policy wifi-down (applied from sub_default)
        qos-policing-policy wifi-up (applied from sub_default)
marcin.kuczera at wifi
        Circuit   2/2 vlan-id 800 pppoe 8015
        Internal Circuit   2/2:1023:63/6/2/24405
        Current port-limit 1
        ip pool pool (applied)
        dns primary 195.66.73.11 (applied from sub_default)
        dns secondary 195.66.73.4 (applied from sub_default)
        port-limit 1 (not applied from sub_default)
        ip source-validation 1 (not applied from sub_default)
        ip address 89.200.231.116 (applied from pool)
        qos rate inbound rate 4096 burst 1000000 (not applied)
        qos rate outbound rate 4096 burst 1000000 (not applied)
        qos-metering-policy wifi-down (not applied from sub_default)
        qos-policing-policy wifi-up (not applied from sub_default)

the first session is dead, but SEOS didn't notify that, and the second 
session is
invoked new continously...
Until, the first session is deteced as dead by SEOS.


How can I force the system to drop the first session when second comes up ?
Or - is there any other solution like that ?


Regards,
Marcin




More information about the redback-nsp mailing list