This is an old revision of the document!
Table of Contents
help/documentation for myip services under BALUG.org
http/https
https/http URLs for the services:
http or https may be use with their respective default ports 80 and 443,
domain names that may be used:
- www.balug.org (dual stack: this service available via IPv4 and IPv6)
- www.ipv4.balug.org (this service available only via IPv4)
- www.ipv6.balug.org (this service available only via IPv6)
Note that in the above, if the www. prefix is omitted, will HTTP redirect to include the www. prefix.
Path portion of URL/URI:
/myip
/srcip may alternatively be used, but it may not be canonical, and may go away in future
So, e.g:
https://www.balug.org/myip http://www.balug.org/myip
https://www.ipv4.balug.org/myip http://www.ipv4.balug.org/myip
https://www.ipv6.balug.org/myip http://www.ipv6.balug.org/myip
ssh
domain names that may be used:
- balug.org (dual stack: this service available via IPv4 and IPv6)
- ipv4.balug.org (this service available only via IPv4)
- ipv6.balug.org (this service available only via IPv6)
Note that the above may optionally be prefixed by www.
user / login name, use myip, e.g. ssh -T myip@balug.org
or ssh -l myip -T balug.org
There is no password and password is neither needed nor requested.
No pseudo-terminal allocation will not occur, so may want to use -T option or equivalent option/setting.
ssh fingerprints, see DNSSEC secured DNS SSHFP records, for many clients, may also be able to use, e.g.:
ssh -T -o VerifyHostKeyDNS=yes myip@balug.org
One may also want to put suitable configuration options in ~/.ssh/config or equivalent, e.g.:
Host balug.org balug.org. *.balug.org *.balug.org. User myip RequestTTY no VerifyHostKeyDNS yes
so one can then conveniently do something like just: ssh balug.org
The command is forced, however one may give a single command matching exactly one of these:
- myconnection
- SSH_CONNECTION
in which case the output is instead of just the first value from SSH_CONNECTION from the environment,
the full content of the SSH_CONNECTION, which
is described on ssh(1):
SSH_CONNECTION Identifies the client and server ends of the con- nection. The variable contains four space-sepa- rated values: client IP address, client port num- ber, server IP address, and server port number.
E.g.:
$ ssh -T -o VerifyHostKeyDNS=yes myip@balug.org myconnection 96.86.170.226 53136 96.86.170.229 22 $ ssh -T -o VerifyHostKeyDNS=yes myip@ipv6.balug.org SSH_CONNECTION 2001:470:67:76f::2 58882 2001:470:1f05:19e::2 22 $
In any of these cases, the output is terminated by a single newline character.
concept/design/alpha/beta - not yet implemented in production
list
list is exclusive and takes no value(s)
help
help is exclusive and takes no value(s)