multiple IPs
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
How can I get my IPs from this configuration :
me@here:~/nodejs-projects/tim$ ifconfig
enp4s0 Link encap:Ethernet HWaddr 00:04:ac:f3:62:d0
inet addr:192.168.1.254 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::204:acff:fef3:62d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4900576 errors:0 dropped:0 overruns:0 frame:0
TX packets:3296566 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4577415638 (4.5 GB) TX bytes:550292783 (550.2 MB)
enp4s5 Link encap:Ethernet HWaddr 00:15:17:5c:9e:55
inet addr:10.139.238.194 Bcast:10.139.238.223 Mask:255.255.255.224
inet6 addr: fe80::215:17ff:fe5c:9e55/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4581022 errors:0 dropped:274 overruns:0 frame:0
TX packets:5786250 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:779326013 (779.3 MB) TX bytes:5233689092 (5.2 GB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:162008 errors:0 dropped:0 overruns:0 frame:0
TX packets:162008 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:50482196 (50.4 MB) TX bytes:50482196 (50.4 MB)
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file or test is named; start by reviewing node-ip's existing API and the behavior requested for the interfaces shown by ifconfig. Done would require a clearly defined way to retrieve multiple configured IPs, along with documented expected behavior and coverage for this configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100