[BALUG-Talk] http[s]://{www., }{, ipv[46].}balug.org/{myip, srcip, myconnection, *}

[Michael Paoli]

Not for high-volume use, not a high availability nor high bandwidth
service, but ...

http[s]://{www,}{,.ipv[46]}.balug.org/{myip,srcip,myconnection,*}

Want to know your (Internet) source IP address ... for
IPv4?:
$ curl https://www.ipv4.balug.org/myip
198.144.194.235
$
IPv6?:
$ curl https://www.ipv6.balug.org/myip
2001:470:66:76f::2
$
What about source IP and port, and likewise for target:
$ curl https://www.ipv6.balug.org/myconnection
2001:470:66:76f::2 50265 2001:470:1f04:19e::2 443
$

Anyway, (notably not that balug.org is also off of DreamHost.com, yay!)
implemented similar for BALUG what I'd earlier implemented for
SF-LUG with those URLs.

If one uses, e.g.:
https://www.balug.org/myip
one may connect and see IPv4, or IPv6 IP (server is dual stack).
$ wget -4 -q -O - https://www.balug.org/myip
198.144.194.235
$ wget -6 -q -O - https://www.balug.org/myip
2001:470:66:76f::2
$
The URLs with ipv4 or ipv6 in the host (DNS) name are *only* IPv4 or
IPv6, respectively.  That can be handy when, e.g. one has a client
where one can't (feasibly) tell the client to only use IPv4 or IPv6.

Can also use http instead of https (and will all the further lack of
assurances on http with the traffic then in the clear).

And balug ... one less character to type than sf-lug.  ;-)

references/excerpts:

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> To: SF-LUG <sf-lug@linuxmafia.com>
> Subject:  
> http[s]://{www,}{,.ipv[46]}.sf-lug.org/{myip,srcip,myconnection,*}  
> ... m-net.arbornet.org
> Date: Thu, 22 Jun 2017 06:58:06 -0700

> Now also working with https,
> and also handy URL portions ending with /myip, /srcip, /myconnection,
> e.g.:
> $ curl -s https://www.ipv4.sf-lug.org/myip
> 99.95.107.156
> $ curl -s https://www.ipv4.sf-lug.org/myconnection
> 99.95.107.156 64316 198.144.194.238 443
> $ curl -s https://www.ipv6.sf-lug.org/srcip
> 2001:470:66:76f::2
> $ curl -s http://www.ipv6.sf-lug.org/myconnection
> 2001:470:66:76f::2 40862 2001:470:1f04:19e::2 80
> $
> (/myip and /srcip are equivalent)
> Some of those may be particularly useful when you're behind
> layer(s) of NAT/SNAT, and also, as essentially noted earlier,
> if/when you want to explicitly check IPv4 or IPv6 - particularly
> if you're using a client that one can't (reasonably) specify
> which protocol on the client itself (e.g. mobile browser on
> "smartphone").
>
>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> To: SF-LUG <sf-lug@linuxmafia.com>
>> Subject: http://www.ipv4.sf-lug.org/ http://ipv4.sf-lug.org/
>> Date: Sun, 18 Jun 2017 14:16:13 -0700
>
>> And for those that may find it useful,
>> if/when you want/need to hit only IPv4, I've also added:
>> http://www.ipv4.sf-lug.org/
>> http://ipv4.sf-lug.org/
>> With the former of those two being the canonical form.
>>
>> So long as you don't have need/reason to restrict to IPv4 only,
>> should just use the canonical form:
>> http://www.sf-lug.org/
>> or
>> https://www.sf-lug.org/
>>
>> One can also often restrict to just IPv4 or IPv6 with
>> the client ... but not all clients offer such an option
>> (e.g. dual stack mobile device may not offer such an option).
>>
>> What about?:
>> https://www.ipv4.sf-lug.org/
>> https://ipv4.sf-lug.org/
>> I don't have corresponding cert added yet, but expect
>> I'll have that completed before 2016-08-20T01:30:00+0000.
>> Until I add such cert, they "work" - notwihstanding cert
>> not having those newer names included.
>>
>> I didn't add similar for .com, as it's non-canonical anyway.
>>
>>> Date: Tue, 01 Dec 2015 17:33:28 -0800
>>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>>> To: SF-LUG <sf-lug@linuxmafia.com>
>>> Subject: [www.]ipv6.sf-lug.{org,com} [Re: SF-LUG & IPv6 :-)]
>>>
>>> And for those that may be interested, curious, or might find it useful,
>>> if one accesses the sf-lug website via any of these DNS names in the URLs:
>>> http://www.ipv6.sf-lug.org/
>>> http://ipv6.sf-lug.org/
>>> http://www.ipv6.sf-lug.com/
>>> http://ipv6.sf-lug.com/
>>> One gets IPv6 only access to the site (it won't work if you don't  
>>> have IPv6).
>>> Same content, just alternatives names (with the "ipv6." portion added)
>>> to access via IPv6 only if/when one may want to do or test that.
>>> If one doesn't include the "ipv6." portion, the site has both IPv6 and
>>> IPv4, so one doesn't have to use ipv6 names (unless one wants to exclude
>>> IPv4).
>>>
>>>
>>>> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
>>>> Subject: SF-LUG & IPv6 :-)
>>>> Date: Sat, 28 Nov 2015 11:29:32 -0800
>>>
>>>> The SF-LUG websites
>>>> http://([www.]sf-lug.{org,com}/
>>>> now also have IPv6.
>>>> Do use the DNS names, as not only may IPv6 addresses change,
>>>> but the web server also uses virtual name hosting, and presently
>>>> hosts more than just
>>>> SF-LUG content.
>>>>
>>>> Note that the list host (linuxmafia.com) does not (yet?) have IPv6.
>>>>
>>>> Also, many of the BALUG.org sites now have IPv6 (notably BALUG
>>>> ancillary sites
>>>> (e.g. archive & wiki sites), but not yet [www.]balug.org itself),
>>>> but these don't
>>>> yet have full chain of IPv6 DNS servers (alas, balug.org hosting
>>>> provider has no
>>>> IPv6 DNS servers).