search

billleblanc / netopeer

Automatically exported from code.google.com/p/netopeer
0 stars 0 forks source link

using ncclient causes a segfault in netopeer-server #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use ncclient and try edit config
2. netopeer-server segfaults
3. The same request works correctly when using netopeer-cli 

Crash Data:
netopeer-server[2355]: segfault at 2c ip b67a6d50 sp bfa9f200 error 4 in 
libaugeas.so.0.18.0[b67a0000+56000]

This might have something to do with the xml namespaces. 

1. The same request from netopeer-cli works correctly. 
The request as sent by netopeer-cli 

<?xml version="1.0" encoding="UTF-8"?>#012<rpc 
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="7">#012  
<edit-config>#012    <target>#012      <running/>#012    </target>#012    
<config>#012      <system xmlns="urn:avaya:params:xml:ns:yang:ona100">#012      
  <status>#012          <device-status>green</device-status>#012        
</status>#012      </system>#012    </config>#012  </edit-config>#012</rpc>

2. The request sent by ncclient. This causes the crash 

 <?xml version="1.0" encoding="UTF-8"?>#012<nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:ns1="urn:avaya:params:xml:ns:yang:ona100" message-id="urn:uuid:c9d007ea-d29c-11e4-87b8-080027ba1a92">#012  <nc:edit-config>#012    <nc:target>#012      <nc:candidate/>#012    </nc:target>#012    <config>#012      <ns1:system>#012        <ns1:status>#012          <ns1:device-status>green</ns1:device-status>#012        </ns1:status>#012      </ns1:system>#012    </config>#012  </nc:edit-config>#012</nc:rpc>

Original issue reported on code.google.com by vivekatr...@gmail.com on 25 Mar 2015 at 4:04

GoogleCodeExporter commented 9 years ago 
The problem is at the transAPI module system in namespace 
"urn:avaya:params:xml:ns:yang:ona100" which is not a part of netopeer.

Original comment by rkre...@cesnet.cz on 7 Apr 2015 at 9:27