Size: a a a

2020 July 16

D

Dimka88 in Accel-PPP
Многое зависит сколько сессий
источник

SM

Sergei Markelov in Accel-PPP
В общей сложности пока +/-1000
источник

SM

Sergei Markelov in Accel-PPP
Еще не всех перетащил
источник

SM

Sergei Markelov in Accel-PPP
что такое 0,100:1000 и -1 в конце
источник

D

Dimka88 in Accel-PPP
не принимать больше сессий
источник

D

Dimka88 in Accel-PPP
источник

D

Dimka88 in Accel-PPP
по 1000 на двух серверах?
источник

SM

Sergei Markelov in Accel-PPP
по 500, будет по 1500 примерно
источник

D

Dimka88 in Accel-PPP
Лучше сразу weigh внедрять тогда
[ipoe]
weight=1
источник

D

Dimka88 in Accel-PPP
На обоих серверах
источник

D

Dimka88 in Accel-PPP
И будет поровну балансировать
источник

D

Dimka88 in Accel-PPP
weight=n
By default not defined:

More modern load balancing mechanism based on weight.

How it works: On reception of DHCPDISCOVER accel-ppp sends broadcast DHCP message to port 67 with same xid and add special vendor-specific option where encodes its current session count multipled by weight. On reception of such message accel-ppp searches session with same xid and compares weight. If received weight is less than session’s weight then it terminates this session. May be used as per-interface.
источник

SM

Sergei Markelov in Accel-PPP
ок. А что по поводу pppoe? Они балансируются?
источник

D

Dimka88 in Accel-PPP
Угу, pado-delay
источник

SM

Sergei Markelov in Accel-PPP
ок
источник

D

Dimka88 in Accel-PPP
pado-delay=delay[,delay1:count1[,delay2:count2[,…]]]
By default is disabled.

Specifies delays (also in condition of connection count) to send PADO (ms). Last delay in list may be -1 which means don’t accept new connections. List have to be sorted by count key.
источник

SM

Sergei Markelov in Accel-PPP
Спасибо!
источник

SM

Sergei Markelov in Accel-PPP
Релоад достаточно, или рестарт:
источник

D

Dimka88 in Accel-PPP
Для ipoe достаточно, для pppoe либо через accel-cmd применять, либо через restart
источник

DM

Dmitriy Mihaylenko in Accel-PPP
Dimka88
weight=n
By default not defined:

More modern load balancing mechanism based on weight.

How it works: On reception of DHCPDISCOVER accel-ppp sends broadcast DHCP message to port 67 with same xid and add special vendor-specific option where encodes its current session count multipled by weight. On reception of such message accel-ppp searches session with same xid and compares weight. If received weight is less than session’s weight then it terminates this session. May be used as per-interface.
А в случае weight только один брас пошлет пакет авторизации в радиус? Или как при offer-delay все пошлют?
источник