indutny / indutny/node-netroute
getInfo() returns undefined on Raspbian (Ubuntu) on Raspberry Pi
- Dominant language
- C++
- Stars
- 47
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Testing with node v0.10.36 at the moment, but I'll also try on io.js v1.2.0 (once fixes for armv6 support are merged back in).
`test-netroute.js`:
``` javascript
'use strict';
console.log(
require('netroute')
, require('netroute').getInfo()
, require('netroute').getGateway()
);
```
``` bash
node test-netroute.js
/home/pi/holepunch/node_modules/netroute/lib/netroute.js:10
def = info.IPv4.filter(function(route) {
^
TypeError: Cannot read property 'IPv4' of undefined
at Object.getGateway (/home/pi/holepunch/node_modules/netroute/lib/netroute.js:10:13)
at Object. (/home/pi/holepunch/test-netroute.js:6:23)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:929:3
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the report with test-netroute.js on Raspbian and inspect lib/netroute.js, especially getInfo() and the getGateway() call at line 10. Trace why the route data is undefined on this platform; done means the reported calls return usable route information without the shown TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100