subject:"Stretch net install on EeePC \- unable to resolve mirror host address"

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-24 Thread Reco

Hi.

On Sat, Feb 24, 2018 at 06:48:13PM +0100, Roger Price wrote:
> On Sat, 24 Feb 2018, Reco wrote:
> > On Sat, Feb 24, 2018 at 03:14:26PM +0100, Roger Price wrote:
> > > rprice@kananga:~$ systemctl status NetworkManager
> > > ● NetworkManager.service - Network Manager
> > >Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
> > > vendor preset: enabled)
> > >Active: active (running) since Fri 2018-02-23 12:03:54 CET; 1 day 2h 
> > > ago
> > >  Docs: man:NetworkManager(8)
> > >  Main PID: 372 (NetworkManager)
> > > Tasks: 4 (limit: 4915)
> > >CGroup: /system.slice/NetworkManager.service
> > >├─372 /usr/sbin/NetworkManager --no-daemon
> > >└─472 /sbin/dhclient -d -q -sf 
> > > /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid
> > 
> > Assuming that's reference ISC DHCP, can you please try this for me?
> > 
> > dhclient -6 -d wlan0
> > 
> > Let it run for 10 seconds or so, terminate it with Ctrl+C. I'm
> > interested in the output. Oh, and there's no need to disable
> > NetworkManager, or kill running dhclient and wpasupplicant.
> 
> Script started on Sat 24 Feb 2018 06:38:17 PM CET
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on Socket/wlan0
> Sending on   Socket/wlan0
> Created duid "\000\001\000\001\"$_\211t\360m\002\262L".
> PRC: Soliciting for leases (INIT).
> XMT: Forming Solicit, 0 ms elapsed.
> XMT:  X-- IA_NA 6d:02:b2:4c
> XMT:  | X-- Request renew in  +3600
> XMT:  | X-- Request rebind in +5400
> XMT: Solicit on wlan0, interval 1080ms.
> XMT: Forming Solicit, 1080 ms elapsed.
> XMT:  X-- IA_NA 6d:02:b2:4c
> XMT:  | X-- Request renew in  +3600
> XMT:  | X-- Request rebind in +5400
> XMT: Solicit on wlan0, interval 2150ms.
> XMT: Forming Solicit, 3230 ms elapsed.
> XMT:  X-- IA_NA 6d:02:b2:4c
> XMT:  | X-- Request renew in  +3600
> XMT:  | X-- Request rebind in +5400
> XMT: Solicit on wlan0, interval 4280ms.
> XMT: Forming Solicit, 7520 ms elapsed.
> XMT:  X-- IA_NA 6d:02:b2:4c
> XMT:  | X-- Request renew in  +3600
> XMT:  | X-- Request rebind in +5400
> XMT: Solicit on wlan0, interval 8640ms.
> XMT: Forming Solicit, 16160 ms elapsed.
> XMT:  X-- IA_NA 6d:02:b2:4c
> XMT:  | X-- Request renew in  +3600
> XMT:  | X-- Request rebind in +5400
> XMT: Solicit on wlan0, interval 17250ms.
> ^C
> Script done on Sat 24 Feb 2018 06:38:40 PM CET
> 
> There is nothing in the router log for today.

Thanks, was worth the try. No DHCPv6 or RA was detected.
How exactly d-i was able to procure a valid IPv6 address is still a
mystery to me.

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-24 Thread Roger Price


On Sat, 24 Feb 2018, Reco wrote:

On Sat, Feb 24, 2018 at 03:14:26PM +0100, Roger Price wrote:

rprice@kananga:~$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2018-02-23 12:03:54 CET; 1 day 2h ago
 Docs: man:NetworkManager(8)
 Main PID: 372 (NetworkManager)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
   ├─372 /usr/sbin/NetworkManager --no-daemon
   └─472 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid


Assuming that's reference ISC DHCP, can you please try this for me?

dhclient -6 -d wlan0

Let it run for 10 seconds or so, terminate it with Ctrl+C. I'm
interested in the output. Oh, and there's no need to disable
NetworkManager, or kill running dhclient and wpasupplicant.


Script started on Sat 24 Feb 2018 06:38:17 PM CET
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/wlan0
Sending on   Socket/wlan0
Created duid "\000\001\000\001\"$_\211t\360m\002\262L".
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_NA 6d:02:b2:4c
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 1080ms.
XMT: Forming Solicit, 1080 ms elapsed.
XMT:  X-- IA_NA 6d:02:b2:4c
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 2150ms.
XMT: Forming Solicit, 3230 ms elapsed.
XMT:  X-- IA_NA 6d:02:b2:4c
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 4280ms.
XMT: Forming Solicit, 7520 ms elapsed.
XMT:  X-- IA_NA 6d:02:b2:4c
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 8640ms.
XMT: Forming Solicit, 16160 ms elapsed.
XMT:  X-- IA_NA 6d:02:b2:4c
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 17250ms.
^C
Script done on Sat 24 Feb 2018 06:38:40 PM CET

There is nothing in the router log for today.
Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-24 Thread Reco

Hi.

On Sat, Feb 24, 2018 at 03:14:26PM +0100, Roger Price wrote:
> On Fri, 23 Feb 2018, Reco wrote:
> 
> > > rprice@kananga:~$ ip -6 ro l
> > > fe80::/64 dev wlan0 proto kernel metric 256  pref medium
> > 
> > Now *that* actually means it should be impossible for this host to
> > connect to 2001:41d0:202:100:213:32:5:7.
> > 
> > So either we have a little wonder here, or … do you have DHCP6 client
> > installed there by chance? Installer most certainly should include one,
> > and that could explain the difference in behavior between your current
> > host and d-i.
> 
> The stretch i386 installer provides a dhcp client: /sbin/dhclient which is
> called by NetworkManager.
> 
> rprice@kananga:~$ systemctl status NetworkManager
> ● NetworkManager.service - Network Manager
>Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
> vendor preset: enabled)
>Active: active (running) since Fri 2018-02-23 12:03:54 CET; 1 day 2h ago
>  Docs: man:NetworkManager(8)
>  Main PID: 372 (NetworkManager)
> Tasks: 4 (limit: 4915)
>CGroup: /system.slice/NetworkManager.service
>├─372 /usr/sbin/NetworkManager --no-daemon
>└─472 /sbin/dhclient -d -q -sf 
> /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid

Assuming that's reference ISC DHCP, can you please try this for me?

dhclient -6 -d wlan0

Let it run for 10 seconds or so, terminate it with Ctrl+C. I'm
interested in the output. Oh, and there's no need to disable
NetworkManager, or kill running dhclient and wpasupplicant.

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-24 Thread Roger Price


On Fri, 23 Feb 2018, Reco wrote:


rprice@kananga:~$ ip -6 ro l
fe80::/64 dev wlan0 proto kernel metric 256  pref medium


Now *that* actually means it should be impossible for this host to
connect to 2001:41d0:202:100:213:32:5:7.

So either we have a little wonder here, or … do you have DHCP6 client
installed there by chance? Installer most certainly should include one,
and that could explain the difference in behavior between your current
host and d-i.


The stretch i386 installer provides a dhcp client: /sbin/dhclient which is 
called by NetworkManager.


rprice@kananga:~$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2018-02-23 12:03:54 CET; 1 day 2h ago
 Docs: man:NetworkManager(8)
 Main PID: 372 (NetworkManager)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
   ├─372 /usr/sbin/NetworkManager --no-daemon
   └─472 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid

Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-24 Thread Roger Price


On Fri, 23 Feb 2018, Reco wrote:


On the EeePC Ctl-Alt-F3 /dev/tty3:
 ~ # ip address
 3: enp0s4:  ...


rprice@kananga:~$ ip -6 ro l
fe80::/64 dev wlan0 proto kernel metric 256  pref medium


But, looking at all this once more, I see a discrepancy - "ip a" shows
Unpredictable Network Name, yet "ip ro" shows conventional "wlan0".


You are very sharp eyed!.  The change was because I introduced the kernel boot 
option net.ifnames=0


Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Reco

Hi.

You're replying to the wrong thread.
These two are similar as both are about IPv6 malfunction.
Let's not confuse thing further, and move this part of the discussion to
"Wrong URL" thread.

On Fri, Feb 23, 2018 at 09:10:23AM -0500, Stephen P. Molnar wrote:
> 
> On 02/23/2018 08:38 AM, Stephen P. Molnar wrote:
> > 
> > On 02/23/2018 07:12 AM, Reco wrote:
> > > Hi.
> > > 
> > > On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:
> > > > On Thu, 22 Feb 2018, Reco wrote:
> > > > 
> > > > > > On the EeePC Ctl-Alt-F3 /dev/tty3:
> > > > > >   ~ # ip address
> > > > > >   3: enp0s4:  ...
> > > > > > ...
> > > > > > inet 10.218.0.100 scope global enp0s4
> > > > > > inet6 fe80::22cf:30ff:fe10:43fd/64 scope link
> > > > > > 
> > > > > > The "fe" at the beginning of the IPv6 address says that
> > > > > > this is not capable
> > > > > > of working with the public IPv6 network.
> > > > > There's one crucial detail that's missing here. I agree that fe80
> > > > > designates link-local IPv6 (they don't put "scope link" there for
> > > > > nothing), but what about routing?
> > > > > I.e. I'm curious about the output of "ip -6 ro l".
> > > > rprice@kananga:~$ ip -6 ro l
> > > > fe80::/64 dev wlan0 proto kernel metric 256  pref medium
> > > Now *that* actually means it should be impossible for this host to
> > > connect to 2001:41d0:202:100:213:32:5:7.
> > > 
> > > So either we have a little wonder here, or … do you have DHCP6 client
> > > installed there by chance? Installer most certainly should include one,
> > > and that could explain the difference in behavior between your current
> > > host and d-i.
> > > 
> > > Reco
> > > 
> > > 
> > Interesting,
> > 
> > The only entry in Synaptic for DHCP was kea-dhcp6-server. Synaptic
> > installed:
> > 
> > kea-common (1.1.0-1)
> > kea-dhcp6-server (1.1.0-1)
> > liblog4cplus-1.1-9 (1.1.2-3.2)
> > 
> > Now, when I do  apt update I get:
> > 
> > root@AbNormal:/home/comp# apt update
> > Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> > Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
> > Hit:3 http://security.debian.org/debian-security stretch/updates
> > InRelease
> > Hit:4 http://debian.uchicago.edu/debian stretch Release
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > All packages are up to date.
> > 
> > Although if I do:
> > 
> > root@AbNormal:/home/comp# dpkg --add-architecture i386
> > root@AbNormal:/home/comp# spt update
> > 
> > then
> > 
> > root@AbNormal:/home/comp# apt update
> > Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> > Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
> > Hit:3 http://debian.uchicago.edu/debian stretch Release
> > Hit:4 http://security.debian.org/debian-security stretch/updates
> > InRelease
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > All packages are up to date.
> > 
> > but, gdebi happily installed acroread, which requires i386 libraries,
> > there were no warning or error messages.  Acroread works notmally.
> > 
> This is a bit later than the above message.
> 
> I added backports to /etc/apt/sources.list
> 
> # deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD Binary-1
> 20171209-12:11]/ stretch contrib main
> 
> # deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD Binary-1
> 20171209-12:11]/ stretch main contrib
> 
> deb http://debian.uchicago.edu/debian/ stretch main non-free contrib
> deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib
> 
> deb http://security.debian.org/debian-security/ stretch/updates main contrib
> non-free
> deb-src http://security.debian.org/debian-security/ stretch/updates main
> contrib non-free
> 
> # stretch-updates, previously known as 'volatile'
> deb http://debian.uchicago.edu/debian/ stretch-updates main contrib non-free
> deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib
> non-free
> 
> deb http://debian.uchicago.edu/debian/ stretch-backports main contrib
> non-free
> deb-src http://debian.uchicago.edu/debian/ stretch-backports main contrib
> non-free
> 
> the I rebooted the system and got
> 
> root@AbNormal:/home/comp# apt update
> Ign:1 http://debian.uchicago.edu/debian stretch InRelease
> Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
> Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
> Hit:4 http://debian.uchicago.edu/debian stretch Release
> Hit:6 http://security.debian.org/debian-security stretch/updates InRelease
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> All packages are up to date.
> 
> with a long pause before it finished.
> 
> Then I ran sysctl -w net.ipv6.conf.all.disable_ipv6=1 (as root) and got the
> same result from apt update, but without the pause.  Still no listing for
> i386.

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Stephen P. Molnar



On 02/23/2018 08:38 AM, Stephen P. Molnar wrote:


On 02/23/2018 07:12 AM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:

On Thu, 22 Feb 2018, Reco wrote:


On the EeePC Ctl-Alt-F3 /dev/tty3:
  ~ # ip address
  3: enp0s4:  ...
...
inet 10.218.0.100 scope global enp0s4
inet6 fe80::22cf:30ff:fe10:43fd/64 scope link

The "fe" at the beginning of the IPv6 address says that this is 
not capable

of working with the public IPv6 network.

There's one crucial detail that's missing here. I agree that fe80
designates link-local IPv6 (they don't put "scope link" there for
nothing), but what about routing?
I.e. I'm curious about the output of "ip -6 ro l".

rprice@kananga:~$ ip -6 ro l
fe80::/64 dev wlan0 proto kernel metric 256  pref medium

Now *that* actually means it should be impossible for this host to
connect to 2001:41d0:202:100:213:32:5:7.

So either we have a little wonder here, or … do you have DHCP6 client
installed there by chance? Installer most certainly should include one,
and that could explain the difference in behavior between your current
host and d-i.

Reco



Interesting,

The only entry in Synaptic for DHCP was kea-dhcp6-server. Synaptic 
installed:


kea-common (1.1.0-1)
kea-dhcp6-server (1.1.0-1)
liblog4cplus-1.1-9 (1.1.2-3.2)

Now, when I do  apt update I get:

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://security.debian.org/debian-security stretch/updates 
InRelease

Hit:4 http://debian.uchicago.edu/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

Although if I do:

root@AbNormal:/home/comp# dpkg --add-architecture i386
root@AbNormal:/home/comp# spt update

then

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Hit:4 http://security.debian.org/debian-security stretch/updates 
InRelease

Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

but, gdebi happily installed acroread, which requires i386 libraries, 
there were no warning or error messages.  Acroread works notmally.



This is a bit later than the above message.

I added backports to /etc/apt/sources.list

# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD 
Binary-1 20171209-12:11]/ stretch contrib main


# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD 
Binary-1 20171209-12:11]/ stretch main contrib


deb http://debian.uchicago.edu/debian/ stretch main non-free contrib
deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free
deb-src http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free


# stretch-updates, previously known as 'volatile'
deb http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free


deb http://debian.uchicago.edu/debian/ stretch-backports main contrib 
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-backports main 
contrib non-free


the I rebooted the system and got

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch-backports InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Hit:6 http://security.debian.org/debian-security stretch/updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

with a long pause before it finished.

Then I ran sysctl -w net.ipv6.conf.all.disable_ipv6=1 (as root) and got 
the same result from apt update, but without the pause.  Still no 
listing for i386.




--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Stephen P. Molnar



On 02/23/2018 07:12 AM, Reco wrote:

Hi.

On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:

On Thu, 22 Feb 2018, Reco wrote:


On the EeePC Ctl-Alt-F3 /dev/tty3:
  ~ # ip address
  3: enp0s4:  ...
...
inet 10.218.0.100 scope global enp0s4
inet6 fe80::22cf:30ff:fe10:43fd/64 scope link

The "fe" at the beginning of the IPv6 address says that this is not capable
of working with the public IPv6 network.

There's one crucial detail that's missing here. I agree that fe80
designates link-local IPv6 (they don't put "scope link" there for
nothing), but what about routing?
I.e. I'm curious about the output of "ip -6 ro l".

rprice@kananga:~$ ip -6 ro l
fe80::/64 dev wlan0 proto kernel metric 256  pref medium

Now *that* actually means it should be impossible for this host to
connect to 2001:41d0:202:100:213:32:5:7.

So either we have a little wonder here, or … do you have DHCP6 client
installed there by chance? Installer most certainly should include one,
and that could explain the difference in behavior between your current
host and d-i.

Reco



Interesting,

The only entry in Synaptic for DHCP was kea-dhcp6-server.  Synaptic 
installed:


kea-common (1.1.0-1)
kea-dhcp6-server (1.1.0-1)
liblog4cplus-1.1-9 (1.1.2-3.2)

Now, when I do  apt update I get:

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://security.debian.org/debian-security stretch/updates InRelease
Hit:4 http://debian.uchicago.edu/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

Although if I do:

root@AbNormal:/home/comp# dpkg --add-architecture i386
root@AbNormal:/home/comp# spt update

then

root@AbNormal:/home/comp# apt update
Ign:1 http://debian.uchicago.edu/debian stretch InRelease
Hit:2 http://debian.uchicago.edu/debian stretch-updates InRelease
Hit:3 http://debian.uchicago.edu/debian stretch Release
Hit:4 http://security.debian.org/debian-security stretch/updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

but, gdebi happily installed acroread, which requires i386 libraries, 
there were no warning or error messages.  Acroread works notmally.


--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Reco

On Fri, Feb 23, 2018 at 02:22:01PM +0100, Erwan David wrote:
> On Fri, Feb 23, 2018 at 01:12:41PM CET, Reco  said:
> > Hi.
> > 
> > On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:
> > > On Thu, 22 Feb 2018, Reco wrote:
> > > 
> > > > > On the EeePC Ctl-Alt-F3 /dev/tty3:
> > > > >  ~ # ip address
> > > > >  3: enp0s4:  ...
> > > > >...
> > > > >inet 10.218.0.100 scope global enp0s4
> > > > >inet6 fe80::22cf:30ff:fe10:43fd/64 scope link
> > > > > 
> > > > > The "fe" at the beginning of the IPv6 address says that this is not 
> > > > > capable
> > > > > of working with the public IPv6 network.
> > > > 
> > > > There's one crucial detail that's missing here. I agree that fe80
> > > > designates link-local IPv6 (they don't put "scope link" there for
> > > > nothing), but what about routing?
> > > > I.e. I'm curious about the output of "ip -6 ro l".
> > > 
> > > rprice@kananga:~$ ip -6 ro l
> > > fe80::/64 dev wlan0 proto kernel metric 256  pref medium
> > 
> > Now *that* actually means it should be impossible for this host to
> > connect to 2001:41d0:202:100:213:32:5:7.
> 
> No. In SLAAC the router often sends its linklocal address as
> gateway.

And this particular routing table does not have it.
What it does have is the usual link-local /64 route, which cannot be
used to send packets to 2001::/96.


But, looking at all this once more, I see a discrepancy - "ip a" shows
Unpredictable Network Name, yet "ip ro" shows conventional "wlan0".

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Erwan David

On Fri, Feb 23, 2018 at 01:12:41PM CET, Reco  said:
>   Hi.
> 
> On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:
> > On Thu, 22 Feb 2018, Reco wrote:
> > 
> > > > On the EeePC Ctl-Alt-F3 /dev/tty3:
> > > >  ~ # ip address
> > > >  3: enp0s4:  ...
> > > >...
> > > >inet 10.218.0.100 scope global enp0s4
> > > >inet6 fe80::22cf:30ff:fe10:43fd/64 scope link
> > > > 
> > > > The "fe" at the beginning of the IPv6 address says that this is not 
> > > > capable
> > > > of working with the public IPv6 network.
> > > 
> > > There's one crucial detail that's missing here. I agree that fe80
> > > designates link-local IPv6 (they don't put "scope link" there for
> > > nothing), but what about routing?
> > > I.e. I'm curious about the output of "ip -6 ro l".
> > 
> > rprice@kananga:~$ ip -6 ro l
> > fe80::/64 dev wlan0 proto kernel metric 256  pref medium
> 
> Now *that* actually means it should be impossible for this host to
> connect to 2001:41d0:202:100:213:32:5:7.

No. In SLAAC the router often sends its linklocal address as
gateway. The IP address of the gateway has only one use : to get it's
mac address (same in IPv4 or IPv6), thus link local is OK.


-- 
Erwan

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Reco

Hi.

On Fri, Feb 23, 2018 at 12:22:26PM +0100, Roger Price wrote:
> On Thu, 22 Feb 2018, Reco wrote:
> 
> > > On the EeePC Ctl-Alt-F3 /dev/tty3:
> > >  ~ # ip address
> > >  3: enp0s4:  ...
> > >...
> > >inet 10.218.0.100 scope global enp0s4
> > >inet6 fe80::22cf:30ff:fe10:43fd/64 scope link
> > > 
> > > The "fe" at the beginning of the IPv6 address says that this is not 
> > > capable
> > > of working with the public IPv6 network.
> > 
> > There's one crucial detail that's missing here. I agree that fe80
> > designates link-local IPv6 (they don't put "scope link" there for
> > nothing), but what about routing?
> > I.e. I'm curious about the output of "ip -6 ro l".
> 
> rprice@kananga:~$ ip -6 ro l
> fe80::/64 dev wlan0 proto kernel metric 256  pref medium

Now *that* actually means it should be impossible for this host to
connect to 2001:41d0:202:100:213:32:5:7.

So either we have a little wonder here, or … do you have DHCP6 client
installed there by chance? Installer most certainly should include one,
and that could explain the difference in behavior between your current
host and d-i.

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-23 Thread Roger Price


On Thu, 22 Feb 2018, Reco wrote:


On the EeePC Ctl-Alt-F3 /dev/tty3:
 ~ # ip address
 3: enp0s4:  ...
   ...
   inet 10.218.0.100 scope global enp0s4
   inet6 fe80::22cf:30ff:fe10:43fd/64 scope link

The "fe" at the beginning of the IPv6 address says that this is not capable
of working with the public IPv6 network.


There's one crucial detail that's missing here. I agree that fe80
designates link-local IPv6 (they don't put "scope link" there for
nothing), but what about routing?
I.e. I'm curious about the output of "ip -6 ro l".


rprice@kananga:~$ ip -6 ro l
fe80::/64 dev wlan0 proto kernel metric 256  pref medium

Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-22 Thread Reco

Hi.

On Thu, Feb 22, 2018 at 10:11:24AM +0100, Roger Price wrote:
> On Tue, 20 Feb 2018, Reco wrote:
> > On Tue, Feb 20, 2018 at 12:23:06PM +0100, Roger Price wrote:
> > > Later the installation hangs with the message:
> > > 
> > >  in-target: Failed to fetch
> > >  
> > > http://debian.mirrors.ovh.net/debian/dists/stretch/main/i18n/Translation-en
> > >  Cannot initiate the connection to debian.mirrors.ovh.net:80
> > >  (2001:41d0:202:100:213:32:5:7). - connect (101: Network is unreachable)
> > >  [IP 2001:41d0:202:100:213:32:5:7 80]
> > > 
> > > There is no mention of IPv4 and I do not have IPv6.
> > 
> > Of course you have IPv6, probably in the form of SLAAC/RA. How else
> > Linux kernel used in the installer would know which IPv6 address to use
> > and which IPv6 route to choose to 2001:41d0:202:100:213:32:5:7.
> 
> I have a TP-Link TL-WR1043ND v3 router sold as IPv6 capable. I selected
> SLAAC and the following was reported in the system log:
> 
>  Feb 19 23:41:47  IPv6 NOTICE  getSlaacParameters 477 sscanf address and 
> prefix error
>  Feb 19 23:43:32  IPv6 INFOIPv6 is not enabled.

Curious, but wonders cannot happen by themself.


> IPv6 management in the router has hung and I cannot select an alternative to
> SLAAC.

Thank you, added that particular model to my 'Do Not Buy Ever' list.


> On the EeePC Ctl-Alt-F3 /dev/tty3:
>  ~ # ip address
>  3: enp0s4:  ...
>...
>inet 10.218.0.100 scope global enp0s4
>inet6 fe80::22cf:30ff:fe10:43fd/64 scope link
> 
> The "fe" at the beginning of the IPv6 address says that this is not capable
> of working with the public IPv6 network.

There's one crucial detail that's missing here. I agree that fe80
designates link-local IPv6 (they don't put "scope link" there for
nothing), but what about routing?
I.e. I'm curious about the output of "ip -6 ro l".

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-22 Thread Roger Price


On Tue, 20 Feb 2018, Reco wrote:

On Tue, Feb 20, 2018 at 12:23:06PM +0100, Roger Price wrote:

Later the installation hangs with the message:

 in-target: Failed to fetch
 http://debian.mirrors.ovh.net/debian/dists/stretch/main/i18n/Translation-en
 Cannot initiate the connection to debian.mirrors.ovh.net:80
 (2001:41d0:202:100:213:32:5:7). - connect (101: Network is unreachable)
 [IP 2001:41d0:202:100:213:32:5:7 80]

There is no mention of IPv4 and I do not have IPv6.


Of course you have IPv6, probably in the form of SLAAC/RA. How else
Linux kernel used in the installer would know which IPv6 address to use
and which IPv6 route to choose to 2001:41d0:202:100:213:32:5:7.


I have a TP-Link TL-WR1043ND v3 router sold as IPv6 capable. I selected SLAAC 
and the following was reported in the system log:


 Feb 19 23:41:47  IPv6 NOTICE  getSlaacParameters 477 sscanf address and prefix 
error
 Feb 19 23:43:32  IPv6 INFOIPv6 is not enabled.

IPv6 management in the router has hung and I cannot select an alternative to 
SLAAC.


On the EeePC Ctl-Alt-F3 /dev/tty3:
 ~ # ip address
 3: enp0s4:  ...
   ...
   inet 10.218.0.100 scope global enp0s4
   inet6 fe80::22cf:30ff:fe10:43fd/64 scope link

The "fe" at the beginning of the IPv6 address says that this is not capable of 
working with the public IPv6 network.


On Tue, 20 Feb 2018, Brian wrote:

On Tue 20 Feb 2018 at 13:39:25 +, Curt wrote:

On 2018-02-20, Reco  wrote:


https://www.debian.org/releases/stable/i386/ch05s03.html.en

So I guess the 'netcfg/disable_autoconfig=true' as boot parameter would
allow for manual configuration of the network within the installer, thus
obviating the IPv6 conundrum.


I do not understand the netcfg/disable... notation.  It is not described in the 
debconf man page, neither in Joey Hess' tutorial at 
http://www.fifi.org/doc/debconf-doc/tutorial.html . In any case, the graphical 
installer asks the question.



Yet what installer *does* have that's /proc.

So, wait for the network autoconfiguration, switch to root vt, invoke:

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6


This fixed my problem.  I tried again to install, and set disable_ipv6 to 1 
before starting the step "Install the base system".  The installation of 
stretch/Xfce i386 was successful!  After booting, I set 
GRUB_CMDLINE_LINUX="ipv6.disable=1 net.ifnames=0" in /etc/default/grub and ran 
update-grub. (Maybe the net.ifnames=0 is not essential.) I also installed 
rt2860.bin needed for the WiFi.  I recovered the /home partition from an earlier 
installation of openSUSE 12.2, re-booted and I now have my EeePC running with 
stretch.  Thanks to all who commented in this thread.


I will not mark the subject [SOLVED] since the underlying problem of why wget 
fails with 12 mirrors out of 13 is not solved.


Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-20 Thread Brian

On Tue 20 Feb 2018 at 13:39:25 +, Curt wrote:

> On 2018-02-20, Reco  wrote:
> >
> >> Is there some way
> >> of telling the installer not to use IPv6?  I have read
> >> https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6 but the
> >> installer does not have file /etc/sysctl.conf
> 
> I looked up the router (I've now lost the page and the router
> references--but it did mention "supported protocols IPv4 + IPv6" as
> indicated below).
> 
> At any rate: 
> 
>  if you have an IPv6 router or a DHCP server on your local network, but
>  want to avoid them because e.g. they give wrong answers, you can use
>  the parameter netcfg/disable_autoconfig=true to prevent any automatic
>  configuration of the network (neither v4 nor v6) and to enter the
>  information manually.
> 
> https://www.debian.org/releases/stable/i386/ch05s03.html.en
> 
> So I guess the 'netcfg/disable_autoconfig=true' as boot parameter would
> allow for manual configuration of the network within the installer, thus
> obviating the IPv6 conundrum.
> 
> > Yet what installer *does* have that's /proc.
> > So, wait for the network autoconfiguration, switch to root vt, invoke:
> >
> > echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
> 
> Maybe this would be less trouble.

The OP's wget command could be tested immediately after the network is
set up and IPv6 is disabled using either yours or Reco's method.

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-20 Thread Curt

On 2018-02-20, Reco  wrote:
>
>> Is there some way
>> of telling the installer not to use IPv6?  I have read
>> https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6 but the
>> installer does not have file /etc/sysctl.conf

I looked up the router (I've now lost the page and the router
references--but it did mention "supported protocols IPv4 + IPv6" as
indicated below).

At any rate: 

 if you have an IPv6 router or a DHCP server on your local network, but
 want to avoid them because e.g. they give wrong answers, you can use
 the parameter netcfg/disable_autoconfig=true to prevent any automatic
 configuration of the network (neither v4 nor v6) and to enter the
 information manually.

https://www.debian.org/releases/stable/i386/ch05s03.html.en

So I guess the 'netcfg/disable_autoconfig=true' as boot parameter would
allow for manual configuration of the network within the installer, thus
obviating the IPv6 conundrum.

> Yet what installer *does* have that's /proc.
> So, wait for the network autoconfiguration, switch to root vt, invoke:
>
> echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6

Maybe this would be less trouble.

> And you just disabled IPv6 until the next reboot.
>
> Reco

-- 
New York was no mere city. It was instead an infinitely romantic notion, the
mysterious nexus of all love and money and power, the shining and the
perishable dream itself. To think of 'living' there was to reduce the
miraculous to the mundane; one does not 'live' at Xanadu. --Joan Didion

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-20 Thread Reco

Hi.

On Tue, Feb 20, 2018 at 12:23:06PM +0100, Roger Price wrote:
> Later the installation hangs with the message:
> 
>  in-target: Failed to fetch
>  http://debian.mirrors.ovh.net/debian/dists/stretch/main/i18n/Translation-en
>  Cannot initiate the connection to debian.mirrors.ovh.net:80
>  (2001:41d0:202:100:213:32:5:7). - connect (101: Network is unreachable)
>  [IP 2001:41d0:202:100:213:32:5:7 80]
> 
> There is no mention of IPv4 and I do not have IPv6. 

Of course you have IPv6, probably in the form of SLAAC/RA. How else
Linux kernel used in the installer would know which IPv6 address to use
and which IPv6 route to choose to 2001:41d0:202:100:213:32:5:7.

> Is there some way
> of telling the installer not to use IPv6?  I have read
> https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6 but the
> installer does not have file /etc/sysctl.conf

Yet what installer *does* have that's /proc.
So, wait for the network autoconfiguration, switch to root vt, invoke:

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6

And you just disabled IPv6 until the next reboot.

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-20 Thread Roger Price


Thanks again for your suggestions.

On Sun, 18 Feb 2018, Gene Heskett wrote:


Is the machine fully uptodate?


The netinst CD is freshly downloaded and identifies as << Debian
GNU/Linux 9.3.0 "Stretch" - Official i386 NETINST 20171209-13:03 >>.  Is
there a newer CD?

On Sun, 18 Feb 2018, Brian wrote:


On Sun 18 Feb 2018 at 23:19:48 +0100, Roger Price wrote:

  3. Load installer components from CD
 [X] choose-mirror


Why? I've never used it. I don't know what it does. It's optional. Don't
select it.



Try a different mirror. With and without step 3.


On Sun, 18 Feb 2018, David Wright wrote:


 And as Brian said, forget this option:

   Installer components to load:
   [ ] choose-mirror: Choose mirror to install from (menu item)

Work your way through the main menu …

...

… and don't think about mirrors until you get to this point.
 │  Select and install software


I naïvely choose that component because I assumed it provided the "choose a 
mirror" function.  If that is not true, then the option needs to be renamed.


Choosing this component has the considerable advantage that it gets to the 
problem much more quickly without having to specify users and partition disks at 
each test.


I tried 11 other mirrors.

 ftp.fr.debian.org  ftp.ch.debian.org ftp.se.debian.org
 ftp.fi.debian.org  ftp.hk.debian.org debian.proxad.net
 ftp.uni-stuttgart.de   debian.mirror.lrz.de  mirror.ox.ac.uk
 opensource.nchc.org.tw debian.mirrors.easynet.fr

They all connect and then hang on "HTTP request sent, awaiting response...".

I tried ftp.uni-kl.de which gets as far as "200 OK" and then hangs.

I tried debian.mirrors.ovh.net which succeeds with retries.  At the step "Select 
and install software", the only option is [X] Standard system utilities. 
Nothing else.


I choose the default linux kernel, and when finally I boot the new installation, 
I get many ACPI errors and then fall into initramfs which offers me Busybox.


I tried again with debian.mirrors.ovh.net and saw on Ctl-Alt-F4

 main-menu[346]: (process:4174): unknown udeb stretch-support
 main-menu[346]: INFO: falling back to the package description for brltty-udeb

Is this a sign that something is wrong?

Later the installation hangs with the message:

 in-target: Failed to fetch
 http://debian.mirrors.ovh.net/debian/dists/stretch/main/i18n/Translation-en
 Cannot initiate the connection to debian.mirrors.ovh.net:80
 (2001:41d0:202:100:213:32:5:7). - connect (101: Network is unreachable)
 [IP 2001:41d0:202:100:213:32:5:7 80]

There is no mention of IPv4 and I do not have IPv6.  Is there some way
of telling the installer not to use IPv6?  I have read
https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6 but the
installer does not have file /etc/sysctl.conf

Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-19 Thread Brian

On Mon 19 Feb 2018 at 09:46:27 -0500, Gene Heskett wrote:

> On Monday 19 February 2018 07:44:04 Brian wrote:
> 
> > On Sun 18 Feb 2018 at 20:21:57 -0500, Gene Heskett wrote:
> > > On Sunday 18 February 2018 18:47:58 Brian wrote:
> > > > On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote:
> > > > > On Sunday 18 February 2018 17:19:48 Roger Price wrote:
> > > >
> > > > [Snipped]
> > > >
> > > > > > It looks as if the network setup in the EeePC is correct, but
> > > > > > wget fails. Any suggestion would be very welcome, Roger
> > > > >
> > > > > Check the list, I think wget was mentioned as a problem child
> > > > > child within the last 2 or 3 weeks. Is the machine fully
> > > > > uptodate?
> > > >
> > > > What significance does "fully uptodate" have when using the
> > > > installer?
> > >
> > > The install media may be dated, so if it will boot at all, the first
> > > thing should be to update it and see if wget is replaced and now
> > > works.
> >
> > Sounds reasonable until one realises the installer uses a busybox
> > version of wget. And busybox hasn't changed during the lifetime of
> > 9.x.x.
> 
> while wget (and curl) has been updated, apparently trying to fix a bug or 
> attack vector, several times in the last 6 weeks or so.
> 
> So this would appear to be a busybox problem from my point of view? Or 

I've been misleading (because I did not check /usr/bin within the
installer). Apologies. The installer actually uses wget 1.18-5+deb9u1,
not the busybox version.

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-19 Thread Reco

 Hi.

On Mon, Feb 19, 2018 at 09:46:27AM -0500, Gene Heskett wrote:
> On Monday 19 February 2018 07:44:04 Brian wrote:
> 
> > On Sun 18 Feb 2018 at 20:21:57 -0500, Gene Heskett wrote:
> > > On Sunday 18 February 2018 18:47:58 Brian wrote:
> > > > On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote:
> > > > > On Sunday 18 February 2018 17:19:48 Roger Price wrote:
> > > >
> > > > [Snipped]
> > > >
> > > > > > It looks as if the network setup in the EeePC is correct, but
> > > > > > wget fails. Any suggestion would be very welcome, Roger
> > > > >
> > > > > Check the list, I think wget was mentioned as a problem child
> > > > > child within the last 2 or 3 weeks. Is the machine fully
> > > > > uptodate?
> > > >
> > > > What significance does "fully uptodate" have when using the
> > > > installer?
> > >
> > > The install media may be dated, so if it will boot at all, the first
> > > thing should be to update it and see if wget is replaced and now
> > > works.
> >
> > Sounds reasonable until one realises the installer uses a busybox
> > version of wget. And busybox hasn't changed during the lifetime of
> > 9.x.x.
> 
> while wget (and curl) has been updated, apparently trying to fix a bug or 
> attack vector, several times in the last 6 weeks or so.
> 
> So this would appear to be a busybox problem from my point of view? Or 
> possibly a broken link as I get that same pair of errors regardless of 
> the machine on my home net that I initiate this query from:
> 
> wget -S --spider https://wiki.debian.org
> 

>   HTTP/1.1 403 FORBIDDEN

> 
> Found 1 broken link.
> 
> https://wiki.debian.org/
> 
> Converted 0 files in 0 seconds.
> 
> So either wget has been banned, or the file does not exist.

It gets better. Force wget to send GET instead of HEAD, and it works:

$ wget -O /dev/null https://wiki.debian.org
--2018-02-19 18:16:48--  https://wiki.debian.org/
Resolving wiki.debian.org (wiki.debian.org)...  
2001:41b8:202:deb:6564:a62:52c3:4b70, 82.195.75.112
Connecting to wiki.debian.org 
(wiki.debian.org)|2001:41b8:202:deb:6564:a62:52c3:4b70|:443...
connected.
HTTP request sent, awaiting response... 200 OK

Busybox's wget fails, of course as https is not implemented there:

$ busybox wget -O /dev/null https://wiki.debian.org
wget: not an http or ftp url: https://wiki.debian.org

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-19 Thread Gene Heskett

On Monday 19 February 2018 07:44:04 Brian wrote:

> On Sun 18 Feb 2018 at 20:21:57 -0500, Gene Heskett wrote:
> > On Sunday 18 February 2018 18:47:58 Brian wrote:
> > > On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote:
> > > > On Sunday 18 February 2018 17:19:48 Roger Price wrote:
> > >
> > > [Snipped]
> > >
> > > > > It looks as if the network setup in the EeePC is correct, but
> > > > > wget fails. Any suggestion would be very welcome, Roger
> > > >
> > > > Check the list, I think wget was mentioned as a problem child
> > > > child within the last 2 or 3 weeks. Is the machine fully
> > > > uptodate?
> > >
> > > What significance does "fully uptodate" have when using the
> > > installer?
> >
> > The install media may be dated, so if it will boot at all, the first
> > thing should be to update it and see if wget is replaced and now
> > works.
>
> Sounds reasonable until one realises the installer uses a busybox
> version of wget. And busybox hasn't changed during the lifetime of
> 9.x.x.

while wget (and curl) has been updated, apparently trying to fix a bug or 
attack vector, several times in the last 6 weeks or so.

So this would appear to be a busybox problem from my point of view? Or 
possibly a broken link as I get that same pair of errors regardless of 
the machine on my home net that I initiate this query from:

wget -S --spider https://wiki.debian.org

And this is the response I get from here in WV,USA:
gene@coyote:~/Documents$ wget -S --spider https://wiki.debian.org
Spider mode enabled. Check if remote file exists.
--2018-02-19 09:39:51--  https://wiki.debian.org/
Resolving wiki.debian.org (wiki.debian.org)... 82.195.75.112, 
2001:41b8:202:deb:6564:a62:52c3:4b70
Connecting to wiki.debian.org (wiki.debian.org)|82.195.75.112|:443... 
connected.
HTTP request sent, awaiting response...
  HTTP/1.1 403 FORBIDDEN
  Date: Mon, 19 Feb 2018 14:39:42 GMT
  Server: Apache
  X-Content-Type-Options: nosniff
  X-Frame-Options: sameorigin
  Referrer-Policy: no-referrer
  X-Xss-Protection: 1
  Strict-Transport-Security: max-age=15552000
  Public-Key-Pins: 
pin-sha256="yPqY/77C2aLVJIEAYtuMrFy+cX6g4CatH03gcBQbxpo="; 
pin-sha256="TzmD7DK6d5d7RU66/XTJtlENSfv+i0P7x2Xmpl8uFrY="; 
max-age=5184000
  Content-Length: 166
  X-Clacks-Overhead: GNU Terry Pratchett
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html
Remote file does not exist -- broken link!!!

Found 1 broken link.

https://wiki.debian.org/

Converted 0 files in 0 seconds.

So either wget has been banned, or the file does not exist.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-19 Thread Gene Heskett

On Sunday 18 February 2018 20:33:52 Ólafur Jens Sigurðsson wrote:

> wget -S --spider https://wiki.debian.org

rock64@rock64:~$ wget -S --spider https://wiki.debian.org
Spider mode enabled. Check if remote file exists.
--2018-02-19 14:27:45--  https://wiki.debian.org/
Resolving wiki.debian.org (wiki.debian.org)... 82.195.75.112, 
2001:41b8:202:deb:6564:a62:52c3:4b70
Connecting to wiki.debian.org (wiki.debian.org)|82.195.75.112|:443... 
connected.
HTTP request sent, awaiting response...
  HTTP/1.1 403 FORBIDDEN
  Date: Mon, 19 Feb 2018 14:27:45 GMT
  Server: Apache
  X-Content-Type-Options: nosniff
  X-Frame-Options: sameorigin
  Referrer-Policy: no-referrer
  X-Xss-Protection: 1
  Strict-Transport-Security: max-age=15552000
  Public-Key-Pins: 
pin-sha256="yPqY/77C2aLVJIEAYtuMrFy+cX6g4CatH03gcBQbxpo="; 
pin-sha256="TzmD7DK6d5d7RU66/XTJtlENSfv+i0P7x2Xmpl8uFrY="; 
max-age=5184000
  Content-Length: 166
  X-Clacks-Overhead: GNU Terry Pratchett
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html
Remote file does not exist -- broken link!!!



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-19 Thread Brian

On Sun 18 Feb 2018 at 20:21:57 -0500, Gene Heskett wrote:

> On Sunday 18 February 2018 18:47:58 Brian wrote:
> 
> > On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote:
> > > On Sunday 18 February 2018 17:19:48 Roger Price wrote:
> >
> > [Snipped]
> >
> > > > It looks as if the network setup in the EeePC is correct, but wget
> > > > fails. Any suggestion would be very welcome, Roger
> > >
> > > Check the list, I think wget was mentioned as a problem child child
> > > within the last 2 or 3 weeks. Is the machine fully uptodate?
> >
> > What significance does "fully uptodate" have when using the installer?
> 
> The install media may be dated, so if it will boot at all, the first 
> thing should be to update it and see if wget is replaced and now works.

Sounds reasonable until one realises the installer uses a busybox
version of wget. And busybox hasn't changed during the lifetime of
9.x.x.

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread David Wright

On Mon 19 Feb 2018 at 01:33:52 (+), Ólafur Jens Sigurðsson wrote:
> On Sat, Feb 17, 2018 at 06:52:43PM +, Curt wrote:
> > On 2018-02-17, Reco  wrote:
> > >
> > > First, please don't get me wrong, but can you provide the output of
> > > (regular box, of course):
> > >
> > > wget -S --spider https://wiki.debian.org
> > >
> > > There have been some reports from people using your ISP that this page
> > > does not work for them somehow, and I'm too lazy to travel to France to
> > > check it out :)
> > >
> > 
> > Here I am conveniently in France:
> > 
> > curty@einstein:~$ wget -S --spider https://wiki.debian.org
> > Spider mode enabled. Check if remote file exists.
> > --2018-02-17 19:52:06--  https://wiki.debian.org/
> > Resolving wiki.debian.org (wiki.debian.org)... 82.195.75.112, 
> > 2001:41b8:202:deb:6564:a62:52c3:4b70
> > Connecting to wiki.debian.org (wiki.debian.org)|82.195.75.112|:443... 
> > connected.
> > HTTP request sent, awaiting response... 
> >   HTTP/1.1 403 FORBIDDEN
> >   Date: Sat, 17 Feb 2018 18:52:06 GMT
> >   Server: Apache
> >   X-Content-Type-Options: nosniff
> >   X-Frame-Options: sameorigin
> >   Referrer-Policy: no-referrer
> >   X-Xss-Protection: 1
> >   Strict-Transport-Security: max-age=15552000
> >   Public-Key-Pins: 
> > pin-sha256="yPqY/77C2aLVJIEAYtuMrFy+cX6g4CatH03gcBQbxpo="; 
> > pin-sha256="TzmD7DK6d5d7RU66/XTJtlENSfv+i0P7x2Xmpl8uFrY="; max-age=5184000
> >   Content-Length: 166
> >   X-Clacks-Overhead: GNU Terry Pratchett
> >   Keep-Alive: timeout=5, max=100
> >   Connection: Keep-Alive
> >   Content-Type: text/html
> > Remote file does not exist -- broken link!!!
> > 
> > I surfed the wiki the other day, no problemo, but "HTTP/1.1 403 FORBIDDEN"?
> 
> I get the same here in Iceland, IP address is 193.109.xxx.xxx (AS Number
> is 24743) and I can browse the wiki just fine.
> 
> What do people in the US get?

Much the same as anyone else. But who cares. This subthread was
hijacked here:
https://lists.debian.org/debian-user/2018/02/msg00755.html

Forget the wiki. And as Brian said, forget this option:

Installer components to load:
[ ] choose-mirror: Choose mirror to install from (menu item)

Work your way through the main menu …

  │  Choose language
  │  Configure the keyboard
  │  Detect and mount CD-ROM
  │  Load installer components from CD
  │  Detect network hardware
  │  Configure the network
  │  Set up users and passwords
  │  Configure the clock
  │  Detect disks
  │  Partition disks
  │  Install the base system
  │  Configure the package manager

… and don't think about mirrors until you get to this point.

  │  Select and install software
  │  Install the GRUB boot loader on a hard disk
  │  Finish the installation

Cheers,
David.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread Ólafur Jens Sigurðsson

On Sat, Feb 17, 2018 at 06:52:43PM +, Curt wrote:
> On 2018-02-17, Reco  wrote:
> >
> > First, please don't get me wrong, but can you provide the output of
> > (regular box, of course):
> >
> > wget -S --spider https://wiki.debian.org
> >
> > There have been some reports from people using your ISP that this page
> > does not work for them somehow, and I'm too lazy to travel to France to
> > check it out :)
> >
> 
> Here I am conveniently in France:
> 
> curty@einstein:~$ wget -S --spider https://wiki.debian.org
> Spider mode enabled. Check if remote file exists.
> --2018-02-17 19:52:06--  https://wiki.debian.org/
> Resolving wiki.debian.org (wiki.debian.org)... 82.195.75.112, 
> 2001:41b8:202:deb:6564:a62:52c3:4b70
> Connecting to wiki.debian.org (wiki.debian.org)|82.195.75.112|:443... 
> connected.
> HTTP request sent, awaiting response... 
>   HTTP/1.1 403 FORBIDDEN
>   Date: Sat, 17 Feb 2018 18:52:06 GMT
>   Server: Apache
>   X-Content-Type-Options: nosniff
>   X-Frame-Options: sameorigin
>   Referrer-Policy: no-referrer
>   X-Xss-Protection: 1
>   Strict-Transport-Security: max-age=15552000
>   Public-Key-Pins: pin-sha256="yPqY/77C2aLVJIEAYtuMrFy+cX6g4CatH03gcBQbxpo="; 
> pin-sha256="TzmD7DK6d5d7RU66/XTJtlENSfv+i0P7x2Xmpl8uFrY="; max-age=5184000
>   Content-Length: 166
>   X-Clacks-Overhead: GNU Terry Pratchett
>   Keep-Alive: timeout=5, max=100
>   Connection: Keep-Alive
>   Content-Type: text/html
> Remote file does not exist -- broken link!!!
> 
> I surfed the wiki the other day, no problemo, but "HTTP/1.1 403 FORBIDDEN"?

I get the same here in Iceland, IP address is 193.109.xxx.xxx (AS Number
is 24743) and I can browse the wiki just fine.

What do people in the US get?

Cheers, Oli

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread Gene Heskett

On Sunday 18 February 2018 18:47:58 Brian wrote:

> On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote:
> > On Sunday 18 February 2018 17:19:48 Roger Price wrote:
>
> [Snipped]
>
> > > It looks as if the network setup in the EeePC is correct, but wget
> > > fails. Any suggestion would be very welcome, Roger
> >
> > Check the list, I think wget was mentioned as a problem child child
> > within the last 2 or 3 weeks. Is the machine fully uptodate?
>
> What significance does "fully uptodate" have when using the installer?

The install media may be dated, so if it will boot at all, the first 
thing should be to update it and see if wget is replaced and now works.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread Brian

On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote:

> On Sunday 18 February 2018 17:19:48 Roger Price wrote:

[Snipped]
 
> > It looks as if the network setup in the EeePC is correct, but wget
> > fails. Any suggestion would be very welcome, Roger
> 
> Check the list, I think wget was mentioned as a problem child child 
> within the last 2 or 3 weeks. Is the machine fully uptodate?

What significance does "fully uptodate" have when using the installer?

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread Brian

On Sun 18 Feb 2018 at 23:19:48 +0100, Roger Price wrote:

> Thanks for all your comments, I repeated my attempt to install as follows:
> 
> Hardware: EeePC1201K (AMD Athlon 1000MHz, 1Gbyte)
>  External CD/DVD reader Samsung SE-S084.
>  Router: TP-Link 450M Wireless N Gigabit Model No. TL-WR1043ND. No IPv6
> 
> "Graphical expert install"
>   1. Configure the keyboard (AZERTY)
>   2. Detect and mount CD-ROM
>   3. Load installer components from CD
>  [X] choose-mirror

Why? I've never used it. I don't know what it does. It's optional. Don't
select it.

>   4. Detect network hardware
>  Missing firmware files are: rt2680.bin Load? [X] No
>   5. Configure the network
>  enp0s4: Silicon Intergrated Systems [SiS] 190 Ethernet Adapter
>  wlp2s0: Ralink Corp: RT3090 Wireless 802.11n 1T/1R PCIe (wireless)
>   6. Choose enp0s4 as primary
>   7. Auto-configure networking? Yes
>  IPv6 + DHCP, set hostname and domain name.
>   8. Ctl-Alt-F3 to /dev/tty3
>  ~ # route
>  Kernel IP routing table
>  Destination  Gateway GenmaskFlags Metric Ref Use Iface
>  default  10.218.0.1  0.0.0.0UG0  0   0   enp0s4
>  10.218.0.0   *   255.255.255.0  U 0  0   0   enp0s4
>   9. ~ # ip address
>  ...
>  3: enp0s4:  mtu 1500 ...
> link/ether 20:cf:30:10:43:fd brd ff:...
> inet 10.218.0.100/24 scope global enp0s4
>  ...
>  10. ~ # ping -c3 debian.proxad.net
>  PING debian.proxad.net (212.27.32.66): 56 data bytes
>  64 bytes from 212.27.32.66: seq=0 ttl=57 time=38.838 ms
>  ...
>  3 packets transmitted, 3 packets received, 0% packet loss
>  11. Ctl-Alt-F5 Graphical install
>  Choose a mirror of the Debian archive
>http, debian.proxad.net
>  12. Ctl-Alt-F4
>  Last line shows EeePC hung on
>  choose-mirror[4246]: DEBUG: command: wget --no-verbose
>   http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
>   '^(Suite|Codename|Architectures):'
>  13. Ctl-Alt-F3 to /dev/tty3
>  ping ftp.fr.debian.org is successful, but
>  hangs on command wget --no-verbose
>   http://ftp.fr.debian.org/debian/dists/stretch/Release -O - | grep -E
>   '^(Suite|Codename|Architectures):'
>  14. I repeated 13 with more verbosity:
>  wget http://ftp.fr.debian.org/debian/dists/stretch/Release -O - | grep -E
>   '^(Suite|Codename|Architectures):'
>  --2018-02-18 20:50:31-- 
> http://ftp.fr.debian.org/debian/dists/stretch/Release
>  Resolving ftp.fr.debian.org... 212.27.32.66, 2a01:e0c:1:1598::2
>  Connecting to ftp.fr.debian.org|212.27.32.66|:80... Connected
>  HTTP request sent, awaiting response
>  ... 15 minutes go by ...
>  Read error (Connection timed out) in headers.
>  Retrying
> 
> It looks as if the network setup in the EeePC is correct, but wget fails.
> Any suggestion would be very welcome, Roger

Try a different mirror. With and without step 3.

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread Gene Heskett

On Sunday 18 February 2018 17:19:48 Roger Price wrote:

> On Sat, 17 Feb 2018, Gene Heskett wrote:
> >>   ~ # cat /etc/resolv.conf
> >>   search rogerprice.org
> >>   nameserver 8.8.8.8
> >
> > Does the resolv.conf still contain that data?
>
> Yes
>
> On Sat, 17 Feb 2018, Gene Heskett wrote:
> >> debian.proxad.net is 212.27.32.6. If you ping that?
> >
> > Yes, works great even from a rock64 out in the garage.
> > Do a "sudo route -n" and see if you get a valid gateway, "UG"
> > address. Then describe your hardware arrangement precisely please
>
> On Sat, 17 Feb 2018, Gene Heskett wrote:
> > On Saturday 17 February 2018 19:48:20 Rodary Jacques wrote:
> >> I had this kind of problem with free (i.e. proxad) repository which
> >> isn't any more (bust was in 2016) on the mirror list, and had to
> >> replace it with  -not a ftp
> >> server- in /etc/apt/sources.list. Salut. Jacques
> >
> > debian.proxad.net pings just fine from a stretch install on an arm64
> > machine:
> > rock64@rock64:/media/slash/home/rock64$ ping debian.proxad.net
> > PING debian.proxad.net (212.27.32.66) 56(84) bytes of data.
> > 64 bytes from debian.proxad.net (212.27.32.66): icmp_seq=1 ttl=50
> > time=107 ms
>
> ...
>
> > 4 packets transmitted, 4 received, 0% packet loss, time 3003ms
> > Something is wrong with his gateway, or dns.
>
> Thanks for all your comments, I repeated my attempt to install as
> follows:
>
> Hardware: EeePC1201K (AMD Athlon 1000MHz, 1Gbyte)
>   External CD/DVD reader Samsung SE-S084.
>   Router: TP-Link 450M Wireless N Gigabit Model No. TL-WR1043ND. No
> IPv6
>
> "Graphical expert install"
>1. Configure the keyboard (AZERTY)
>2. Detect and mount CD-ROM
>3. Load installer components from CD
>   [X] choose-mirror
>4. Detect network hardware
>   Missing firmware files are: rt2680.bin Load? [X] No
>5. Configure the network
>   enp0s4: Silicon Intergrated Systems [SiS] 190 Ethernet Adapter
>   wlp2s0: Ralink Corp: RT3090 Wireless 802.11n 1T/1R PCIe
> (wireless) 6. Choose enp0s4 as primary
>7. Auto-configure networking? Yes
>   IPv6 + DHCP, set hostname and domain name.
>8. Ctl-Alt-F3 to /dev/tty3
>   ~ # route
>   Kernel IP routing table
>   Destination  Gateway GenmaskFlags Metric Ref Use
> Iface default  10.218.0.1  0.0.0.0UG0  0   0  
> enp0s4 10.218.0.0   *   255.255.255.0  U 0  0   0  
> enp0s4 9. ~ # ip address
>   ...
>   3: enp0s4:  mtu 1500 ...
>  link/ether 20:cf:30:10:43:fd brd ff:...
>  inet 10.218.0.100/24 scope global enp0s4
>   ...
>   10. ~ # ping -c3 debian.proxad.net
>   PING debian.proxad.net (212.27.32.66): 56 data bytes
>   64 bytes from 212.27.32.66: seq=0 ttl=57 time=38.838 ms
>   ...
>   3 packets transmitted, 3 packets received, 0% packet loss
>   11. Ctl-Alt-F5 Graphical install
>   Choose a mirror of the Debian archive
> http, debian.proxad.net
>   12. Ctl-Alt-F4
>   Last line shows EeePC hung on
>   choose-mirror[4246]: DEBUG: command: wget --no-verbose
>http://debian.proxad.net/debian/dists/stretch/Release -O - |
> grep -E '^(Suite|Codename|Architectures):'
>   13. Ctl-Alt-F3 to /dev/tty3
>   ping ftp.fr.debian.org is successful, but
>   hangs on command wget --no-verbose
>http://ftp.fr.debian.org/debian/dists/stretch/Release -O - |
> grep -E '^(Suite|Codename|Architectures):'
>   14. I repeated 13 with more verbosity:
>   wget http://ftp.fr.debian.org/debian/dists/stretch/Release -O -
> | grep -E '^(Suite|Codename|Architectures):'
>   --2018-02-18 20:50:31--
> http://ftp.fr.debian.org/debian/dists/stretch/Release Resolving
> ftp.fr.debian.org... 212.27.32.66, 2a01:e0c:1:1598::2 Connecting to
> ftp.fr.debian.org|212.27.32.66|:80... Connected HTTP request sent,
> awaiting response
>   ... 15 minutes go by ...
>   Read error (Connection timed out) in headers.
>   Retrying
>
> It looks as if the network setup in the EeePC is correct, but wget
> fails. Any suggestion would be very welcome, Roger

Check the list, I think wget was mentioned as a problem child child 
within the last 2 or 3 weeks. Is the machine fully uptodate?



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-18 Thread Roger Price


On Sat, 17 Feb 2018, Gene Heskett wrote:


  ~ # cat /etc/resolv.conf
  search rogerprice.org
  nameserver 8.8.8.8

Does the resolv.conf still contain that data?


Yes

On Sat, 17 Feb 2018, Gene Heskett wrote:


debian.proxad.net is 212.27.32.6. If you ping that?

Yes, works great even from a rock64 out in the garage.
Do a "sudo route -n" and see if you get a valid gateway, "UG" address.
Then describe your hardware arrangement precisely please


On Sat, 17 Feb 2018, Gene Heskett wrote:


On Saturday 17 February 2018 19:48:20 Rodary Jacques wrote:


I had this kind of problem with free (i.e. proxad) repository which
isn't any more (bust was in 2016) on the mirror list, and had to 
replace it with  -not a ftp server-

in /etc/apt/sources.list. Salut. Jacques


debian.proxad.net pings just fine from a stretch install on an arm64
machine:
rock64@rock64:/media/slash/home/rock64$ ping debian.proxad.net
PING debian.proxad.net (212.27.32.66) 56(84) bytes of data. 
64 bytes from debian.proxad.net (212.27.32.66): icmp_seq=1 ttl=50 time=107 ms

...

4 packets transmitted, 4 received, 0% packet loss, time 3003ms
Something is wrong with his gateway, or dns.


Thanks for all your comments, I repeated my attempt to install as follows:

Hardware: EeePC1201K (AMD Athlon 1000MHz, 1Gbyte)
 External CD/DVD reader Samsung SE-S084.
 Router: TP-Link 450M Wireless N Gigabit Model No. TL-WR1043ND. No IPv6

"Graphical expert install"
  1. Configure the keyboard (AZERTY)
  2. Detect and mount CD-ROM
  3. Load installer components from CD
 [X] choose-mirror
  4. Detect network hardware
 Missing firmware files are: rt2680.bin Load? [X] No
  5. Configure the network
 enp0s4: Silicon Intergrated Systems [SiS] 190 Ethernet Adapter
 wlp2s0: Ralink Corp: RT3090 Wireless 802.11n 1T/1R PCIe (wireless)
  6. Choose enp0s4 as primary
  7. Auto-configure networking? Yes
 IPv6 + DHCP, set hostname and domain name.
  8. Ctl-Alt-F3 to /dev/tty3
 ~ # route
 Kernel IP routing table
 Destination  Gateway GenmaskFlags Metric Ref Use Iface
 default  10.218.0.1  0.0.0.0UG0  0   0   enp0s4
 10.218.0.0   *   255.255.255.0  U 0  0   0   enp0s4
  9. ~ # ip address
 ...
 3: enp0s4:  mtu 1500 ...
link/ether 20:cf:30:10:43:fd brd ff:...
inet 10.218.0.100/24 scope global enp0s4
 ...
 10. ~ # ping -c3 debian.proxad.net
 PING debian.proxad.net (212.27.32.66): 56 data bytes
 64 bytes from 212.27.32.66: seq=0 ttl=57 time=38.838 ms
 ...
 3 packets transmitted, 3 packets received, 0% packet loss
 11. Ctl-Alt-F5 Graphical install
 Choose a mirror of the Debian archive
   http, debian.proxad.net
 12. Ctl-Alt-F4
 Last line shows EeePC hung on
 choose-mirror[4246]: DEBUG: command: wget --no-verbose
  http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
  '^(Suite|Codename|Architectures):'
 13. Ctl-Alt-F3 to /dev/tty3
 ping ftp.fr.debian.org is successful, but
 hangs on command wget --no-verbose
  http://ftp.fr.debian.org/debian/dists/stretch/Release -O - | grep -E
  '^(Suite|Codename|Architectures):'
 14. I repeated 13 with more verbosity:
 wget http://ftp.fr.debian.org/debian/dists/stretch/Release -O - | grep -E
  '^(Suite|Codename|Architectures):'
 --2018-02-18 20:50:31-- 
http://ftp.fr.debian.org/debian/dists/stretch/Release
 Resolving ftp.fr.debian.org... 212.27.32.66, 2a01:e0c:1:1598::2
 Connecting to ftp.fr.debian.org|212.27.32.66|:80... Connected
 HTTP request sent, awaiting response
 ... 15 minutes go by ...
 Read error (Connection timed out) in headers.
 Retrying

It looks as if the network setup in the EeePC is correct, but wget fails.
Any suggestion would be very welcome, Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Gene Heskett

On Saturday 17 February 2018 19:48:20 Rodary Jacques wrote:

> Le samedi 17 février 2018, 16:20:06 CET Roger Price a écrit :
> > I am trying to net install stretch i386 on an EeePC using a wired
> > connection. I chose my ISP as the mirror, but the installation hangs
> > on "Configure the packet management tool (APT)" [french text reads
> > "Configurer l'outil de gestion des paquets (APT)"].
> >
> > I checked on my regular box that stretch i386 is available at
> > debian.proxad.net
> >
> >   rprice@maria ~ wget --no-verbose
> > http://debian.proxad.net/debian/dists/stretch/Release -O - |
> > grep -E '^(Suite|Codename|Architectures):'
> >   Suite: stable
> >   Codename: stretch
> >   Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel
> > ppc64el s390x
> >
> > but on the EeePC with Ctl-Alt-F3 I get
> >
> >   ~ # wget --no-verbose
> > http://debian.proxad.net/debian/dists/stretch/Release -O - |
> > grep -E '^(Suite|Codename|Architectures):'
> >   wget: unable to resolve host address 'debian.proxad.net'
> >
> > Command « ip address » shows that the EeePC has been assigned the
> > correct IP address 10.218.0.100, and /etc/resolv.conf correctly
> > points to the router as the DNS resolver:
> >
> >   ~ # cat /etc/resolv.conf
> >   search rogerprice.org
> >   nameserver 10.218.0.1
> >
> > I am using the same router and the same name server to post this
> > message. Any suggestion or hint for fixing the installation would be
> > most welcome,
> >
> > Roger
>
> I had this kind of problem with free (i.e. proxad) repository which
> isn't any more (bust was in 2016) on the mirror list, and had to
> replace it with  -not a ftp server-
> in /etc/apt/sources.list. Salut. Jacques

debian.proxad.net pings just fine from a stretch install on an arm64 
machine:
rock64@rock64:/media/slash/home/rock64$ ping debian.proxad.net
PING debian.proxad.net (212.27.32.66) 56(84) bytes of data.
64 bytes from debian.proxad.net (212.27.32.66): icmp_seq=1 ttl=50 
time=107 ms
64 bytes from debian.proxad.net (212.27.32.66): icmp_seq=2 ttl=50 
time=105 ms
64 bytes from debian.proxad.net (212.27.32.66): icmp_seq=3 ttl=50 
time=105 ms
64 bytes from debian.proxad.net (212.27.32.66): icmp_seq=4 ttl=50 
time=107 ms
^C
--- debian.proxad.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 105.046/106.442/107.576/1.100 ms

Something is wrong with his gateway, or dns.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Gene Heskett

On Saturday 17 February 2018 18:35:10 Brian wrote:

> On Sat 17 Feb 2018 at 18:27:57 -0500, Gene Heskett wrote:
> > On Saturday 17 February 2018 18:13:33 Brian wrote:
> > > On Sat 17 Feb 2018 at 22:21:49 +0100, Roger Price wrote:
> > > > On Sat, 17 Feb 2018, Brian wrote:
> > > > > >  ~ # cat /etc/resolv.conf
> > > > > >  search rogerprice.org
> > > > > >  nameserver 10.218.0.1
> > > > > >
> > > > > > I am using the same router and the same name server to post
> > > > > > this message.
> > > > >
> > > > > I would try pinging www.debian.org and anywhere else you can
> > > > > think of. Or edit resolv.conf to have 8.8.8.8 (a Google
> > > > > nameserver).
> > > >
> > > > I edited /etc/resolv.conf but no success:
> > > >
> > > >  ~ # cat /etc/resolv.conf
> > > >  search rogerprice.org
> > > >  nameserver 8.8.8.8
> > > >  ~ # ping -c3 debian.proxad.net
> > > >  ping: bad address 'debian.proxad.net'
> > >
> > > debian.proxad.net is 212.27.32.6. If you ping that?
> >
> > Yes, works great even from a rock64 out in the garage.
> > Do a "sudo route -n" and see if you get a valid gateway, "UG"
> > address. Then describe your hardware arrangement precisely please
>
> sudo isn't installed within the installer environment,

Is route then within the users $PATH? It is not on that particular 
stretch machine, so I either have to know the full path, or use sudo to 
execute it.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Rodary Jacques

Le samedi 17 février 2018, 16:20:06 CET Roger Price a écrit :
> I am trying to net install stretch i386 on an EeePC using a wired connection. 
> I 
> chose my ISP as the mirror, but the installation hangs on "Configure the 
> packet 
> management tool (APT)" [french text reads "Configurer l'outil de gestion des 
> paquets (APT)"].
> 
> I checked on my regular box that stretch i386 is available at 
> debian.proxad.net
> 
>   rprice@maria ~ wget --no-verbose
> http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
> '^(Suite|Codename|Architectures):'
>   Suite: stable
>   Codename: stretch
>   Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
> s390x
> 
> but on the EeePC with Ctl-Alt-F3 I get
> 
>   ~ # wget --no-verbose
> http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
> '^(Suite|Codename|Architectures):'
>   wget: unable to resolve host address 'debian.proxad.net'
> 
> Command « ip address » shows that the EeePC has been assigned the correct IP 
> address 10.218.0.100, and /etc/resolv.conf correctly points to the router as 
> the 
> DNS resolver:
> 
>   ~ # cat /etc/resolv.conf
>   search rogerprice.org
>   nameserver 10.218.0.1
> 
> I am using the same router and the same name server to post this message. Any 
> suggestion or hint for fixing the installation would be most welcome,
>
> Roger
I had this kind of problem with free (i.e. proxad) repository which isn't any 
more (bust was in 2016) on the mirror list, 
and had to replace it with  -not a ftp 
server- in /etc/apt/sources.list.
Salut. Jacques

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Brian

On Sat 17 Feb 2018 at 18:27:57 -0500, Gene Heskett wrote:

> On Saturday 17 February 2018 18:13:33 Brian wrote:
> 
> > On Sat 17 Feb 2018 at 22:21:49 +0100, Roger Price wrote:
> > > On Sat, 17 Feb 2018, Brian wrote:
> > > > >  ~ # cat /etc/resolv.conf
> > > > >  search rogerprice.org
> > > > >  nameserver 10.218.0.1
> > > > >
> > > > > I am using the same router and the same name server to post this
> > > > > message.
> > > >
> > > > I would try pinging www.debian.org and anywhere else you can think
> > > > of. Or edit resolv.conf to have 8.8.8.8 (a Google nameserver).
> > >
> > > I edited /etc/resolv.conf but no success:
> > >
> > >  ~ # cat /etc/resolv.conf
> > >  search rogerprice.org
> > >  nameserver 8.8.8.8
> > >  ~ # ping -c3 debian.proxad.net
> > >  ping: bad address 'debian.proxad.net'
> >
> > debian.proxad.net is 212.27.32.6. If you ping that?
> 
> Yes, works great even from a rock64 out in the garage.
> Do a "sudo route -n" and see if you get a valid gateway, "UG" address.
> Then describe your hardware arrangement precisely please

sudo isn't installed within the installer environment,

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Gene Heskett

On Saturday 17 February 2018 18:13:33 Brian wrote:

> On Sat 17 Feb 2018 at 22:21:49 +0100, Roger Price wrote:
> > On Sat, 17 Feb 2018, Brian wrote:
> > > >  ~ # cat /etc/resolv.conf
> > > >  search rogerprice.org
> > > >  nameserver 10.218.0.1
> > > >
> > > > I am using the same router and the same name server to post this
> > > > message.
> > >
> > > I would try pinging www.debian.org and anywhere else you can think
> > > of. Or edit resolv.conf to have 8.8.8.8 (a Google nameserver).
> >
> > I edited /etc/resolv.conf but no success:
> >
> >  ~ # cat /etc/resolv.conf
> >  search rogerprice.org
> >  nameserver 8.8.8.8
> >  ~ # ping -c3 debian.proxad.net
> >  ping: bad address 'debian.proxad.net'
>
> debian.proxad.net is 212.27.32.6. If you ping that?

Yes, works great even from a rock64 out in the garage.
Do a "sudo route -n" and see if you get a valid gateway, "UG" address.
Then describe your hardware arrangement precisely please



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Brian

On Sat 17 Feb 2018 at 22:21:49 +0100, Roger Price wrote:

> On Sat, 17 Feb 2018, Brian wrote:
> 
> > >  ~ # cat /etc/resolv.conf
> > >  search rogerprice.org
> > >  nameserver 10.218.0.1
> > > 
> > > I am using the same router and the same name server to post this message.
> > 
> > I would try pinging www.debian.org and anywhere else you can think of.
> > Or edit resolv.conf to have 8.8.8.8 (a Google nameserver).
> 
> I edited /etc/resolv.conf but no success:
> 
>  ~ # cat /etc/resolv.conf
>  search rogerprice.org
>  nameserver 8.8.8.8
>  ~ # ping -c3 debian.proxad.net
>  ping: bad address 'debian.proxad.net'

debian.proxad.net is 212.27.32.6. If you ping that?

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Gene Heskett

On Saturday 17 February 2018 16:21:49 Roger Price wrote:

> On Sat, 17 Feb 2018, Brian wrote:
> >>  ~ # cat /etc/resolv.conf
> >>  search rogerprice.org
> >>  nameserver 10.218.0.1
> >>
> >> I am using the same router and the same name server to post this
> >> message.
> >
> > I would try pinging www.debian.org and anywhere else you can think
> > of. Or edit resolv.conf to have 8.8.8.8 (a Google nameserver).
>
> I edited /etc/resolv.conf but no success:
>
>   ~ # cat /etc/resolv.conf
>   search rogerprice.org
>   nameserver 8.8.8.8
>   ~ # ping -c3 debian.proxad.net
>   ping: bad address 'debian.proxad.net'
>
> Roger
Does the resolv.conf still contain that data?



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Roger Price


On Sat, 17 Feb 2018, Brian wrote:


 ~ # cat /etc/resolv.conf
 search rogerprice.org
 nameserver 10.218.0.1

I am using the same router and the same name server to post this message.


I would try pinging www.debian.org and anywhere else you can think of.
Or edit resolv.conf to have 8.8.8.8 (a Google nameserver).


I edited /etc/resolv.conf but no success:

 ~ # cat /etc/resolv.conf
 search rogerprice.org
 nameserver 8.8.8.8
 ~ # ping -c3 debian.proxad.net
 ping: bad address 'debian.proxad.net'

Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Roger Price


On Sat, 17 Feb 2018, Curt wrote:


On 2018-02-17, Reco  wrote:


First, please don't get me wrong, but can you provide the output of
(regular box, of course):
wget -S --spider https://wiki.debian.org
There have been some reports from people using your ISP that this page
does not work for them somehow, and I'm too lazy to travel to France to
check it out :)


Here I am conveniently in France:

curty@einstein:~$ wget -S --spider https://wiki.debian.org
...
 HTTP/1.1 403 FORBIDDEN
...


As a subscriber to the french ISP Free, I get that same output for wget, however 
I can read the page successfully with the four browsers lynx, w3m, opera and 
firefox, and command « nmap -A wiki.debian.org » reports


 Starting Nmap 7.40 ( https://nmap.org ) at 2018-02-17 21:30 CET
 Nmap scan report for wiki.debian.org (82.195.75.112)
 Host is up (0.056s latency).
 Other addresses for wiki.debian.org (not scanned):
 2001:41b8:202:deb:6564:a62:52c3:4b70
 rDNS record for 82.195.75.112: wilder.debian.org
 Not shown: 989 closed ports
 PORT STATESERVICE  VERSION
 22/tcp   open ssh  OpenSSH 7.4p1 Debian 10+deb9u2 (protocol 2.0)
 | ssh-hostkey:
 |_  2048 7a:d8:5c:e4:e5:38:6b:6b:d0:5c:c2:87:8e:d6:05:b3 (RSA)
 80/tcp   open http Apache httpd
 |_http-server-header: Apache
 |_http-title: Did not follow redirect to https://wiki.debian.org/
 135/tcp  filtered msrpc
 139/tcp  filtered netbios-ssn
 443/tcp  open ssl/http Apache httpd
 | http-robots.txt: 1 disallowed entry
 |_/action/
 |_http-server-header: Apache
 |_http-title: FrontPage - Debian Wiki
 | ssl-cert: Subject: commonName=wiki.debian.org
 | Subject Alternative Name: DNS:wiki.debian.org
 | Not valid before: 2017-12-28T00:22:24
 |_Not valid after:  2018-03-28T00:22:24
 |_ssl-date: TLS randomness does not represent time
 445/tcp  filtered microsoft-ds
 873/tcp  open rsync(protocol version 31)
 1026/tcp filtered LSA-or-nterm
 1027/tcp filtered IIS
 1433/tcp filtered ms-sql-s
 1723/tcp filtered pptp

Perhaps wget is getting special treatment.

Roger

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Andy Smith

Hello,

On Sat, Feb 17, 2018 at 10:34:10PM +0300, Reco wrote:
> Weird, isn't it? Someone responsible to wiki.debian.org blocked the
> whole 78.192.0.0/10 subnet (AS12322), so it seems.

In  it
was suggested to report such things to w...@debian.org.

Cheers,
Andy

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Reco

Hi.

On Sat, Feb 17, 2018 at 06:52:43PM +, Curt wrote:
> On 2018-02-17, Reco  wrote:
> >
> > First, please don't get me wrong, but can you provide the output of
> > (regular box, of course):
> >
> > wget -S --spider https://wiki.debian.org
> >
> > There have been some reports from people using your ISP that this page
> > does not work for them somehow, and I'm too lazy to travel to France to
> > check it out :)
> >
> 
> Here I am conveniently in France:

Thank you.

> 
> curty@einstein:~$ wget -S --spider https://wiki.debian.org
> Spider mode enabled. Check if remote file exists.
> --2018-02-17 19:52:06--  https://wiki.debian.org/
> Resolving wiki.debian.org (wiki.debian.org)... 82.195.75.112, 
> 2001:41b8:202:deb:6564:a62:52c3:4b70
> Connecting to wiki.debian.org (wiki.debian.org)|82.195.75.112|:443... 
> connected.
> HTTP request sent, awaiting response... 
>   HTTP/1.1 403 FORBIDDEN
>   Date: Sat, 17 Feb 2018 18:52:06 GMT
>   Server: Apache
>   X-Content-Type-Options: nosniff
>   X-Frame-Options: sameorigin
>   Referrer-Policy: no-referrer
>   X-Xss-Protection: 1
>   Strict-Transport-Security: max-age=15552000
>   Public-Key-Pins: pin-sha256="yPqY/77C2aLVJIEAYtuMrFy+cX6g4CatH03gcBQbxpo="; 
> pin-sha256="TzmD7DK6d5d7RU66/XTJtlENSfv+i0P7x2Xmpl8uFrY="; max-age=5184000
>   Content-Length: 166
>   X-Clacks-Overhead: GNU Terry Pratchett
>   Keep-Alive: timeout=5, max=100
>   Connection: Keep-Alive
>   Content-Type: text/html
> Remote file does not exist -- broken link!!!
> 
> I surfed the wiki the other day, no problemo, but "HTTP/1.1 403 FORBIDDEN"?

Weird, isn't it? Someone responsible to wiki.debian.org blocked the
whole 78.192.0.0/10 subnet (AS12322), so it seems.

Reco

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Curt

On 2018-02-17, Reco  wrote:
>
> First, please don't get me wrong, but can you provide the output of
> (regular box, of course):
>
> wget -S --spider https://wiki.debian.org
>
> There have been some reports from people using your ISP that this page
> does not work for them somehow, and I'm too lazy to travel to France to
> check it out :)
>

Here I am conveniently in France:

curty@einstein:~$ wget -S --spider https://wiki.debian.org
Spider mode enabled. Check if remote file exists.
--2018-02-17 19:52:06--  https://wiki.debian.org/
Resolving wiki.debian.org (wiki.debian.org)... 82.195.75.112, 
2001:41b8:202:deb:6564:a62:52c3:4b70
Connecting to wiki.debian.org (wiki.debian.org)|82.195.75.112|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 403 FORBIDDEN
  Date: Sat, 17 Feb 2018 18:52:06 GMT
  Server: Apache
  X-Content-Type-Options: nosniff
  X-Frame-Options: sameorigin
  Referrer-Policy: no-referrer
  X-Xss-Protection: 1
  Strict-Transport-Security: max-age=15552000
  Public-Key-Pins: pin-sha256="yPqY/77C2aLVJIEAYtuMrFy+cX6g4CatH03gcBQbxpo="; 
pin-sha256="TzmD7DK6d5d7RU66/XTJtlENSfv+i0P7x2Xmpl8uFrY="; max-age=5184000
  Content-Length: 166
  X-Clacks-Overhead: GNU Terry Pratchett
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html
Remote file does not exist -- broken link!!!

I surfed the wiki the other day, no problemo, but "HTTP/1.1 403 FORBIDDEN"?




-- 
New York was no mere city. It was instead an infinitely romantic notion, the
mysterious nexus of all love and money and power, the shining and the
perishable dream itself. To think of 'living' there was to reduce the
miraculous to the mundane; one does not 'live' at Xanadu. --Joan Didion

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Brian

On Sat 17 Feb 2018 at 16:20:06 +0100, Roger Price wrote:

> I am trying to net install stretch i386 on an EeePC using a wired
> connection. I chose my ISP as the mirror, but the installation hangs on
> "Configure the packet management tool (APT)" [french text reads "Configurer
> l'outil de gestion des paquets (APT)"].
> 
> I checked on my regular box that stretch i386 is available at 
> debian.proxad.net
> 
>  rprice@maria ~ wget --no-verbose
>http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
>'^(Suite|Codename|Architectures):'
>  Suite: stable
>  Codename: stretch
>  Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
> s390x

That works for me too.
 
> but on the EeePC with Ctl-Alt-F3 I get
> 
>  ~ # wget --no-verbose
>http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
>'^(Suite|Codename|Architectures):'
>  wget: unable to resolve host address 'debian.proxad.net'
> 
> Command « ip address » shows that the EeePC has been assigned the correct IP
> address 10.218.0.100, and /etc/resolv.conf correctly points to the router as
> the DNS resolver:
> 
>  ~ # cat /etc/resolv.conf
>  search rogerprice.org
>  nameserver 10.218.0.1
> 
> I am using the same router and the same name server to post this message.
> Any suggestion or hint for fixing the installation would be most welcome,

I would try pinging www.debian.org and anywhere else you can think of.
Or edit resolv.conf to have 8.8.8.8 (a Google nameserver).

-- 
Brian.

Re: Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Reco

Hi.

On Sat, Feb 17, 2018 at 04:20:06PM +0100, Roger Price wrote:
> I am trying to net install stretch i386 on an EeePC using a wired
> connection. I chose my ISP as the mirror, but the installation hangs on
> "Configure the packet management tool (APT)" [french text reads "Configurer
> l'outil de gestion des paquets (APT)"].
> 
> I checked on my regular box that stretch i386 is available at 
> debian.proxad.net
> 
>  rprice@maria ~ wget --no-verbose
>http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
>'^(Suite|Codename|Architectures):'
>  Suite: stable
>  Codename: stretch
>  Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
> s390x
> 
> but on the EeePC with Ctl-Alt-F3 I get
> 
>  ~ # wget --no-verbose
>http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
>'^(Suite|Codename|Architectures):'
>  wget: unable to resolve host address 'debian.proxad.net'
> 
> Command « ip address » shows that the EeePC has been assigned the correct IP
> address 10.218.0.100, and /etc/resolv.conf correctly points to the router as
> the DNS resolver:
> 
>  ~ # cat /etc/resolv.conf
>  search rogerprice.org
>  nameserver 10.218.0.1
> 
> I am using the same router and the same name server to post this message.
> Any suggestion or hint for fixing the installation would be most welcome,

First, please don't get me wrong, but can you provide the output of
(regular box, of course):

wget -S --spider https://wiki.debian.org

There have been some reports from people using your ISP that this page
does not work for them somehow, and I'm too lazy to travel to France to
check it out :)

Returning to your problem, I'd like to propose using Debian LiveCD [1]
on the problematic EeePC as LiveCD has some proper network
troubleshooting tools, namely tcpdump.

An file produced by:

tcpdump -w /tmp/proxad.pcap -ni any udp port 53 or udp port 5353 \
or tcp port 80

while running 

wget http://debian.proxad.net/debian/dists/stretch/Release -O /dev/null

would be invaluable in solving this out.

[1] http://www.debian.org/CD/live

Reco

Stretch net install on EeePC - unable to resolve mirror host address

2018-02-17 Thread Roger Price

I am trying to net install stretch i386 on an EeePC using a wired connection. I 
chose my ISP as the mirror, but the installation hangs on "Configure the packet 
management tool (APT)" [french text reads "Configurer l'outil de gestion des 
paquets (APT)"].


I checked on my regular box that stretch i386 is available at debian.proxad.net

 rprice@maria ~ wget --no-verbose
   http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
   '^(Suite|Codename|Architectures):'
 Suite: stable
 Codename: stretch
 Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x

but on the EeePC with Ctl-Alt-F3 I get

 ~ # wget --no-verbose
   http://debian.proxad.net/debian/dists/stretch/Release -O - | grep -E
   '^(Suite|Codename|Architectures):'
 wget: unable to resolve host address 'debian.proxad.net'

Command « ip address » shows that the EeePC has been assigned the correct IP 
address 10.218.0.100, and /etc/resolv.conf correctly points to the router as the 
DNS resolver:


 ~ # cat /etc/resolv.conf
 search rogerprice.org
 nameserver 10.218.0.1

I am using the same router and the same name server to post this message. Any 
suggestion or hint for fixing the installation would be most welcome,


Roger

45 matches

Mail list logo