twisla/roro9stack
Public Access
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Releases 25 Activity

Shell: ping, nslookup, port, traceroute, ifconfig and arp (#90) #91

Merged
twisla merged 2 commits from net-tools into main 2026-10-08 00:38:19 +00:00
Conversation 0 Commits 2 Files Changed 16
+969 -6
2 Commits
Author SHA1 Message Date
twislaandClaude Opus 5.5 a8f267416b N1: the network commands ship as v0.20.0
CI / build (pull_request) Successful in 1m37s
Details
Site / build (pull_request) Successful in 13s
Details 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
 2026-10-08 02:35:49 +02:00
twislaandClaude Opus 5.5 ed7abdcaf5 Shell: ping, nslookup, port, traceroute, ifconfig and arp (#90)
CI / build (pull_request) Successful in 1m38s
Details
Site / build (pull_request) Successful in 11s
Details 
Network troubleshooting from the device itself, in the Shell and over both
consoles. ping, nslookup, port and traceroute each run on a task of their
own and print as they go, to the console that asked; one at a time, and
`cancel` stops it. ifconfig and arp answer at once: the interfaces (Wi-Fi
and the VPN), which is the default route, the DNS servers, the neighbours.

nslookup asks a DNS server itself, so it can say which server answered and
in how long, and ask another. A sized ping finds what a tunnel really
carries.

With a how-to, "When the network doesn't work", and the rest of the docs.
tls, ntp and netstat from the issue's list are not in this.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
 2026-10-08 02:29:04 +02:00