forum.bitel.ru :: Просмотр темы - failed to authenticate ourselves to peer mikrotik pppoe

/ppp profile
set 0 change-tcp-mss=no only-one=no use-compression=no use-encryption=no \
use-vj-compression=no
add change-tcp-mss=no dns-server=100.64.0.2 local-address=100.64.0.1 name=\
ppp use-compression=no use-encryption=no use-mpls=no use-vj-compression=\
no
/ppp aaa
set use-radius=yes
/radius
add address=10.0.18.3 secret=123 service=ppp
/radius incoming
set accept=yes port=1700

pppoe-out1: initializing...
pppoe-out1: connecting...
ether9: sent PADI to FF:FF:FF:FF:FF:FF
session-id=0x0000
host-uniq=0xc50021
service-name=
session-id=0x0000
vlan2_bridge: rcvd PADI from 4C:5E:0C:92:59:F1
session-id=0x0000
host-uniq=0xc50021
service-name=
session-id=0x0000
vlan2_bridge: sent PADO to 4C:5E:0C:92:59:F1
session-id=0x0000
host-uniq=0xc50021
service-name=
ac-name=SUPONEVO-NAS1
session-id=0x0000
ether9: rcvd PADO from 4C:5E:0C:92:5A:01
session-id=0x0000
host-uniq=0xc50021
service-name=
ac-name=SUPONEVO-NAS1
session-id=0x0000
ether9: sent PADR to 4C:5E:0C:92:5A:01
session-id=0x0000
host-uniq=0xc50022
service-name=
session-id=0x0000
<02f4>: LCP lowerup
<02f4>: LCP open
vlan2_bridge: rcvd PADR from 4C:5E:0C:92:59:F1
session-id=0x0000
host-uniq=0xc50022
service-name=
session-id=0x0000
PPPoE connection established from 4C:5E:0C:92:59:F1
vlan2_bridge: sent PADS to 4C:5E:0C:92:59:F1
session-id=0x02f4
host-uniq=0xc50022
service-name=
session-id=0x02f4
ether9: rcvd PADS from 4C:5E:0C:92:5A:01
session-id=0x02f4
host-uniq=0xc50022
service-name=
session-id=0x02f4
pppoe-out1: LCP lowerup
pppoe-out1: LCP open
pppoe-out1: LCP timer
<02f4>: rcvd LCP ConfReq id=0x46
<mru 1480>
<magic 0x4eecd450>
<02f4>: sent LCP ConfReq id=0x1
<mru 1480>
<magic 0x1787c261>
<auth chap>
<02f4>: sent LCP ConfAck id=0x46
<mru 1480>
<magic 0x4eecd450>
pppoe-out1: sent LCP ConfReq id=0x46
<mru 1480>
<magic 0x4eecd450>
<02f4>: rcvd LCP ConfAck id=0x1
<mru 1480>
<magic 0x1787c261>
<auth chap>
<02f4>: LCP opened
<02f4>: sent CHAP Challenge id=0x1
<challenge len=16>
<name SUPONEVO-NAS1>
pppoe-out1: rcvd LCP ConfReq id=0x1
<mru 1480>
<magic 0x1787c261>
<auth chap>
pppoe-out1: sent LCP ConfAck id=0x1
<mru 1480>
<magic 0x1787c261>
<auth chap>
pppoe-out1: rcvd LCP ConfAck id=0x46
<mru 1480>
<magic 0x4eecd450>
pppoe-out1: LCP opened
pppoe-out1: rcvd CHAP Challenge id=0x1
<challenge len=16>
<name SUPONEVO-NAS1>
pppoe-out1: sent CHAP Response id=0x1
<response len=16>
<name test>
<02f4>: rcvd CHAP Response id=0x1
<response len=16>
<name test>
<02f4>: sent CHAP Failure id=0x1
bad username or password
<02f4>: user test authentication failed
pppoe-out1: rcvd CHAP Failure id=0x1
bad username or password
pppoe-out1: LCP close
pppoe-out1: LCP closed
pppoe-out1: sent LCP TermReq id=0x47
failed to authenticate ourselves to peer
<02f4>: LCP close
<02f4>: LCP closed
<02f4>: sent LCP TermReq id=0x2
pppoe-out1: rcvd LCP TermReq id=0x2
pppoe-out1: sent LCP TermAck id=0x2
pppoe-out1: LCP lowerdown
pppoe-out1: terminating... - failed to authenticate ourselves to peer
ether9: sent PADT to 00:00:00:00:00:00
session-id=0x02f4
session-id=0x02f4
pppoe-out1: LCP lowerdown
pppoe-out1: LCP down event in starting state
pppoe-out1: disconnected
<02f4>: rcvd LCP TermReq id=0x47
failed to authenticate ourselves to peer
<02f4>: sent LCP TermAck id=0x47
<02f4>: LCP lowerdown
<02f4>: LCP lowerdown
<02f4>: LCP down event in starting state
vlan2_bridge: sent PADT to 4C:5E:0C:92:59:F1
session-id=0x02f4
session-id=0x02f4
ether9: rcvd PADT from 4C:5E:0C:92:5A:01
session-id=0x02f4
session-id=0x02f4

09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 203
Authenticator: {3C AA BD 8A 84 58 D0 86 F2 38 C4 A3 36 57 6B 2D}
Attributes:
User-Name=test
NAS-Identifier=SUPONEVO-NAS1
NAS-Port-Id=vlan2_bridge
CHAP-Password={01 57 E6 3A 26 92 D1 EB 31 E9 26 83 46 59 8B 25 17}
NAS-IP-Address=10.77.16.1
NAS-Port=15729394
Service-Type=2
Framed-Protocol=1
Calling-Station-Id=4C:5E:0C:92:59:F1
NAS-Port-Type=15
CHAP-Challenge=??^y?"?R?=??

09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetNas - Search by username=test
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusProcessor - [username=test] Authenticated as inetServId:1
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetApplication - TariffOptionMap: {}
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetApplication - inetServ[id=1] balance ok: 1000.00 [0]
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetApplication - OptionSet: []
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusProcessor - Set ip from serv
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusProcessor - Return code=0
09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 203
Authenticator: {FD B0 B4 94 D7 57 F5 A9 85 A6 6E F1 EC D3 07 AF}
Attributes:
Framed-IP-Address=100.64.33.87

Process time auth: 2

dialup.workmode=1
nas.inspector.class=bitel.billing.server.processor.PoDNASConnectionInspector
nas.inspector.pod.port=1700
nas.inspector.pod.attributes=User-Name;Framed-IP-Address;Acct-Session-Id

pppoe-out1: initializing...
pppoe-out1: connecting...
ether9: sent PADI to FF:FF:FF:FF:FF:FF
session-id=0x0000
host-uniq=0xbf0001
service-name=
session-id=0x0000
vlan2_bridge: rcvd PADI from 4C:5E:0C:92:59:F1
session-id=0x0000
host-uniq=0xbf0001
service-name=
session-id=0x0000
vlan2_bridge: sent PADO to 4C:5E:0C:92:59:F1
session-id=0x0000
host-uniq=0xbf0001
service-name=
ac-name=SUPONEVO-NAS1
session-id=0x0000
<0320>: LCP lowerup
<0320>: LCP open
ether9: rcvd PADO from 02:87:6A:DE:E8:ED
session-id=0x0000
host-uniq=0xbf0001
service-name=
ac-name=SUPONEVO-NAS1
session-id=0x0000
ether9: sent PADR to 02:87:6A:DE:E8:ED
session-id=0x0000
host-uniq=0xbf0002
service-name=
session-id=0x0000
vlan2_bridge: rcvd PADR from 4C:5E:0C:92:59:F1
session-id=0x0000
host-uniq=0xbf0002
service-name=
session-id=0x0000
18:41:25 pppoe,info PPPoE connection established from 4C:5E:0C:92:59:F1
vlan2_bridge: sent PADS to 4C:5E:0C:92:59:F1
session-id=0x0320
host-uniq=0xbf0002
service-name=
session-id=0x0320
ether9: rcvd PADS from 02:87:6A:DE:E8:ED
session-id=0x0320
host-uniq=0xbf0002
service-name=
session-id=0x0320
pppoe-out1: LCP lowerup
pppoe-out1: LCP open
pppoe-out1: LCP timer
pppoe-out1: sent LCP ConfReq id=0x42
<mru 1480>
<magic 0x698446a2>
<0320>: rcvd LCP ConfReq id=0x42
<mru 1480>
<magic 0x698446a2>
<0320>: sent LCP ConfReq id=0x1
<mru 1480>
<magic 0x3dee1e39>
<auth chap>
<0320>: sent LCP ConfAck id=0x42
<mru 1480>
<magic 0x698446a2>
<0320>: rcvd LCP ConfAck id=0x1
<mru 1480>
<magic 0x3dee1e39>
<auth chap>
<0320>: LCP opened
<0320>: sent CHAP Challenge id=0x1
<challenge len=16>
<name SUPONEVO-NAS1>
<0320>: rcvd CHAP Response id=0x1
<response len=16>
<name test>
pppoe-out1: rcvd LCP ConfReq id=0x1
<mru 1480>
<magic 0x3dee1e39>
<auth chap>
pppoe-out1: sent LCP ConfAck id=0x1
<mru 1480>
<magic 0x3dee1e39>
<auth chap>
pppoe-out1: rcvd LCP ConfAck id=0x42
<mru 1480>
<magic 0x698446a2>
pppoe-out1: LCP opened
pppoe-out1: rcvd CHAP Challenge id=0x1
<challenge len=16>
<name SUPONEVO-NAS1>
pppoe-out1: sent CHAP Response id=0x1
<response len=16>
<name test>
<0320>: sent CHAP Success id=0x1
Welcome.
<pppoe-test>: authenticated
pppoe-out1: rcvd CHAP Success id=0x1
Welcome.
pppoe-out1: authenticated
pppoe-out1: IPCP lowerup
pppoe-out1: sent IPCP ConfReq id=0x3
<addr 0.0.0.0>
pppoe-out1: IPCP open
pppoe-out1: IPV6CP open
pppoe-out1: MPLSCP lowerup
pppoe-out1: sent MPLSCP ConfReq id=0x2
pppoe-out1: MPLSCP open
pppoe-out1: BCP open
pppoe-out1: CCP lowerup
pppoe-out1: CCP open
<0320>: IPCP lowerup
<0320>: IPCP open
<0320>: sent IPCP ConfReq id=0x1
<addr 100.64.0.1>
<0320>: IPV6CP open
<0320>: MPLSCP open
<0320>: BCP open
<0320>: CCP lowerup
<0320>: CCP open
<0320>: rcvd IPCP ConfReq id=0x3
<addr 0.0.0.0>
<0320>: sent IPCP ConfNak id=0x3
<addr 18.2.2.2>
pppoe-out1: rcvd IPCP ConfReq id=0x1
<addr 100.64.0.1>
pppoe-out1: sent IPCP ConfAck id=0x1
<addr 100.64.0.1>
pppoe-out1: rcvd IPCP ConfNak id=0x3
<addr 18.2.2.2>
pppoe-out1: sent IPCP ConfReq id=0x4
<addr 18.2.2.2>
<0320>: rcvd MPLSCP ConfReq id=0x2
<0320>: received unsupported protocol 0x8281
<0320>: sent LCP ProtRej id=0x2
82 81 01 02 00 04
pppoe-out1: rcvd LCP ProtRej id=0x2
82 81 01 02 00 04
<0320>: rcvd IPCP ConfAck id=0x1
<addr 100.64.0.1>
<0320>: rcvd IPCP ConfReq id=0x4
<addr 18.2.2.2>
<0320>: sent IPCP ConfAck id=0x4
<addr 18.2.2.2>
<0320>: IPCP opened
<pppoe-test>: connected
pppoe-out1: rcvd IPCP ConfAck id=0x4
<addr 18.2.2.2>
pppoe-out1: IPCP opened
pppoe-out1: connected

Автор:	jone31 [ 07 сен 2014, 00:12 ]
Заголовок сообщения:	failed to authenticate ourselves to peer mikrotik pppoe
На mikrotik настроен ppoe сервер. Код: /ppp profile set 0 change-tcp-mss=no only-one=no use-compression=no use-encryption=no \ use-vj-compression=no add change-tcp-mss=no dns-server=100.64.0.2 local-address=100.64.0.1 name=\ ppp use-compression=no use-encryption=no use-mpls=no use-vj-compression=\ no /ppp aaa set use-radius=yes /radius add address=10.0.18.3 secret=123 service=ppp /radius incoming set accept=yes port=1700 в логах микротик это: Код: pppoe-out1: initializing... pppoe-out1: connecting... ether9: sent PADI to FF:FF:FF:FF:FF:FF session-id=0x0000 host-uniq=0xc50021 service-name= session-id=0x0000 vlan2_bridge: rcvd PADI from 4C:5E:0C:92:59:F1 session-id=0x0000 host-uniq=0xc50021 service-name= session-id=0x0000 vlan2_bridge: sent PADO to 4C:5E:0C:92:59:F1 session-id=0x0000 host-uniq=0xc50021 service-name= ac-name=SUPONEVO-NAS1 session-id=0x0000 ether9: rcvd PADO from 4C:5E:0C:92:5A:01 session-id=0x0000 host-uniq=0xc50021 service-name= ac-name=SUPONEVO-NAS1 session-id=0x0000 ether9: sent PADR to 4C:5E:0C:92:5A:01 session-id=0x0000 host-uniq=0xc50022 service-name= session-id=0x0000 <02f4>: LCP lowerup <02f4>: LCP open vlan2_bridge: rcvd PADR from 4C:5E:0C:92:59:F1 session-id=0x0000 host-uniq=0xc50022 service-name= session-id=0x0000 PPPoE connection established from 4C:5E:0C:92:59:F1 vlan2_bridge: sent PADS to 4C:5E:0C:92:59:F1 session-id=0x02f4 host-uniq=0xc50022 service-name= session-id=0x02f4 ether9: rcvd PADS from 4C:5E:0C:92:5A:01 session-id=0x02f4 host-uniq=0xc50022 service-name= session-id=0x02f4 pppoe-out1: LCP lowerup pppoe-out1: LCP open pppoe-out1: LCP timer <02f4>: rcvd LCP ConfReq id=0x46 <mru 1480> <magic 0x4eecd450> <02f4>: sent LCP ConfReq id=0x1 <mru 1480> <magic 0x1787c261> <auth chap> <02f4>: sent LCP ConfAck id=0x46 <mru 1480> <magic 0x4eecd450> pppoe-out1: sent LCP ConfReq id=0x46 <mru 1480> <magic 0x4eecd450> <02f4>: rcvd LCP ConfAck id=0x1 <mru 1480> <magic 0x1787c261> <auth chap> <02f4>: LCP opened <02f4>: sent CHAP Challenge id=0x1 <challenge len=16> <name SUPONEVO-NAS1> pppoe-out1: rcvd LCP ConfReq id=0x1 <mru 1480> <magic 0x1787c261> <auth chap> pppoe-out1: sent LCP ConfAck id=0x1 <mru 1480> <magic 0x1787c261> <auth chap> pppoe-out1: rcvd LCP ConfAck id=0x46 <mru 1480> <magic 0x4eecd450> pppoe-out1: LCP opened pppoe-out1: rcvd CHAP Challenge id=0x1 <challenge len=16> <name SUPONEVO-NAS1> pppoe-out1: sent CHAP Response id=0x1 <response len=16> <name test> <02f4>: rcvd CHAP Response id=0x1 <response len=16> <name test> <02f4>: sent CHAP Failure id=0x1 bad username or password <02f4>: user test authentication failed pppoe-out1: rcvd CHAP Failure id=0x1 bad username or password pppoe-out1: LCP close pppoe-out1: LCP closed pppoe-out1: sent LCP TermReq id=0x47 failed to authenticate ourselves to peer <02f4>: LCP close <02f4>: LCP closed <02f4>: sent LCP TermReq id=0x2 pppoe-out1: rcvd LCP TermReq id=0x2 pppoe-out1: sent LCP TermAck id=0x2 pppoe-out1: LCP lowerdown pppoe-out1: terminating... - failed to authenticate ourselves to peer ether9: sent PADT to 00:00:00:00:00:00 session-id=0x02f4 session-id=0x02f4 pppoe-out1: LCP lowerdown pppoe-out1: LCP down event in starting state pppoe-out1: disconnected <02f4>: rcvd LCP TermReq id=0x47 failed to authenticate ourselves to peer <02f4>: sent LCP TermAck id=0x47 <02f4>: LCP lowerdown <02f4>: LCP lowerdown <02f4>: LCP down event in starting state vlan2_bridge: sent PADT to 4C:5E:0C:92:59:F1 session-id=0x02f4 session-id=0x02f4 ether9: rcvd PADT from 4C:5E:0C:92:5A:01 session-id=0x02f4 session-id=0x02f4 в логах access Код: 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 203 Authenticator: {3C AA BD 8A 84 58 D0 86 F2 38 C4 A3 36 57 6B 2D} Attributes: User-Name=test NAS-Identifier=SUPONEVO-NAS1 NAS-Port-Id=vlan2_bridge CHAP-Password={01 57 E6 3A 26 92 D1 EB 31 E9 26 83 46 59 8B 25 17} NAS-IP-Address=10.77.16.1 NAS-Port=15729394 Service-Type=2 Framed-Protocol=1 Calling-Station-Id=4C:5E:0C:92:59:F1 NAS-Port-Type=15 CHAP-Challenge=??^y?"?R?=?? 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetNas - Search by username=test 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusProcessor - [username=test] Authenticated as inetServId:1 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetApplication - TariffOptionMap: {} 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetApplication - inetServ[id=1] balance ok: 1000.00 [0] 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetApplication - OptionSet: [] 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusProcessor - Set ip from serv 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusProcessor - Return code=0 09-06/22:03:34 INFO [rdsLstnr-p-7-t-8] InetRadiusListenerWorker - RESPONSE: Packet type: Access-Accept Identifier: 203 Authenticator: {FD B0 B4 94 D7 57 F5 A9 85 A6 6E F1 EC D3 07 AF} Attributes: Framed-IP-Address=100.64.33.87 Process time auth: 2 пробовал добавить юзера test в лог базу микротик - коннектится нормально. не пойму что не так...

Автор:	jone31 [ 09 сен 2014, 02:33 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
сегодня все переустановил заново - опять затык на этом месте. помогите разобраться...

Автор:	Amir [ 09 сен 2014, 03:23 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
В биллинге в устройстве в поле Secret тоже 123 указано? Другие режимы аутентификации не пробовали?

Автор:	jone31 [ 09 сен 2014, 18:14 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
Amir писал(а): В биллинге в устройстве в поле Secret тоже 123 указано? Другие режимы аутентификации не пробовали? да. пробоал разрешить все режимы pap, chap, mschap1, mschap2 - все одно и тоже... в конфиге устройства это (из вашей вики): Код: dialup.workmode=1 nas.inspector.class=bitel.billing.server.processor.PoDNASConnectionInspector nas.inspector.pod.port=1700 nas.inspector.pod.attributes=User-Name;Framed-IP-Address;Acct-Session-Id

Автор:	Amir [ 09 сен 2014, 18:17 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
Цитата: dialup.workmode=1 nas.inspector.class=bitel.billing.server.processor.PoDNASConnectionInspector nas.inspector.pod.port=1700 nas.inspector.pod.attributes=User-Name;Framed-IP-Address;Acct-Session-Id Это не нужно. Может быть в Access-Accept какие-то дополнительные атрибуты нужно выдавать?

forum.bitel.ru http://forum.bitel.ru/

failed to authenticate ourselves to peer mikrotik pppoe http://forum.bitel.ru/viewtopic.php?f=44&t=9672	Страница 1 из 1

Автор:	jone31 [ 09 сен 2014, 20:46 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
Amir писал(а): Цитата: dialup.workmode=1 nas.inspector.class=bitel.billing.server.processor.PoDNASConnectionInspector nas.inspector.pod.port=1700 nas.inspector.pod.attributes=User-Name;Framed-IP-Address;Acct-Session-Id Это не нужно. Может быть в Access-Accept какие-то дополнительные атрибуты нужно выдавать? сейчас у нас Carbon Billing 4 - никаких доп манипуляций в части радиус авторизации не делали - все заработало из коробки. вот лог микротика: когда он авторизуется сам на себе: (в vlan2_bridge pppoe server, в ether9 - pppoe клиент, между ними свитч) Код: pppoe-out1: initializing... pppoe-out1: connecting... ether9: sent PADI to FF:FF:FF:FF:FF:FF session-id=0x0000 host-uniq=0xbf0001 service-name= session-id=0x0000 vlan2_bridge: rcvd PADI from 4C:5E:0C:92:59:F1 session-id=0x0000 host-uniq=0xbf0001 service-name= session-id=0x0000 vlan2_bridge: sent PADO to 4C:5E:0C:92:59:F1 session-id=0x0000 host-uniq=0xbf0001 service-name= ac-name=SUPONEVO-NAS1 session-id=0x0000 <0320>: LCP lowerup <0320>: LCP open ether9: rcvd PADO from 02:87:6A:DE:E8:ED session-id=0x0000 host-uniq=0xbf0001 service-name= ac-name=SUPONEVO-NAS1 session-id=0x0000 ether9: sent PADR to 02:87:6A:DE:E8:ED session-id=0x0000 host-uniq=0xbf0002 service-name= session-id=0x0000 vlan2_bridge: rcvd PADR from 4C:5E:0C:92:59:F1 session-id=0x0000 host-uniq=0xbf0002 service-name= session-id=0x0000 18:41:25 pppoe,info PPPoE connection established from 4C:5E:0C:92:59:F1 vlan2_bridge: sent PADS to 4C:5E:0C:92:59:F1 session-id=0x0320 host-uniq=0xbf0002 service-name= session-id=0x0320 ether9: rcvd PADS from 02:87:6A:DE:E8:ED session-id=0x0320 host-uniq=0xbf0002 service-name= session-id=0x0320 pppoe-out1: LCP lowerup pppoe-out1: LCP open pppoe-out1: LCP timer pppoe-out1: sent LCP ConfReq id=0x42 <mru 1480> <magic 0x698446a2> <0320>: rcvd LCP ConfReq id=0x42 <mru 1480> <magic 0x698446a2> <0320>: sent LCP ConfReq id=0x1 <mru 1480> <magic 0x3dee1e39> <auth chap> <0320>: sent LCP ConfAck id=0x42 <mru 1480> <magic 0x698446a2> <0320>: rcvd LCP ConfAck id=0x1 <mru 1480> <magic 0x3dee1e39> <auth chap> <0320>: LCP opened <0320>: sent CHAP Challenge id=0x1 <challenge len=16> <name SUPONEVO-NAS1> <0320>: rcvd CHAP Response id=0x1 <response len=16> <name test> pppoe-out1: rcvd LCP ConfReq id=0x1 <mru 1480> <magic 0x3dee1e39> <auth chap> pppoe-out1: sent LCP ConfAck id=0x1 <mru 1480> <magic 0x3dee1e39> <auth chap> pppoe-out1: rcvd LCP ConfAck id=0x42 <mru 1480> <magic 0x698446a2> pppoe-out1: LCP opened pppoe-out1: rcvd CHAP Challenge id=0x1 <challenge len=16> <name SUPONEVO-NAS1> pppoe-out1: sent CHAP Response id=0x1 <response len=16> <name test> <0320>: sent CHAP Success id=0x1 Welcome. <pppoe-test>: authenticated pppoe-out1: rcvd CHAP Success id=0x1 Welcome. pppoe-out1: authenticated pppoe-out1: IPCP lowerup pppoe-out1: sent IPCP ConfReq id=0x3 <addr 0.0.0.0> pppoe-out1: IPCP open pppoe-out1: IPV6CP open pppoe-out1: MPLSCP lowerup pppoe-out1: sent MPLSCP ConfReq id=0x2 pppoe-out1: MPLSCP open pppoe-out1: BCP open pppoe-out1: CCP lowerup pppoe-out1: CCP open <0320>: IPCP lowerup <0320>: IPCP open <0320>: sent IPCP ConfReq id=0x1 <addr 100.64.0.1> <0320>: IPV6CP open <0320>: MPLSCP open <0320>: BCP open <0320>: CCP lowerup <0320>: CCP open <0320>: rcvd IPCP ConfReq id=0x3 <addr 0.0.0.0> <0320>: sent IPCP ConfNak id=0x3 <addr 18.2.2.2> pppoe-out1: rcvd IPCP ConfReq id=0x1 <addr 100.64.0.1> pppoe-out1: sent IPCP ConfAck id=0x1 <addr 100.64.0.1> pppoe-out1: rcvd IPCP ConfNak id=0x3 <addr 18.2.2.2> pppoe-out1: sent IPCP ConfReq id=0x4 <addr 18.2.2.2> <0320>: rcvd MPLSCP ConfReq id=0x2 <0320>: received unsupported protocol 0x8281 <0320>: sent LCP ProtRej id=0x2 82 81 01 02 00 04 pppoe-out1: rcvd LCP ProtRej id=0x2 82 81 01 02 00 04 <0320>: rcvd IPCP ConfAck id=0x1 <addr 100.64.0.1> <0320>: rcvd IPCP ConfReq id=0x4 <addr 18.2.2.2> <0320>: sent IPCP ConfAck id=0x4 <addr 18.2.2.2> <0320>: IPCP opened <pppoe-test>: connected pppoe-out1: rcvd IPCP ConfAck id=0x4 <addr 18.2.2.2> pppoe-out1: IPCP opened pppoe-out1: connected

Автор:	Amir [ 10 сен 2014, 13:30 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
Carbon у вас не посылает дополнительные атрибуты в Access-Accept? Попробуйте указать в конфиге устройства radius.realm.default.attributes=Acct-Interim-Interval=60;Service-Type=2;Framed-Protocol=1 Может быть еще есть какие-то логи у Mikrotik, в данном логе ничего не видно про RADIUS (про общение с биллингом). Может быть ответ от биллинга не доходит до Mikrotik. Здесь похожая проблема, http://forum.mikrotik.com/viewtopic.php?f=9&t=30076

Автор:	jone31 [ 11 сен 2014, 00:17 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
в общем, сейчас биллинг ваш стоит на виртуалке KVM, микротик железный. Вчера выключил их обоих. Сегодня включаю виртуалку и тут бац микротик сразу подцепился к BGBilling. никаких изменений не вносил. что это могло быть? честно говоря меня пугает такое непонятное поведение...

Автор:	Amir [ 12 сен 2014, 19:05 ]
Заголовок сообщения:	Re: failed to authenticate ourselves to peer mikrotik pppoe
Вряд ли в биллинге дело, если пакеты такие же, дополнительных атрибутов в Access-Accept нет. Если есть новые атрибуты в Access-Accept - значит настройки меняли и забыли нажать "Перечитать конфигурацию на серверах" или перезапустить InetAccess. Если нет - возможно пакеты не доходили до Mikrotik или какая-то настройка Mikrotik'а применилась после перезапуса.

Страница 1 из 1	Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/