IPoE+L2+dhcp+opt82 (dhcp_local_relay)

IPoE related questions
baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 26 Sep 2019, 17:16

Добрый день, вечер.

Пытаюсь заставить работать связку Centos6(3.16.74)+LanBilling(2.0.24)+des3200. Но не выходит, биллинг через свой радиус 'отвергает'...
Прошу помощи, ткните, куда копать ?

Биллинг авторизовывает на основании mac+opt82. Где username=mac клиента.
Что есть:
accel-ppp.conf
Спойлер
[modules]
log_file
log_tcp
ipoe
radius
shaper

[ipoe]
mode=L2
shared=1
ipv6=0
gw-ip-address=10.11.0.1/24
start=dhcpv4
ifcfg=1
interface=eth0.111,username=lua:u1
lease-time=300
renew-time=150
max-lease-time=600
password=username
lua-file=/etc/accel-ppp.lua
verbose=10
attr-dhcp-client-ip=Framed-IP-Address
attr-dhcp-router-ip=DHCP-Router-IP-Address
attr-dhcp-mask=Framed-IP-Netmask
attr-dhcp-opt82=DHCP-Option82
attr-dhcp-opt82-remote-id=DHCP-Agent-Remote-Id
attr-dhcp-opt82-circuit-id=DHCP-Agent-Circuit-Id
#l4-redirect-ipset=l4-redirect
#vlan-mon=eth0.111

[ip-pool]
10.11.0.0/24,name=ipoet

[radius]
dictionary=/usr/share/accel-ppp/radius/dictionary
nas-identifier=192.168.200.200
nas-ip-address=192.168.200.200
gw-ip-address=10.11.0.1
server=192.168.200.200,lbtest,auth-port=1812,acct-port=1813,req-limit=0,fail-time=0
dae-server=192.168.200.200:3799,lbtest
verbose=100
timeout=3
max-try=3
acct-timeout=0
acct-on=1
acct-interim-interval=60
acct-delay-time=0
sid-in-auth=1
accel-ppp.log
Спойлер
.[1;32m[2019-09-26 22:07:49]: info: eth0.111: .[0;39mrecv [DHCPv4 Discover xid=6fd59582 chaddr=18:a9:05:cb:c3:0a <Message-Type Discover> <Client-ID 0118a905cbc30a> <Host-Name Administrator> <Vendor-Class 4d53465420352e30> <Request-List
Subnet,Domain-Name,Router,DNS,44,46,47,31,Route,Classless-Route,249,Vendor-Specific> <Relay-Agent {Agent-Circuit-ID _0004006f0003} {Agent-Remote-ID _0006340804644984}>]
.[1;32m[2019-09-26 22:07:49]: info: ipoe0: .[0;39mcreate interface ipoe0 parent eth0.111
.[1;32m[2019-09-26 22:07:49]: info: ipoe0: .[0;39msend [RADIUS(1) Access-Request id=1 <User-Name "18:a9:05:cb:c3:0a"> <NAS-Identifier "192.168.200.200"> <NAS-IP-Address 192.168.200.200> <NAS-Port 165> <NAS-Port-Id "ipoe0"> <NAS-Port-Typ
e Ethernet> <Calling-Station-Id "18:a9:05:cb:c3:0a"> <Called-Station-Id "eth0.111"> <DHCP-Option82 0x01060004006f000302080006340804644984> <DHCP-Agent-Remote-Id 0x0006340804644984> <DHCP-Agent-Circuit-Id 0x0004006f0003> <Acct-Session-Id
"774dcff2ac49293a"> <User-Password 0xe4a79bd676cf872ae85a2fab049618878287b1631efbe13c4b9e78529db5bdd0>]
.[1;32m[2019-09-26 22:07:49]: info: ipoe0: .[0;39mrecv [RADIUS(1) Access-Reject id=1]
.[1;34m[2019-09-26 22:07:49]: debug: ipoe0: .[0;39mterminate
.[1;32m[2019-09-26 22:07:49]: info: ipoe0: .[0;39mipoe: session finished

Радиус биллинга:
Спойлер
26.09.2019 22:08:42.112326 VERBOSE LWP3958 [src/radius_base.cpp:56] ============== Authorization packet #186 received from 192.168.200.200, size: 200 ==============
26.09.2019 22:08:42.112360 VERBOSE LWP3958 [src/radius_record.cpp:90] Access-Request (1), id: 0x1, length: 200
26.09.2019 22:08:42.112374 VERBOSE LWP3958 [src/radius_record.cpp:108] Authenticator: 75bceec08ccad80a03015c51528e5976
26.09.2019 22:08:42.112386 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "User-Name", value: "18:a9:05:cb:c3:0a"
26.09.2019 22:08:42.112395 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "NAS-Identifier", value: "192.168.200.200"
26.09.2019 22:08:42.112404 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "NAS-IP-Address", value: "192.168.200.200"
26.09.2019 22:08:42.112412 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "NAS-Port", value: "168"
26.09.2019 22:08:42.112419 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "NAS-Port-Id", value: "ipoe0"
26.09.2019 22:08:42.112427 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "NAS-Port-Type", value: "15"
26.09.2019 22:08:42.112434 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "Calling-Station-Id", value: "18:a9:05:cb:c3:0a"
26.09.2019 22:08:42.112441 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "Called-Station-Id", value: "eth0.111"
26.09.2019 22:08:42.112452 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "DHCP-Option82", value: "01060004006f000302080006340804644984"
26.09.2019 22:08:42.112461 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "DHCP-Agent-Remote-Id", value: "0006340804644984"
26.09.2019 22:08:42.112469 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "DHCP-Agent-Circuit-Id", value: "0004006f0003"
26.09.2019 22:08:42.112476 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "Acct-Session-Id", value: "774dcff2ac49293d"
26.09.2019 22:08:42.112488 VERBOSE LWP3958 [src/radius_record.cpp:113] Attribute "Password", value: "38be93c587bbb5264ce60cfde3e99fc238f5da623ff2d7de1974e20bb7d95afe"
26.09.2019 22:08:42.112498 VERBOSE LWP3958 [src/radius_record.cpp:186] User-Password = "18:a9:05:cb:c3:0a"
26.09.2019 22:08:42.112508 VERBOSE LWP3958 [src/radius_packet.cpp:75] NAS IP replaced to 192.168.200.200 from NAS-Ip-Address
26.09.2019 22:08:42.112561 INFO LWP3958 [src/radius_packet.cpp:914] All auth tries failed: methods='opt82', Session-Id 774dcff2ac49293d
26.09.2019 22:08:42.113365 INFO LWP3958 [src/radius.cpp:591] Access-Reject, <18:a9:05:cb:c3:0a>, Session-Id 774dcff2ac49293d
26.09.2019 22:08:42.113395 VERBOSE LWP3958 [src/radius_record.cpp:90] Access-Reject (3), id: 0x1, length: 20
26.09.2019 22:08:42.113433 VERBOSE LWP3958 [src/radius_base.cpp:92] <=<=<=<=<=<=<=< Authentication answer sent successfully, time: 1 <=<=<=<=<=<=<=<

словарь:
Спойлер
ATTRIBUTE DHCP-Router-IP-Address 241 ipaddr
ATTRIBUTE DHCP-Mask 242 integer
ATTRIBUTE L4-Redirect 243 integer
ATTRIBUTE L4-Redirect-ipset 244 string
ATTRIBUTE DHCP-Option82 245 octets

ATTRIBUTE DHCP-Client-IP-Address 240 ipaddr
ATTRIBUTE DHCP-Router-IP-Address 241 ipaddr
ATTRIBUTE DHCP-Mask 242 ipaddr
ATTRIBUTE DHCP-Lease-Time 244 integer
ATTRIBUTE DHCP-Option82 245 octets
ATTRIBUTE DHCP-Agent-Remote-Id 246 octets
ATTRIBUTE DHCP-Agent-Circuit-Id 247 octets

ATTRIBUTE Acct-Interim-Interval 85 integer
ATTRIBUTE Acct-Input-Gigawords 52 integer
ATTRIBUTE Acct-Output-Gigawords 53 integer

megahertz0
Posts: 8
Joined: 17 Jun 2015, 13:37

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by megahertz0 » 30 Sep 2019, 08:01

Привет!
Не совсем понял зачем одновременно авторизация и по маку и по opt82. Насколько мне известно должен работать только один метод. По крайней мере у меня именно так сделано - ethernet по opt82, PON по макам.

Пока вот что предлагаю. Включи в LBcore запись дебага в логе, видно будет детально авторизацию вплоть до запросов LBarcd к БД. Судя по всему дело в том что агент не может найти у себя абона в БД т.к. в настройках агента radius для NASа указан метод авторизации только по opt82.

Пока проверь вот что.

Соответствие словаря на Акселе словарю в ЛБ. Атрибут "DHCP-Option82" должен заменять атрибут "DHCP-Relay-Agent-Information" ( https://i.imgur.com/htkaeNl.jpg), но опять же это важно только для opt82, для авторизации только по маку это неважно.
Регулярку по которой ЛБ парсит мак-адрес из Calling-Station-Id, вот здесь она описана как macregex https://www.lanbilling.ru/documentation/agents-options

sever-sever
Posts: 1
Joined: 30 Sep 2019, 08:29

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by sever-sever » 30 Sep 2019, 09:18

У тебя некоторые номера атрибутов в словаре пересекаются
например 244
ATTRIBUTE L4-Redirect-ipset 244 string
ATTRIBUTE DHCP-Lease-Time 244 integer

Попробуй сделать словарь:

ATTRIBUTE DHCP-Router-IP-Address 241 ipaddr
ATTRIBUTE DHCP-Mask 242 integer
ATTRIBUTE L4-Redirect 243 integer
ATTRIBUTE L4-Redirect-ipset 244 string
ATTRIBUTE DHCP-Option82 245 octets
ATTRIBUTE AccelRemoteId 246 octets
ATTRIBUTE AccelCircuitId 247 octets
ATTRIBUTE Session-Octets-Limit 227 integer
ATTRIBUTE Octets-Direction 228 integer
ATTRIBUTE PPPD-Upstream-Speed-Limit 230 integer
ATTRIBUTE PPPD-Downstream-Speed-Limit 231 integer
ATTRIBUTE PPPD-Upstream-Speed-Limit-1 232 integer
ATTRIBUTE PPPD-Downstream-Speed-Limit-1 233 integer
ATTRIBUTE PPPD-Upstream-Speed-Limit-2 234 integer
ATTRIBUTE PPPD-Downstream-Speed-Limit-2 235 integer
ATTRIBUTE PPPD-Upstream-Speed-Limit-3 236 integer
ATTRIBUTE PPPD-Downstream-Speed-Limit-3 237 integer
ATTRIBUTE Acct-Interim-Interval 85 integer
ATTRIBUTE Acct-Input-Gigawords 52 integer
ATTRIBUTE Acct-Output-Gigawords 53 integer

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 30 Sep 2019, 14:16

megahertz0 wrote:
30 Sep 2019, 08:01
Не совсем понял зачем одновременно авторизация и по маку и по opt82. Насколько мне известно должен работать только один метод. По крайней мере у меня именно так сделано - ethernet по opt82, PON по макам.
Спасибо за пост, подскажите как Вы это поняли ? Что я пытаюсь авторизовать по двум типам авторизации ?
2019-09-30_19-13-18.png
Да и строчка: 26.09.2019 22:08:42.112561 INFO LWP3958 [src/radius_packet.cpp:914] All auth tries failed: methods='opt82', Session-Id 774dcff2ac49293d я полагаю говорит, что все методы это opt82.Или я, что то не так понимаю ?

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 30 Sep 2019, 14:18

megahertz0 wrote:
30 Sep 2019, 08:01
Атрибут "DHCP-Option82" должен заменять атрибут "DHCP-Relay-Agent-Information" ( https://i.imgur.com/htkaeNl.jpg), но опять же это важно только для opt82, для авторизации только по маку это неважно.
1. ВОт этого не знал, пробую.
2. Вот возник вопрос,
2019-09-30_19-21-14.png
2019-09-30_19-21-14.png (35.64 KiB) Viewed 99 times
К примеру Framed-IP-Address имеет VSAT 8, но вендора 0, в то же время Mikrotik-rate-limit имеет VSAT такой же - 0, но вендора другого. Вопрос, такие совпадения критичны ? И что указывать в словаре биллинга, если в библиотеке радиуса есть VSAT но нет вендора, какой номер вендора прописывать ?

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 30 Sep 2019, 14:26

megahertz0 wrote:
30 Sep 2019, 08:01
Регулярку по которой ЛБ парсит мак-адрес из Calling-Station-Id, вот здесь она описана как macregex https://www.lanbilling.ru/documentation/agents-options
Насколько понял, Вы про: /(..)-(..)-(..)-(..)-(..)-(..)/\\1\\2\\3\\4\\5\\6/i ?

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 30 Sep 2019, 14:52

megahertz0 wrote:
30 Sep 2019, 08:01
Пока вот что предлагаю. Включи в LBcore запись дебага в логе, видно будет детально авторизацию вплоть до запросов LBarcd к БД.
Вот всё что как то смог связать в логе ядра с абонентом.
Спойлер
30.09.2019 19:44:17.251823 DEBUG LWP2359 [db_proxy_connection.cpp:166:LogQuery] SqlQuery : [1863361] DELETE FROM `radius_stat_cache` WHERE (((`group_by_hour` = '2019-08-29 23:00:00' AND `na
s` = 0x00000000000000000000ffffc0a8fe09) AND `session_id` = 'FF16033A7800E770-5D429B1D') AND `record_id` <= '375882232')
30.09.2019 19:44:17.256430 DEBUG LWP2364 [json_session.cpp:92:Read] Session 1034 input: { "id": 205, "method": "setSyncAuthHistory", "params": { "auths": [ { "comment": "", "dt": "2019-09-30 19
:39:09", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac49648c", "vg_login": "18:a9:05:cb:c3:0a" }, { "commen
t": "", "dt": "2019-09-30 19:39:01", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac49648b", "vg_login": "18:
a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:31:13", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff
2ac49648a", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:28:54", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result
": 1, "session_id": "774dcff2ac496489", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:28:39", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip"
: "192.168.200.200", "result": 1, "session_id": "774dcff2ac496488", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:28:31", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c
3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac496487", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:28:26", "duration": 0, "ip":
"::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac496486", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:
27:54", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac496485", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment
": "", "dt": "2019-09-30 19:27:40", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac496484", "vg_login": "18:a
9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:27:33", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2
ac496483", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:02:58", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result"
: 1, "session_id": "774dcff2ac496482", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:02:43", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip":
"192.168.200.200", "result": 1, "session_id": "774dcff2ac496481", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:02:34", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3
:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac496480", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:01:34", "duration": 0, "ip":
"::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac49647f", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment": "", "dt": "2019-09-30 19:0
1:19", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac49647e", "vg_login": "18:a9:05:cb:c3:0a" }, { "comment"
: "", "dt": "2019-09-30 19:01:10", "duration": 0, "ip": "::", "mac": "18:a9:05:cb:c3:0a", "nas_id": 0, "nas_ip": "192.168.200.200", "result": 1, "session_id": "774dcff2ac49647d", "vg_login": "18:a9
:05:cb:c3:0a" } ], "total": 16, "waiting_id": "0x7f54c8010da02019-09-30 19:44:17" } }

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 30 Sep 2019, 14:54

Пожалуй стоит добавить, что схема IPoE+L2+dhcp+opt82 (dhcp_local_relay) работает уже в другом городе, где в качестве браса SE100. Тестовую лабу собрал на домашнем сервере + des-3200. На сервере стоит только LBarcd+Accel-ppp и через openvpn связывается с ядром.

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 30 Sep 2019, 15:11

sever-sever wrote:
30 Sep 2019, 09:18
У тебя некоторые номера атрибутов в словаре пересекаются
LBAcrd (в словаре заменил VSA 246 и 247)
Спойлер
30.09.2019 20:04:40.339400 VERBOSE LWP26744 [src/radius_base.cpp:56] ============== Authorization packet #39 received from 192.168.200.200, size: 164 ==============
30.09.2019 20:04:40.339434 VERBOSE LWP26744 [src/radius_record.cpp:90] Access-Request (1), id: 0x1, length: 164
30.09.2019 20:04:40.339448 VERBOSE LWP26744 [src/radius_record.cpp:108] Authenticator: 007ae6b81677f65a65c26868c8081840
30.09.2019 20:04:40.339460 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "User-Name", value: "18:a9:05:cb:c3:0a"
30.09.2019 20:04:40.339469 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "NAS-Identifier", value: "accel-ppp"
30.09.2019 20:04:40.339477 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "NAS-IP-Address", value: "192.168.200.200"
30.09.2019 20:04:40.339485 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "NAS-Port", value: "384"
30.09.2019 20:04:40.339492 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "NAS-Port-Id", value: "ipoe0"
30.09.2019 20:04:40.339500 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "NAS-Port-Type", value: "15"
30.09.2019 20:04:40.339507 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "Calling-Station-Id", value: "18:a9:05:cb:c3:0a"
30.09.2019 20:04:40.339514 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "Called-Station-Id", value: "eth0.111"
30.09.2019 20:04:40.339521 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "NAS-Identifier", value: "ipoe"
30.09.2019 20:04:40.339530 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "DHCP-Agent-Remote-Id", value: "0006340804644984"
30.09.2019 20:04:40.339538 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "DHCP-Agent-Circuit-Id", value: "0004006f0003"
30.09.2019 20:04:40.339545 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "Acct-Session-Id", value: "774dcff2ac497052"
30.09.2019 20:04:40.339555 VERBOSE LWP26744 [src/radius_record.cpp:113] Attribute "Password", value: "43d58ae5a3bc2898a2010a43cf7c5986"
30.09.2019 20:04:40.339563 VERBOSE LWP26744 [src/radius_record.cpp:186] User-Password = "accel-ppp"
30.09.2019 20:04:40.339573 VERBOSE LWP26744 [src/radius_packet.cpp:75] NAS IP replaced to 192.168.200.200 from NAS-Ip-Address
30.09.2019 20:04:40.339626 INFO LWP26744 [src/radius_packet.cpp:914] All auth tries failed: methods='opt82', Session-Id 774dcff2ac497052
30.09.2019 20:04:40.340498 INFO LWP26744 [src/radius.cpp:591] Access-Reject, <18:a9:05:cb:c3:0a>, Session-Id 774dcff2ac497052
30.09.2019 20:04:40.340532 VERBOSE LWP26744 [src/radius_record.cpp:90] Access-Reject (3), id: 0x1, length: 20

accel-ppp.log
Спойлер
.[1;32m[2019-09-30 20:04:40]: info: ipoe0: .[0;39mcreate interface ipoe0 parent eth0.111
.[1;32m[2019-09-30 20:04:40]: info: ipoe0: .[0;39msend [RADIUS(1) Access-Request id=1 <User-Name "18:a9:05:cb:c3:0a"> <NAS-Identifier "accel-ppp"> <NAS-IP-Address 192.168.200.200> <NAS-Port 384> <
NAS-Port-Id "ipoe0"> <NAS-Port-Type Ethernet> <Calling-Station-Id "18:a9:05:cb:c3:0a"> <Called-Station-Id "eth0.111"> <NAS-Identifier "ipoe"> <AccelRemoteId 0x0006340804644984> <AccelCircuitId 0x00
04006f0003> <Acct-Session-Id "774dcff2ac497052"> <User-Password 0x43d58ae5a3bc2898a2010a43cf7c5986>]
.[1;32m[2019-09-30 20:04:40]: info: ipoe0: .[0;39mrecv [RADIUS(1) Access-Reject id=1]
.[1;34m[2019-09-30 20:04:40]: debug: ipoe0: .[0;39mterminate
.[1;32m[2019-09-30 20:04:40]: info: ipoe0: .[0;39mipoe: session finished

baronzzz
Posts: 21
Joined: 22 Sep 2019, 12:01

Re: IPoE+L2+dhcp+opt82 (dhcp_local_relay)

Post by baronzzz » 02 Oct 2019, 03:59

Коллеги, есть у кого ещё мысли почему это не заводится?

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest