HI,
IIRC there is a way of finding out the IP addresses of devices connected
to a RISC OS m/c but for the life of me I can't remember what it was or
where I wrote it down. Can anyone help please?
Theo <theom+news@chiark.greenend.org.uk> wrote:
Chris Newman <cvjazz@waitrose.com> wrote:
HI, IIRC there is a way of finding out the IP addresses of devices connected to a RISC OS m/c but for the life of me I can't remember
what it was or where I wrote it down. Can anyone help please?
Try *arp -a
Or possibly *inetstat
(*arp -a tells you the IP addresses of everything the machine knows
about, *inetstat tells you what has open TCP connections right now or
has recently closed, including their ports)
Chris Newman <cvjazz@waitrose.com> wrote:
HI,
IIRC there is a way of finding out the IP addresses of devices connected
to a RISC OS m/c but for the life of me I can't remember what it was or where I wrote it down. Can anyone help please?
Try *arp -a
In article <huk*67XCy@news.chiark.greenend.org.uk>, Theo <theom+news@chiark.greenend.org.uk> wrote:
Theo <theom+news@chiark.greenend.org.uk> wrote:
Chris Newman <cvjazz@waitrose.com> wrote:
HI, IIRC there is a way of finding out the IP addresses of
devices connected to a RISC OS m/c but for the life of me I
can't remember what it was or where I wrote it down. Can
anyone help please?
Try *arp -a
Or possibly *inetstat
(*arp -a tells you the IP addresses of everything the machine
knows about, *inetstat tells you what has open TCP connections
right now or has recently closed, including their ports)
Thanks, Theo. That was exciting. Lots of stuff to look at. Now to
see what I recognize and what matches what. Much obliged.
How confusing... RISC OS 6.20
Here *arp -a Displays "route-sysctl-estimate"
*inetstat Displays "kvm_nlist:"
I have no idea what either of those mean?
In article <huk*67XCy@news.chiark.greenend.org.uk>, Theo <theom+news@chiark.greenend.org.uk> wrote:
Theo <theom+news@chiark.greenend.org.uk> wrote:
Chris Newman <cvjazz@waitrose.com> wrote:
HI, IIRC there is a way of finding out the IP addresses of devices connected to a RISC OS m/c but for the life of me I can't remember
what it was or where I wrote it down. Can anyone help please?
Try *arp -a
Or possibly *inetstat
(*arp -a tells you the IP addresses of everything the machine knows
about, *inetstat tells you what has open TCP connections right now or
has recently closed, including their ports)
Thanks, Theo. That was exciting. Lots of stuff to look at. Now to see
what I recognize and what matches what. Much obliged.
On 29/12/2021 19:26, Dave wrote:
How confusing... RISC OS 6.20
Here *arp -a Displays "route-sysctl-estimate"
*inetstat Displays "kvm_nlist:"
I have no idea what either of those mean?
Try posting the full output.
---druck
That is all I get...
What else should I get?
Dave
Straight out of the Task window.
*arp -a
route-sysctl-estimate
*
*inetstat
InetStat: kvm_nlist:
*
Dave <dave@triffid.co.uk> wrote:
That is all I get...
What else should I get?
Dave
Straight out of the Task window.
*arp -a
route-sysctl-estimate
*
*inetstat
InetStat: kvm_nlist:
*
I think you're on VRPC? That doesn't have a RISC OS network stack, it
just piggybacks on Windows'. Hence commands for talking to the RISC OS network stack don't work.
Theo
In article <fuk*xwZCy@news.chiark.greenend.org.uk>, Theo
<theom+news@chiark.greenend.org.uk> wrote:
Dave <dave@triffid.co.uk> wrote:
That is all I get...
What else should I get?
Dave
Straight out of the Task window.
*arp -a route-sysctl-estimate * *inetstat InetStat: kvm_nlist: *
I think you're on VRPC? That doesn't have a RISC OS network stack,
it just piggybacks on Windows'. Hence commands for talking to the
RISC OS network stack don't work.
Theo
Yes indeed it is VRPC.
I've now just run my old hardware SARPC (RISC OS 6.20) and get a
different result for *arp -a
*arp -a router (192.168.0.1) at e8:48: Redacted. faypc (192.168.0.3) at 94:de: Redacted. blackfan (192.168.0.4) at 1c:1b: Redacted. ? (192.168.0.255) at (incomplete) * *inetstat * *fwshow No remote nets
Oooer! I seem to have opened a little thread for discussion (AKA minnie
can of worms).
What does redacted mean? Is there a big black line through it like
government documents?
I also got some marked "incomplete". What does that mean?
Chris Newman <cvjazz@waitrose.com> wrote:
Oooer! I seem to have opened a little thread for discussion (AKA minnie
can of worms).
What does redacted mean? Is there a big black line through it like government documents?
I think that just means Dave removed some of the information to avoid
posting the exact MAC addresses on his system (which aren't a major
privacy risk in general, but fair enough)
I also got some marked "incomplete". What does that mean?
*arp -a just gives a dump of the ARP cache - the mappings of IPs to MACs
that the machine has used recently.
'Incomplete' means the system tried to do an ARP request for a
particular IP but the ARP request failed. For example, you tried to
talk to a machine that is turned off - you wanted to talk to
192.168.1.33 so your machine tried to work out what MAC address has that
by issuing an ARP request. But the machine was turned off, so your
machine opened the entry in the ARP table but nobody replied with a MAC address to fill it in. Similarly broadcast addresses won't have anyone
reply to the ARP request because there isn't a real machine at that
address.
Theo
In article <59a2d2d972dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:
In article <fuk*xwZCy@news.chiark.greenend.org.uk>, Theo
<theom+news@chiark.greenend.org.uk> wrote:
Dave <dave@triffid.co.uk> wrote:
That is all I get...
What else should I get?
Dave
Straight out of the Task window.
*arp -a route-sysctl-estimate * *inetstat InetStat: kvm_nlist: *
I think you're on VRPC? That doesn't have a RISC OS network stack,
it just piggybacks on Windows'. Hence commands for talking to the
RISC OS network stack don't work.
Theo
Yes indeed it is VRPC.
I've now just run my old hardware SARPC (RISC OS 6.20) and get a
different result for *arp -a
*arp -a router (192.168.0.1) at e8:48: Redacted.
faypc (192.168.0.3) at 94:de: Redacted.
blackfan (192.168.0.4) at 1c:1b: Redacted.
(192.168.0.255) at (incomplete)
Oooer! I seem to have opened a little thread for discussion (AKA minnie
can of worms).
What does redacted mean? Is there a big black line through it like
government documents?
I also got some marked "incomplete". What does that mean?
What does redacted mean? Is there a big black line through it like government documents?
I also got some marked "incomplete". What does that mean?
Chris, Theo has answered concisely... but one expansion...
It is somewhat difficult in an email to black line out some
text/numerics, so to indicate I had removed some of the MAC data for
each device (Security) I replaced the missing with "Redacted".
In article <59a27e6d5ccvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:
In article <huk*67XCy@news.chiark.greenend.org.uk>, Theo <theom+news@chiark.greenend.org.uk> wrote:
Theo <theom+news@chiark.greenend.org.uk> wrote:
Chris Newman <cvjazz@waitrose.com> wrote:
HI, IIRC there is a way of finding out the IP addresses of
devices connected to a RISC OS m/c but for the life of me I
can't remember what it was or where I wrote it down. Can
anyone help please?
Try *arp -a
Or possibly *inetstat
(*arp -a tells you the IP addresses of everything the machine
knows about, *inetstat tells you what has open TCP connections
right now or has recently closed, including their ports)
Thanks, Theo. That was exciting. Lots of stuff to look at. Now to
see what I recognize and what matches what. Much obliged.
The original question did not seem to clarify if you wanted the
- WAN Internet IP that RISC OS apps are connected to
*inetstat gives these
- LAN local IP that RISC OS knows about
*arp -a gives these
*fwshow gives discs and hosts connected using ShareFS
- LAN local IP that are connected to your network
If you have a phone or tablet then WiFiMan or one of the many
other similar apps can list all LAN devices. (iStuff may be more
restricted)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 41:55:14 |
Calls: | 6,648 |
Files: | 12,193 |
Messages: | 5,329,573 |