On 8/4/23 19:26, David Wright wrote:
On Thu 03 Aug 2023 at 15:56:07 (-0700), David Christensen wrote:
On 8/2/23 19:05, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 07:01:22PM -0700, David Christensen wrote:
Interesting. Is there a Debian specification that explains the 127.0.1.1
entry?
http
On Thu 03 Aug 2023 at 15:56:07 (-0700), David Christensen wrote:
> On 8/2/23 19:05, Greg Wooledge wrote:
> > On Wed, Aug 02, 2023 at 07:01:22PM -0700, David Christensen wrote:
> > > Interesting. Is there a Debian specification that explains the 127.0.1.1
> > > entry?
> >
> > https://www.debian.or
On 8/2/23 19:05, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 07:01:22PM -0700, David Christensen wrote:
Interesting. Is there a Debian specification that explains the 127.0.1.1
entry?
https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution
I'm sure there ar
On Wed 02 Aug 2023 at 14:48:30 (-0400), gene heskett wrote:
> On 8/2/23 13:21, Greg Wooledge wrote:
> > On Wed, Aug 02, 2023 at 01:07:13PM -0400, gene heskett wrote:
> > > On 8/2/23 07:14, Greg Wooledge wrote:
> > > > On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
> > > > > * "localh
On Wed, Aug 02, 2023 at 08:05:11PM -0400, gene heskett wrote:
[...]
> show mea link to the doc that explains that please
> Cheers, Gene Heskett.
There's not "the doc", but many of them. For starters, rfc5735 [1]
tells us that the whole subnet 127.0.0.0/8 is available for
loopback purposes (I've
On Thu 03 Aug 2023 at 07:48:54 (+0800), jeremy ardley wrote:
> On 3/8/23 07:34, Greg Wooledge wrote:
> > > On Wed 02 Aug 2023 at 16:00:24 (-0400), gene heskett wrote:
> > > > On 8/2/23 15:15, Brian wrote:
> > > > > Where is the line with 127.0.1.1? Debian always provides that.
> > > > >
> > > > Tr
On Wed, Aug 02, 2023 at 07:01:22PM -0700, David Christensen wrote:
> Interesting. Is there a Debian specification that explains the 127.0.1.1
> entry?
https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution
I'm sure there are others, but this was the first one I
On 8/2/23 16:34, Greg Wooledge wrote:
On Wed 02 Aug 2023 at 16:00:24 (-0400), gene heskett wrote:
On 8/2/23 15:15, Brian wrote:
Where is the line with 127.0.1.1? Debian always provides that.
True, but I've never seen a description of what that does or what its
for.
https://www.debian.org/do
On 8/2/23 16:26, David Wright wrote:
On Wed 02 Aug 2023 at 16:00:24 (-0400), gene heskett wrote:
On 8/2/23 15:15, Brian wrote:
On Wed 02 Aug 2023 at 14:52:26 -0400, gene heskett wrote:
On 8/2/23 14:26, Brian wrote:
No - that isn't the way it works. Give what is asked for, not a censored
versi
On 8/2/23 17:02, Brian wrote:
On Wed 02 Aug 2023 at 16:00:24 -0400, gene heskett wrote:
On 8/2/23 15:15, Brian wrote:
On Wed 02 Aug 2023 at 14:52:26 -0400, gene heskett wrote:
On 8/2/23 14:26, Brian wrote:
No - that isn't the way it works. Give what is asked for, not a censored
version that
On 8/2/23 17:02, Brian wrote:
On Wed 02 Aug 2023 at 16:00:24 -0400, gene heskett wrote:
On 8/2/23 15:15, Brian wrote:
On Wed 02 Aug 2023 at 14:52:26 -0400, gene heskett wrote:
On 8/2/23 14:26, Brian wrote:
No - that isn't the way it works. Give what is asked for, not a censored
version that
On 3/8/23 07:34, Greg Wooledge wrote:
On Wed 02 Aug 2023 at 16:00:24 (-0400), gene heskett wrote:
On 8/2/23 15:15, Brian wrote:
Where is the line with 127.0.1.1? Debian always provides that.
True, but I've never seen a description of what that does or what its
for.
https://www.debian.org/d
> On Wed 02 Aug 2023 at 16:00:24 (-0400), gene heskett wrote:
> > On 8/2/23 15:15, Brian wrote:
> > > Where is the line with 127.0.1.1? Debian always provides that.
> > >
> > True, but I've never seen a description of what that does or what its
> > for.
https://www.debian.org/doc/manuals/debian-r
On Wed 02 Aug 2023 at 16:00:24 (-0400), gene heskett wrote:
> On 8/2/23 15:15, Brian wrote:
> > On Wed 02 Aug 2023 at 14:52:26 -0400, gene heskett wrote:
> > > On 8/2/23 14:26, Brian wrote:
> > > > No - that isn't the way it works. Give what is asked for, not a censored
> > > > version that suits y
On 8/2/23 15:17, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 08:14:41PM +0100, Brian wrote:
Where is the line with 127.0.1.1? Debian always provides that.
Either deleted, or not provided by Armbian in the first place. In any
case, it's not immediately relevant to this thread's issue, so long
On 8/2/23 15:15, Brian wrote:
On Wed 02 Aug 2023 at 14:52:26 -0400, gene heskett wrote:
On 8/2/23 14:26, Brian wrote:
No - that isn't the way it works. Give what is asked for, not a censored
version that suits you.
ok, same cat in full:
gene@bpi52:~$ cat /etc/hosts
127.0.0.1 localhost
On 8/2/23, Brian wrote:
> On Wed 02 Aug 2023 at 14:52:26 -0400, gene heskett wrote:
>
>> On 8/2/23 14:26, Brian wrote:
>> > No - that isn't the way it works. Give what is asked for, not a
>> > censored
>> > version that suits you.
>> >
>> ok, same cat in full:
>> gene@bpi52:~$ cat /etc/hosts
>> 127
On Wed, Aug 02, 2023 at 08:14:41PM +0100, Brian wrote:
> Where is the line with 127.0.1.1? Debian always provides that.
Either deleted, or not provided by Armbian in the first place. In any
case, it's not immediately relevant to this thread's issue, so long as
the web service doesn't redirect to
Gene,
On Wed, Aug 02, 2023 at 02:05:48PM -0400, gene heskett wrote:
> this is a blatent attack by chrome
You've absolutely no evidence to suggest that, and other people
have already pointed out they are unable to replicate your issues.
Like almost every thread you start or derail here this is
ove
On 8/2/23 14:26, Brian wrote:
On Wed 02 Aug 2023 at 13:07:13 -0400, gene heskett wrote:
On 8/2/23 07:14, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
* "localhost:80" - This is ambiguous
[...]
It would be nice if we had an exact recipe for how to repr
On 8/2/23 13:21, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 01:07:13PM -0400, gene heskett wrote:
On 8/2/23 07:14, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
* "localhost:80" - This is ambiguous
[...]
It would be nice if we had an exact recipe for
On 8/2/23 09:42, Stefan Monnier wrote:
It would be nice if we had an exact recipe for how to reproduce the
problem. Failing that, it'll be up to Gene to debug the situation on
his end. I'm still leaning toward an edited /etc/hosts file.
My guess is that his Chrome runs in a kind of container
On Wed, Aug 02, 2023 at 01:07:13PM -0400, gene heskett wrote:
> On 8/2/23 07:14, Greg Wooledge wrote:
> > On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
> > > * "localhost:80" - This is ambiguous
> > >
> [...]
> >
> > It would be nice if we had an exact recipe for how to reproduce
On 8/2/23 07:14, Greg Wooledge wrote:
On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
* "localhost:80" - This is ambiguous
[...]
It would be nice if we had an exact recipe for how to reproduce the
problem. Failing that, it'll be up to Gene to debug the situation on
his end. I
> It would be nice if we had an exact recipe for how to reproduce the
> problem. Failing that, it'll be up to Gene to debug the situation on
> his end. I'm still leaning toward an edited /etc/hosts file.
My guess is that his Chrome runs in a kind of container that doesn't
have access to the host
On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
> * "localhost:80" - This is ambiguous
>
> In the case of the latter, are you wanting to use the localhost scheme to
> access the resource called 80 (now, you're going to say "There is no
> protocol called localhost" and I think that Ch
On 01/08/2023 10:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a browser
to run klipper as a google search intercepts port 80, so localhost:80
cannot be used for troubleshooting or for running a 3d printer with
klipper..
I think this comes down to an amb
On Tuesday 01 August 2023 05:33:55 am gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a browser
> to run klipper as a google search intercepts port 80, so localhost:80
> cannot be used for troubleshooting or for running a 3d printer with
> klipper..
>
> FF has
On 1/8/23 20:54, gene heskett wrote:
On 8/1/23 06:26, Bret Busby wrote:
On 1/8/23 17:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a
browser to run klipper as a google search intercepts port 80, so
localhost:80 cannot be used for troubleshooting or for ru
On 8/1/23 06:26, Bret Busby wrote:
On 1/8/23 17:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a browser
to run klipper as a google search intercepts port 80, so localhost:80
cannot be used for troubleshooting or for running a 3d printer with
klipper..
F
On Tue, Aug 01, 2023 at 08:13:50AM -0400, gene heskett wrote:
> On 8/1/23 06:16, Phil Wyett wrote:
> > On Tue, 2023-08-01 at 05:33 -0400, gene heskett wrote:
> >
> > Hi,
> >
> > Maybe direct this to the appropriate arena. Debians default browser is
> > Firefox, if there is no issue with FF means
On 8/1/23 06:16, Phil Wyett wrote:
On Tue, 2023-08-01 at 05:33 -0400, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a
browser
to run klipper as a google search intercepts port 80, so localhost:80
cannot be used for troubleshooting or for running a 3d printer wi
On Tue, Aug 01, 2023 at 05:33:55AM -0400, gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a browser to
> run klipper as a google search intercepts port 80, so localhost:80 cannot be
> used for troubleshooting or for running a 3d printer with klipper..
>
> FF has
On 1/8/23 17:33, gene heskett wrote:
Google seems to have high jacked port 80, I cannot use it as a browser
to run klipper as a google search intercepts port 80, so localhost:80
cannot be used for troubleshooting or for running a 3d printer with
klipper..
FF has no such problems.
Cheers, Gen
On Tue, 2023-08-01 at 05:33 -0400, gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a
> browser
> to run klipper as a google search intercepts port 80, so localhost:80
> cannot be used for troubleshooting or for running a 3d printer with
> klipper..
>
> FF has n
Google seems to have high jacked port 80, I cannot use it as a browser
to run klipper as a google search intercepts port 80, so localhost:80
cannot be used for troubleshooting or for running a 3d printer with
klipper..
FF has no such problems.
Cheers, Gene Heskett.
--
"There are four boxes to
36 matches
Mail list logo
