We have a setup where PPPoE works with the local database, but not with a Radius Server. We are using Free Radius V1.0.0 which has been tested with Radlogin from IEA Software. The Radius server is working fine.

We are running 2.9 beta 4
Our Mikrotik Setup is:

/radius
service = ppp
address = 10.1.0.100 (We have a local ethernet card with IP=10.1.0.1 and can ping the radius server)
secret = the correct secret

/ppp aaa
use-radius=yes
accounting=yes
interim-update=00:00:00

When I monitor radius I get:

/radius monitor 0
pending: 0
requests: 0
accepts: 0
rejects: 0
resends: 0
timeouts: 0
bad-replies: 0

These figures never change. I also never see a request at the radius server when running in debug mode. As well, I have used ethereal and do not see any UDP packets on port 1812.

The Mikrotik log has this:

PPPoE connection established from 00:0A:04:51:08:2F

<pppoe-terryd>: terminating... - user terryd authentication failed - radius timeout

<pppoe-terryd>: disconnected

Any idea why the radius requests are not making it out of the Mikrotik box?

Does anyone have Radius working over PPPoE on 2.9B4?

Terry

Today, I set up the sniffer tool:

/tool sniffer> print
interface: all
only-headers: no
memory-limit: 10
file-name:
file-limit: 10
streaming-enabled: no
streaming-server: 0.0.0.0
filter-stream: yes
filter-protocol: ip-only
filter-address1: 0.0.0.0/0:1812-1813
filter-address2: 10.1.0.100/0:0-65535
running: yes

This should capture all packets on ports 1812 & 1813
and/or all packets destined for 10.1.0.100 which is my radius server.

When I do a ping to 10.1.0.100, I see the packets captured
However, when I try to do a PPPoE authentication, there are no packets.

This leads me to believe that Radius is not working in 2.9b4

Any other thoughts?
Terry

there is a bug in beta4 in radius client. It will be fixed in beta5.

Edgars