Hello,
has anyone succeeded in connecting UBNT client using PPPoe to MT with radius?
My bullet is showing log that it could not determine remote ip address.
Does someone know what definition parameter should I use beside Framed-IP-Address (client IP) and NAS-IP-Address (in my case MT)??
Bullet in any case shows remote IP address 10.64.64.64, and writes to log: LCP terminated by peer (could not determine remote IP address^@)
When authenticating with local users in MT, pppoe works fine.
I don’t think it is related to the CPE rather to the Radius Config and pppoe server profile.
You should create a PPPoE Server profile which has assigned a local IP:
/interface pppoe-server server
add service-name=xyz interface=etherx default-profile=pppoe_profile
/ppp profile
add name=pppoe_profile local-address=10.1.1.1
Caci99, thank you for your comment.
I’m pretty sure that PPP profile is configured with local address, but I will double check and let you know.
No, I didn’t had local ip address configured in profile.
I entered it, but same log errors appear in CPE’s log:
Aug 24 07:55:55 ITuda daemon.notice pppd[318]: Connect: ppp0 ↔ ath0
Aug 24 07:55:55 ITuda daemon.notice pppd[318]: CHAP authentication succeeded
Aug 24 07:55:55 ITuda daemon.notice pppd[318]: peer from calling number 00:xx:xx:xx:xx:xx authorized
Aug 24 07:55:56 ITuda daemon.info pppd[318]: CCP terminated by peer (No compression negotiated^@)
Aug 24 07:55:56 ITuda daemon.notice pppd[318]: Compression disabled by peer.
Aug 24 07:55:59 ITuda daemon.warn pppd[318]: Could not determine remote IP address: defaulting to 10.64.64.64
Aug 24 07:55:59 ITuda daemon.notice pppd[318]: local IP address 10.19.17.6
Aug 24 07:55:59 ITuda daemon.notice pppd[318]: remote IP address 10.64.64.64
Aug 24 07:55:59 ITuda daemon.notice pppd[318]: primary DNS address 10.19.x.y
Aug 24 07:55:59 ITuda daemon.info pppd[318]: IPCP terminated by peer (no local IP address specified^@)
Aug 24 07:55:59 ITuda daemon.info pppd[318]: Connect time 0.0 minutes.
Aug 24 07:55:59 ITuda daemon.info pppd[318]: Sent 0 bytes, received 0 bytes.
Aug 24 07:55:59 ITuda daemon.info pppd[318]: LCP terminated by peer (could not determine remote IP address^@)
Aug 24 07:56:02 ITuda daemon.notice pppd[318]: Connection terminated.
Aug 24 07:56:02 ITuda daemon.notice pppd[318]: Modem hangup
Aug 24 07:56:03 ITuda daemon.info pppd[318]: PPP session is 484
Aug 24 07:56:03 ITuda daemon.info pppd[318]: Using interface ppp0
The fact that you can successfully log on to your local pppoe server without using radius,
indicates that the problem is mostly related to the radius configuration.
What Radius are you using? Are you trying to give dynamic IPs or static ones to the CPE?
If they are dynamic, is the pool correctly configured on Radius? It could also be that Radius
on router is not communicating with the radius server, so can get user profile.
You may have have entered it, but did you do so correctly? Is the profile where you added it, the actual profile being used?
The logs say, that it is not able to obtain an local address. The only way you can define an local address is through the ppp profiles, and telling your pppoe server to use said local ppp profile. You cannot specify an local address through radius.
@Caci99
I’m using freeradius, using static IP address for CPE.
Radius client on the router can communicate with Radius server, otherwise CPE could not now it’s local IP address written in the log.
@savage
Yes, the profile where I entered local IP address is used by PPP server.
What is remote address to Mikrotik, is actually local IP address for CPE, and vice versa.
I done it, PPPoE server pointed on wrong profile, it was default.
Thank you guys!