<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
The core dump was off, now when I enable the coredumps radiusd won't dump anymore.<br>Every other program dumps with SEGV signal, but radiusd won't<br>So I don't know how te get a dump.<br><br>now it aborts with:<br>(0) update coa {<br>ASSERT FAILED evaluate.c[1154]: output_vps<br>Aborted<br><br>Thanks in advance<br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: mixmasterontour@hotmail.com<br>To: freeradius-users@lists.freeradius.org<br>Subject: Coa problem<br>Date: Wed, 7 Nov 2012 12:25:48 +0100<br><br>
<style><!--
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
--></style>
<div dir="ltr">
Hello,<br><br>I have a problem with originate-coa<br><br>I want to send coa to mikrotik to change bandwith<br><br>But if I do that I get the folowing error:<br>(0) update coa {<br>ASSERT FAILED evaluate.c[1154]: output_vps<br>Aborted (core dumped)<br><br>I'm using freeradius version 3.0 (I have tried it with radius version 2.1.10, error was slightly different go a segmentation fault)<br><br>here is the code within sites-enables/default<br><br>update coa {<br> User-Name = "%{User-Name}"<br> Acct-Session-Id = "%{Acct-Session-Id}"<br> NAS-IP-Address = "%{NAS-IP-Address}"<br> Framed-IP-Address = "%{Framed-IP-Address}"<br> Mikrotik-Rate-Limit = "256K/256K"<br>}<br><br>This is send from accounting {<br><br> <br>I put originate-coa in the sites-enabled<br><br>and I have made the folowing config:<br> <br>home_server mikrotik-test-coa {<br> type = coa<br><br> #<br> # Note that a home server of type "coa" MUST be a real NAS,<br> # with an ipaddr or ipv6addr. It CANNOT point to a virtual<br> # server.<br> #<br> <br> ipaddr = 192.168.8.97<br> port = 3799<br><br> # This secret SHOULD NOT be the same as the shared<br> # secret in a "client" section.<br> secret = <same as in clients.conf, because in the NAS it is the same><br><br> # CoA specific parameters. See raddb/proxy.conf for details.<br> coa {<br> irt = 2<br> mrt = 16<br> mrc = 5<br> mrd = 30<br> }<br>}<br><br>server originate-coa.mikrotik {<br> pre-proxy {<br># update proxy-request {<br># NAS-IP-Address = 127.0.0.1<br># }<br> ok<br> }<br><br> #<br> # Handle the responses here.<br> #<br><br> post-proxy {<br> switch "%{proxy-reply:Packet-Type}" {<br> case CoA-ACK {<br> ok<br> }<br><br> case CoA-NAK {<br> # the NAS didn't like the CoA request<br> ok<br> }<br><br> case Disconnect-ACK {<br> ok<br> }<br><br> case Disconnect-NAK {<br> # the NAS didn't like the Disconnect request<br> ok<br> }<br><br> # Invalid packet type. This shouldn't happen.<br> case {<br> fail<br> }<br> }<br><br> #<br> # These methods are run when there is NO response<br> # to the request.<br> #<br> Post-Proxy-Type Fail-CoA {<br> ok<br> }<br><br> Post-Proxy-Type Fail-Disconnect {<br> ok<br> }<br> }<br>}<br><br><br>I have tried many many different settings in originate-coa<br><br>when I use radclient I can send a coa with succes.<br> </div>
<br>-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html</div> </div></body>
</html>