Hi,

on my computer, I can enter an address such as

http://[2a02:...:59cd]:port/

into Firefox to access my home server on IPv6. But on my Android phone,
Firefox instead asks google to find that string and fails to connect.

Do you know why?

Is there some other syntax that works?

--
Cheers, Carlos.

"Carlos E.R." <robin_listas@es.invalid> wrote:

> Hi,
>
> on my computer, I can enter an address such as
>
> http://[2a02:...:59cd]:port/
>
> into Firefox to access my home server on IPv6. But on my Android phone,
> Firefox instead asks google to find that string and fails to connect.
>
> Do you know why?
>
> Is there some other syntax that works?

Is IPv6 enabled for wi-fi connects?

On my old LG phone (your navpath will differ), I go to:

Android settings
--> Network
--> Mobile networks
--> Access Point Names
select the APN that I'm using
--> APN Protocol
check IPv4 and IPv6 are selected

Presumably you used brackets to encompass the IPv6 address although
those are not legal characters in an IP address.

On 18/04/2023 22:40, Carlos E.R. wrote:
>
> on my computer, I can enter an address such as
>
> http://[2a02:...:59cd]:port/
>
> into Firefox to access my home server on IPv6. But on my Android phone,
> Firefox instead asks google to find that string and fails to connect.

IIRC, in about:config set keyword.enabled = false.

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

On 2023-04-19 00:44, VanguardLH wrote:
> "Carlos E.R." <robin_listas@es.invalid> wrote:
>
>> Hi,
>>
>> on my computer, I can enter an address such as
>>
>> http://[2a02:...:59cd]:port/
>>
>> into Firefox to access my home server on IPv6. But on my Android phone,
>> Firefox instead asks google to find that string and fails to connect.
>>
>> Do you know why?
>>
>> Is there some other syntax that works?
>
> Is IPv6 enabled for wi-fi connects?

I have both WiFi and "phone" connectivity on IPv6. The phone passes all
the tests on https://test-ipv6.com

> Presumably you used brackets to encompass the IPv6 address although
> those are not legal characters in an IP address.

Then how do you enter legally an IPv6 address directly in firefox in the
phone?

That exact syntax works perfectly on the computer FF.

--
Cheers, Carlos.

On 2023-04-19 00:53, Java Jive wrote:
> On 18/04/2023 22:40, Carlos E.R. wrote:
>>
>> on my computer, I can enter an address such as
>>
>> http://[2a02:...:59cd]:port/
>>
>> into Firefox to access my home server on IPv6. But on my Android
>> phone, Firefox instead asks google to find that string and fails to
>> connect.
>
> IIRC, in about:config set keyword.enabled = false.
>

about:config produces a blank, white, page in FF in my Android.

--
Cheers, Carlos.

"Carlos E.R." <robin_listas@es.invalid> wrote:

> Java Jive wrote:
>
>> Carlos E.R. wrote:
>>>
>>> on my computer, I can enter an address such as
>>>
>>> http://[2a02:...:59cd]:port/
>>>
>>> into Firefox to access my home server on IPv6. But on my Android
>>> phone, Firefox instead asks google to find that string and fails to
>>> connect.
>>
>> IIRC, in about:config set keyword.enabled = false.
>
> about:config produces a blank, white, page in FF in my Android.

Yeah, Mozilla decided users on mobile devices are too stupid to be
getting into the advanced configuration settings.

about:config used to be available in the standard release, but now it is
available only in the nightly and beta versions. For the mobile
version, many preferences are baked into the GeckoView engine when the
product is built, and others reset when you exit Firefox (it's one of
the few, maybe only, mobile web browsers that has an Exit function that
actually unloads the process instead of backgrounding it). Apparently
some settings will break the Firefox app with data loss.

https://en.wikipedia.org/wiki/Firefox_for_Android
"Version 68.11.0: July 27, 2020. Last version to support Android
4.1–4.4,[235] also the last version to display the about:config page in
consumer releases."
"Version 79.0: August 27, 2020. First version based on GeckoView
engine.[236] New extension framework. about:config is available only in
Nightly releases."

I don't know if Mozilla continued to display the internal about:config
page. I don't bother with nightly and beta releases to test.

There are so many settings that are not available in Firefox Mobile, and
with the total absence of about:config, that sometimes I ponder if
Firefox is any more secure or private than using Chrome.

https://bugzilla.mozilla.org/show_bug.cgi?id=1500541
Make about:config work in GeckoView
Opened 5 years ago.
Closed 5 years ago.
Status: RESOLVED FIXED

Before it got closed, it changed to wontfix status. Mozilla is NOT
going to add about:config for their GeckoView based mobile web browser.

So, Mozilla's attitude toward bringing an equally configurable web
browser to the mobile platform is ... fuck the users! Not exactly
conducive to eliciting loyalty amongst users.

The setting Java noted was to eliminate Firefox (desktop) from ever
doing searches on URLs it doesn't understand. Alas, no way to use
about:config in Firefox for Android.

"Carlos E.R." <robin_listas@es.invalid> wrote:

> VanguardLH wrote:
>
>> "Carlos E.R." <robin_listas@es.invalid> wrote:
>>
>>> on my computer, I can enter an address such as
>>>
>>> http://[2a02:...:59cd]:port/
>>>
>>> into Firefox to access my home server on IPv6. But on my Android
>>> phone, Firefox instead asks google to find that string and fails to
>>> connect.
>>>
>>> Do you know why?
>>>
>>> Is there some other syntax that works?
>>
>> Is IPv6 enabled for wi-fi connects?
>
> I have both WiFi and "phone" connectivity on IPv6. The phone passes all
> the tests on https://test-ipv6.com
>
>> Presumably you used brackets to encompass the IPv6 address although
>> those are not legal characters in an IP address.
>
> Then how do you enter legally an IPv6 address directly in firefox in the
> phone?
>
> That exact syntax works perfectly on the computer FF.

Web browsers have long been deliberatly sloppy in what you enter in the
address field. Codebase is larger for desktop web browsers than mobile
web browsers.

However, I just checked. Colons in IPv6 syntax would conflict with
their use for the protocol delineation (http://) and with port number
designation (http://hostname:port). So, you're correct in using
brackets. My bad.

https://en.wikiversity.org/wiki/IPv6#Use_in_URLs

https://datatracker.ietf.org/doc/html/rfc2732

I did an nslookup on www.intel.com which returned a couple of IPv6
addresses. With or without the brackets, Firefox Desktop refused to
connect to the site. Without brackets, Firefox redirects the URL to
whatever is the default search engine configured in the web browser.
With brackets, Firefox pukes a certificate warning. Apparently the is
no nameserver lookup on the IPv6 address to return a hostname which is
what the certificate specifies for which domains that certificate is
valid.

Nowadays it is getting hard to find HTTP sites (no certs). I found some
bookmarks in my Firefox that only use HTTP (so no cert); however, none
of them had an IPv6 address.

I haven't ran across using IPv6 addresses in Firefox, or in any web
browser. Rarely have I even had to use IPv4 addresses. The prevalent
case is specifying a hostname for a DNS lookup, but the client will
still present the hostname on connecting with the site to perform the
cert check. So, just off the top of my head, what about adding a
hostname to your server, and using the hostname instead? There are free
DNS lookup services. Some have a client you install that reports to
your free DNS lookup account what is the current IP address of your
server host to keep your DNS lookup account in sync with whatever is
your current server's IP address. If you have a static IP address for
your server host, you don't need the dynamic DNS updater client.

https://support.opendns.com/hc/en-us/articles/227987867-What-is-the-OpenDNS-Dynamic-IP-updater-client-

I remember using OpenDNS a few years ago, but stopped after they stopped
their free DNS nameserver service (you specify a hostname, OpenDNS
nameserver has the A record for your client's DNS lookup, OpenDNS
returns the IP address to your client). If you have a dynamic IP
address assigned to you by your ISP (the typical case), you needed their
updater client to update your OpenDNS account with whatever was the
current IP address of your host. My recollection is that I used them
when I wanted a hostname instead of knowing what was the current IP
address of my home computer to remotely connect to it via VNC.

These type of services are often called dynamic DNS (DDNS) providers. I
remember playing with No-IP and DynDNS for awhile for DNS lookup
redirection. I haven't played with DDNS for years. Some routers even
have options to support specific DDNS providers, so you don't need to
run a DDNS updater client on your "server" host. Might find more recent
info in an online search, like:

https://www.google.com/search?q=free+ddns

That's just a thought on how to use DDNS to let you specify a hostname
with the DDNS service doing the "lookup" (returning the IP address
configured in your DDNS account). Else, what about trying the decimal
IP address format?

https://www.ipaddressguide.com/ipv6-to-decimal

My IPv6 address of the WAN-side of my router/cable modem converts to a
38-digit decimal number.

If you run "ipconfig /all" in a command shell, is an IPv6 address
assigned to your NIC(s) on your server host? Does your router, cable
modem, or whatever is your WAN device support IPv6? I had routers for a
long time after IPv6 started getting popular that only supported IPv4,
so no way to get an IPv6 assigned to it for its WAN-side port. Are you
trying to connnect to your intranet host past the WAN-side interface of
your router/modem? If so, you need an IPv6 address for the WAN-side of
the router to which you connect, and a rule in its firewall to punch a
hole to redirect connects to your router to whichever intranet host
you're using as your server. Or, are you only making IPv6 connects from
other intranet hosts to your intranet server host (i.e., connects to
your server host are local)?

On 2023-04-19 04:42, VanguardLH wrote:
> "Carlos E.R." <robin_listas@es.invalid> wrote:
>
>> VanguardLH wrote:
>>
>>> "Carlos E.R." <robin_listas@es.invalid> wrote:
>>>
>>>> on my computer, I can enter an address such as
>>>>
>>>> http://[2a02:...:59cd]:port/
>>>>
>>>> into Firefox to access my home server on IPv6. But on my Android
>>>> phone, Firefox instead asks google to find that string and fails to
>>>> connect.
>>>>
>>>> Do you know why?
>>>>
>>>> Is there some other syntax that works?
>>>
>>> Is IPv6 enabled for wi-fi connects?
>>
>> I have both WiFi and "phone" connectivity on IPv6. The phone passes all
>> the tests on https://test-ipv6.com
>>
>>> Presumably you used brackets to encompass the IPv6 address although
>>> those are not legal characters in an IP address.
>>
>> Then how do you enter legally an IPv6 address directly in firefox in the
>> phone?
>>
>> That exact syntax works perfectly on the computer FF.
>
> Web browsers have long been deliberatly sloppy in what you enter in the
> address field. Codebase is larger for desktop web browsers than mobile
> web browsers.
>
> However, I just checked. Colons in IPv6 syntax would conflict with
> their use for the protocol delineation (http://) and with port number
> designation (http://hostname:port). So, you're correct in using
> brackets. My bad.
>
> https://en.wikiversity.org/wiki/IPv6#Use_in_URLs
>
> https://datatracker.ietf.org/doc/html/rfc2732
>
> I did an nslookup on www.intel.com which returned a couple of IPv6
> addresses. With or without the brackets, Firefox Desktop refused to
> connect to the site. Without brackets, Firefox redirects the URL to
> whatever is the default search engine configured in the web browser.
> With brackets, Firefox pukes a certificate warning. Apparently the is
> no nameserver lookup on the IPv6 address to return a hostname which is
> what the certificate specifies for which domains that certificate is
> valid.

www.intel.com is an alias for intel11.cn.edgekey.net.
intel11.cn.edgekey.net is an alias for e7842.dsca.akamaiedge.net.
e7842.dsca.akamaiedge.net has address 23.73.169.197
e7842.dsca.akamaiedge.net has IPv6 address 2a02:26f0:e0:49f::1ea2
e7842.dsca.akamaiedge.net has IPv6 address 2a02:26f0:e0:490::1ea2
cer@Telcontar:~>

cer@Telcontar:~> curl http://[2a02:26f0:e0:49f::1ea2]
<HTML><HEAD>
<TITLE>Invalid URL</TITLE>
</HEAD><BODY>
<H1>Invalid URL</H1>
The requested URL "&#91;no&#32;URL&#93;", is invalid.<p>
Reference&#32;&#35;9&#46;b6251102&#46;1681896411&#46;220ce511
</BODY></HTML>
cer@Telcontar:~>

As you can see, it actually works.

cer@Telcontar:~> host google.es
google.es has address 142.250.184.3
google.es has IPv6 address 2a00:1450:4003:80e::2003
google.es mail is handled by 0 smtp.google.com.
cer@Telcontar:~>

cer@Telcontar:~> curl http://[2a00:1450:4003:80e::2003]
<!DOCTYPE html>
<html lang=en>
<meta charset=utf-8>
<meta name=viewport content="initial-scale=1, minimum-scale=1,
width=device-width">
<title>Error 404 (Not Found)!!1</title>
<style>
*{margin:0;padding:0}html,code{font:15px/22px
arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7%
auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* >
body{background:url(//www.google.com/images/errors/robot.png) 100% 5px
no-repeat;padding-right:205px}p{margin:11px 0
22px;overflow:hidden}ins{color:#777;text-decoration:none}a
img{border:0}@media screen and
(max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png)
no-repeat;margin-left:-5px}@media only screen and
(min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png)
no-repeat 0% 0%/100%
100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png)
0}}@media only screen and
(-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png)
no-repeat;-webkit-background-size:100%
100%}}#logo{display:inline-block;height:54px;width:150px}
</style>
<a href=//www.google.com/><span id=logo aria-label=Google></span></a>
<p><b>404.</b> <ins>That’s an error.</ins>
<p>The requested URL <code>/</code> was not found on this server.
<ins>That’s all we know.</ins>
cer@Telcontar:~>

See? the http server at that address is responding.

>
> Nowadays it is getting hard to find HTTP sites (no certs). I found some
> bookmarks in my Firefox that only use HTTP (so no cert); however, none
> of them had an IPv6 address.
>
> I haven't ran across using IPv6 addresses in Firefox, or in any web
> browser.

I'm trying to see if my home server is accessible via IPv6, so the phone
is convenient as it is not in my LAN.

> Rarely have I even had to use IPv4 addresses. The prevalent
> case is specifying a hostname for a DNS lookup, but the client will
> still present the hostname on connecting with the site to perform the
> cert check. So, just off the top of my head, what about adding a
> hostname to your server, and using the hostname instead? There are free
> DNS lookup services. Some have a client you install that reports to
> your free DNS lookup account what is the current IP address of your
> server host to keep your DNS lookup account in sync with whatever is
> your current server's IP address. If you have a static IP address for
> your server host, you don't need the dynamic DNS updater client.

yes, I have a dyn dns, but I haven't tried to put my IPv6 there yet, and
anyway, I want to force FF to use IPv6 for testing purposes.

>
> If you run "ipconfig /all" in a command shell, is an IPv6 address
> assigned to your NIC(s) on your server host? Does your router, cable
> modem, or whatever is your WAN device support IPv6? I had routers for a
> long time after IPv6 started getting popular that only supported IPv4,
> so no way to get an IPv6 assigned to it for its WAN-side port. Are you
> trying to connnect to your intranet host past the WAN-side interface of
> your router/modem? If so, you need an IPv6 address for the WAN-side of
> the router to which you connect, and a rule in its firewall to punch a
> hole to redirect connects to your router to whichever intranet host
> you're using as your server. Or, are you only making IPv6 connects from
> other intranet hosts to your intranet server host (i.e., connects to
> your server host are local)?

My home server is indeed accesible directly over IPv6. As the phone
refused to collaborate, I sshed to the machine of a friend and tried
from there. It worked.

My problem here is only how to enter valid IPv6 addresses in the FF box.
Only that.

--
Cheers, Carlos.

On 19/04/2023 01:28, Carlos E.R. wrote:
> On 2023-04-19 00:53, Java Jive wrote:
>> On 18/04/2023 22:40, Carlos E.R. wrote:
>>>
>>> on my computer, I can enter an address such as
>>>
>>> http://[2a02:...:59cd]:port/
>>>
>>> into Firefox to access my home server on IPv6. But on my Android
>>> phone, Firefox instead asks google to find that string and fails to
>>> connect.
>>
>> IIRC, in about:config set keyword.enabled = false.
>
> about:config produces a blank, white, page in FF in my Android.

As VanguardLH has explained; sorry, I wasn't aware of that. I take it
this device has not been rooted? If perchance it has, perhaps you could
give the destination a name in its hosts file, and use that instead?

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

On 2023-04-19 12:15, Java Jive wrote:
> On 19/04/2023 01:28, Carlos E.R. wrote:
>> On 2023-04-19 00:53, Java Jive wrote:
>>> On 18/04/2023 22:40, Carlos E.R. wrote:
>>>>
>>>> on my computer, I can enter an address such as
>>>>
>>>> http://[2a02:...:59cd]:port/
>>>>
>>>> into Firefox to access my home server on IPv6. But on my Android
>>>> phone, Firefox instead asks google to find that string and fails to
>>>> connect.
>>>
>>> IIRC, in about:config set keyword.enabled = false.
>>
>> about:config produces a blank, white, page in FF in my Android.
>
> As VanguardLH has explained; sorry, I wasn't aware of that.  I take it
> this device has not been rooted?  If perchance it has, perhaps you could
> give the destination a name in its hosts file, and use that instead?

No, not routed.

--
Cheers, Carlos.

On 19/04/2023 11:42, Carlos E.R. wrote:
> On 2023-04-19 12:15, Java Jive wrote:
>> On 19/04/2023 01:28, Carlos E.R. wrote:
>>> On 2023-04-19 00:53, Java Jive wrote:
>>>> On 18/04/2023 22:40, Carlos E.R. wrote:
>>>>>
>>>>> on my computer, I can enter an address such as
>>>>>
>>>>> http://[2a02:...:59cd]:port/
>>>>>
>>>>> into Firefox to access my home server on IPv6. But on my Android
>>>>> phone, Firefox instead asks google to find that string and fails to
>>>>> connect.
>>>>
>>>> IIRC, in about:config set keyword.enabled = false.
>>>
>>> about:config produces a blank, white, page in FF in my Android.
>>
>> As VanguardLH has explained; sorry, I wasn't aware of that.  I take it
>> this device has not been rooted?  If perchance it has, perhaps you
>> could give the destination a name in its hosts file, and use that
>> instead?
>
> No, not routed.

I discovered the above setting as a fix for the problem of typing into
my laptop's browser address bar the machine names of servers on my LAN
taking me to search pages.

I've just been experimenting similarly with FF on my Android tablet.
I'm not sure that I've discovered anything useful to your problem, but
you must be the judge of that ...

I can make a connection to a server on my LAN by preceding either its
IP4 address or its name with (note the 's') ...
https://

There is also a FF setting ...

3 vertical dots top-right-hand corner
Settings, at the bottom
Search, first item
Show search suggestions, at the bottom

.... but its value makes no difference to my being able to make a
connection by preceding an IP4 address as above, nor to a bare server
name ending up in a search page if the secure protocol prefix is omitted.

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

On 2023-04-19 13:59, Java Jive wrote:
> On 19/04/2023 11:42, Carlos E.R. wrote:
>> On 2023-04-19 12:15, Java Jive wrote:
>>> On 19/04/2023 01:28, Carlos E.R. wrote:
>>>> On 2023-04-19 00:53, Java Jive wrote:
>>>>> On 18/04/2023 22:40, Carlos E.R. wrote:
>>>>>>
>>>>>> on my computer, I can enter an address such as
>>>>>>
>>>>>> http://[2a02:...:59cd]:port/
>>>>>>
>>>>>> into Firefox to access my home server on IPv6. But on my Android
>>>>>> phone, Firefox instead asks google to find that string and fails
>>>>>> to connect.
>>>>>
>>>>> IIRC, in about:config set keyword.enabled = false.
>>>>
>>>> about:config produces a blank, white, page in FF in my Android.
>>>
>>> As VanguardLH has explained; sorry, I wasn't aware of that.  I take
>>> it this device has not been rooted?  If perchance it has, perhaps you
>>> could give the destination a name in its hosts file, and use that
>>> instead?
>>
>> No, not routed.
>
> I discovered the above setting as a fix for the problem of typing into
> my laptop's browser address bar the machine names of servers on my LAN
> taking me to search pages.
>
> I've just been experimenting similarly with FF on my Android tablet. I'm
> not sure that I've discovered anything useful to your problem, but you
> must be the judge of that ...
>
> I can make a connection to a server on my LAN by preceding either its
> IP4 address or its name with (note the 's') ...
>     https://
>

IPv4 is not a problem.

No, https will not work. The server I need to connect to is http only.

> There is also a FF setting ...
>
>     3 vertical dots top-right-hand corner
>     Settings, at the bottom
>     Search, first item
>     Show search suggestions, at the bottom
>
> ... but its value makes no difference to my being able to make a
> connection by preceding an IP4 address as above, nor to a bare server
> name ending up in a search page if the secure protocol prefix is omitted.

Again, the problem I want to solve is solely how to enter an IPv6
numeric address in Firefox, or another browser, in Android.

Anything else is superfluous.

--
Cheers, Carlos.

On 19/04/2023 13:31, Carlos E.R. wrote:
>
> Again, the problem I want to solve is solely how to enter an IPv6
> numeric address in Firefox, or another browser, in Android.
>
> Anything else is superfluous.

No it's not, the problem you want to solve is to stop FF searching for
it instead, as in your OP ...

On 18/04/2023 22:40, Carlos E.R. wrote:
>
> But on my Android phone, Firefox instead asks google to find that
> string and fails to connect.

.... and what I posted has some relevance to that, though I grant is not
a solution to it.

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

Carlos E.R. wrote:

> the problem I want to solve is solely how to enter an IPv6 numeric
> address in Firefox, or another browser, in Android.

For a link-local IPv6 URL, which works from firefox on windows

http://[fe80::blah:blah]:9981/

firefox/fenix on android redirects it to my default search engine, other
people on reddit/github/bugzilla reporting the same ...

<https://bugzilla.mozilla.org/show_bug.cgi?id=1807752>

On 2023-04-19 15:18, Andy Burns wrote:
> Carlos E.R. wrote:
>
>> the problem I want to solve is solely how to enter an IPv6 numeric
>> address in Firefox, or another browser, in Android.
>
> For a link-local IPv6 URL, which works from firefox on windows
>
>     http://[fe80::blah:blah]:9981/
>
> firefox/fenix on android redirects it to my default search engine, other
> people on reddit/github/bugzilla reporting the same ...
>
>     <https://bugzilla.mozilla.org/show_bug.cgi?id=1807752>
>

I'm not interested (today) in link-local addresses, that's a long
standing bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=700999

The documented url syntax for link local is

http://[fe80::2d8:61ff:fea1:5abd%eth0]

But FF removed support for it long ago. If you need it, just use an old
FF copy (version 3.6.23)

I repeat: I only want to reach a standard public IPv6 address by typing
it in Android's firefox.

For the record, I just verified it works in Chrome.

--
Cheers, Carlos.

Carlos E.R. wrote:

> The documented url syntax for link local is
>
> http://[fe80::2d8:61ff:fea1:5abd%eth0]
>
> But FF removed support for it long ago.

as I said, it works for me on win11 latest firefox, without the %iface
suffix (why would that be needed?)

"Carlos E.R." <robin_listas@es.invalid> wrote:

> Andy Burns wrote:
>
>>     <https://bugzilla.mozilla.org/show_bug.cgi?id=1807752>
>
> I'm not interested (today) in link-local addresses,

I did not see where that bug report mentioned local links. The example
given was an IPv6 address for www.mozilla.org (I don't think the bug
reporter was on an internal network to reach Mozilla's web site).

Another one is:

https://github.com/mozilla-mobile/android-components/pull/5546

So, from those 2 tickets (might be more) seems Firefox Android
interprets IPv6 addresses which have to be enclosed in brackets as
search terms. Looks like you're screwed using Firefox Android with IPv6
addresses until Mozilla decides to prioritize the bugs to get the
product to work rather than focus on performance issues. If Chrome on
Android works, that what you'll have to use for now.

On 2023-04-19 22:37, VanguardLH wrote:
> "Carlos E.R." <robin_listas@es.invalid> wrote:
>
>> Andy Burns wrote:
>>
>>>     <https://bugzilla.mozilla.org/show_bug.cgi?id=1807752>
>>
>> I'm not interested (today) in link-local addresses,
>
> I did not see where that bug report mentioned local links. The example
> given was an IPv6 address for www.mozilla.org (I don't think the bug
> reporter was on an internal network to reach Mozilla's web site).
>
> Another one is:
>
> https://github.com/mozilla-mobile/android-components/pull/5546
>
> So, from those 2 tickets (might be more) seems Firefox Android
> interprets IPv6 addresses which have to be enclosed in brackets as
> search terms. Looks like you're screwed using Firefox Android with IPv6
> addresses until Mozilla decides to prioritize the bugs to get the
> product to work rather than focus on performance issues. If Chrome on
> Android works, that what you'll have to use for now.

Right.

It worked once, then I added a path and stopped working. Go figure.

--
Cheers, Carlos.

Carlos E.R. <robin_listas@es.invalid> wrote:
> It worked once, then I added a path and stopped working. Go figure.

According to:
https://github.com/mozilla-mobile/fenix/issues/4343

https://user:pass@[ipv6]

works. Not sure about adding a path, but maybe try:

https://u@[ipv6]

and see if that works? Then try paths on the end.

Theo

Theo <theom+news@chiark.greenend.org.uk> wrote:

> Carlos E.R. <robin_listas@es.invalid> wrote:
>
>> It worked once, then I added a path and stopped working. Go figure.
>
> According to:
> https://github.com/mozilla-mobile/fenix/issues/4343
>
> https://user:pass@[ipv6]
>
> works. Not sure about adding a path, but maybe try:
>
> https://u@[ipv6]
>
> and see if that works? Then try paths on the end.

There was/is Firefox for Android. Then came Firefox Focus, a stripped
down version. Fenix was supposed to replace Firefox for Android. Has
Fenix yet been released? I only remember the app that I downloaded onto
my Android phone was called Firefox, so it probably was Firefox for
Android.

https://github.com/mozilla-mobile/fenix/releases

How do users know which edition of "Firefox" they have on their Android
phones? It's not like they can go to play.google.com to find Fenix from
Mozilla that replaces Firefox for Android.

https://play.google.com/store/search?q=fenix&c=apps

The only Firefox you find there is "Firefox Fast & Private Browser"
which is not the product name, but their marketing folks are stupid,
plus Fenix is used in naming other apps and products (i.e., Fenix is not
a unique name).

https://play.google.com/store/apps/details?id=org.mozilla.firefox

My guess is Carlos has Firefox [[for] Android], not Fenix. I wasn't
aware Fenix was yet released.

VanguardLH wrote:

> There was/is Firefox for Android. Then came Firefox Focus, a stripped
> down version. Fenix was supposed to replace Firefox for Android. Has
> Fenix yet been released?

3 years ago, the release version only allows curated add-ons

Andy Burns <usenet@andyburns.uk> wrote:

> VanguardLH wrote:
>
>> There was/is Firefox for Android. Then came Firefox Focus, a stripped
>> down version. Fenix was supposed to replace Firefox for Android. Has
>> Fenix yet been released?
>
> 3 years ago, the release version only allows curated add-ons

Where do you find it? It's not at the Google Play Store for Android
apps. Also, 3 years ago it was not yet publicly released. So, is Fenix
actually a released or GA (General Availability) product, or is it still
in alpha or beta status? That it can be got doesn't mandate it is
released.

VanguardLH wrote:

> Andy Burns wrote:
>
>> VanguardLH wrote:
>>
>>> There was/is Firefox for Android. Then came Firefox Focus, a stripped
>>> down version. Fenix was supposed to replace Firefox for Android. Has
>>> Fenix yet been released?
>>
>> 3 years ago, the release version only allows curated add-ons
>
> Where do you find it? It's not at the Google Play Store for Android
> apps.

They swapped the "firefox" name from the fennec app to the fenix app.

> Also, 3 years ago it was not yet publicly released. So, is Fenix
> actually a released or GA (General Availability) product, or is it still
> in alpha or beta status? That it can be got doesn't mandate it is
> released.

For a while you could keep the fennec version, but eventually they
killed the previous non-fenix app, and pushed all users over.

I think other app-stores still offer fennec builds?

VanguardLH wrote:

>>> Fenix was supposed to replace Firefox for Android.
>
> Where do you find it? It's not at the Google Play Store for Android
> apps.

It is, they don't name it 'Fenix', it's just 'Firefox'

<https://play.google.com/store/apps/details?id=org.mozilla.firefox>

On 2023-04-22 20:49, VanguardLH wrote:
> Andy Burns <usenet@andyburns.uk> wrote:
>
>> VanguardLH wrote:

....

> NOTE: Looks like I still had the old Firefox Android (pre-Fenix).
> I uninstalled Firefox on my Android phone. Then installed it anew. The
> GUI is very different. Looks like I never got automatically updated to
> Fenix, and was kept on the old Firefox for Android. So, not sure which
> Firefox the OP has.

112.1.0 (Build #2015944787), 5085a19802+
GV: 112.0.1-20230414125621
AS: 97.2.0

2023-04-14T18:23:29.076587

--
Cheers, Carlos.