Your message dated Thu, 30 Jul 2020 12:09:46 +0100
with message-id 
<57b20cf34f28db60624c7c8275d920690b03b905.ca...@adam-barratt.org.uk>
and subject line Re: Bug#966536: bugs.debian.org (140.211.166.201) is not 
reachable
has caused the Debian Bug report #966536,
regarding bugs.debian.org (140.211.166.201) is not reachable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
966536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966536
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: important

zira:~> ping bugs.debian.org
PING bugs.debian.org (140.211.166.201) 56(84) bytes of data.
^C
--- bugs.debian.org ping statistics ---
212 packets transmitted, 0 received, 100% packet loss, time 215779ms

And with mtr:

zira:~> mtr -r bugs.debian.org
Start: 2020-07-30T12:43:02+0200
HOST: zira                        Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.1.1                0.0%    10    0.6   0.5   0.5   0.6   0.0
  2.|-- 69gui1-nro-1.nro.gaoland.  0.0%    10    2.3   2.0   0.9   2.6   0.7
  3.|-- 113.10.3.109.rev.sfr.net   0.0%    10    1.5   2.0   1.5   3.0   0.6
  4.|-- 101.216.129.77.rev.sfr.ne  0.0%    10    8.0   8.6   8.0   9.4   0.5
  5.|-- 101.216.129.77.rev.sfr.ne  0.0%    10    7.9   8.2   7.1   8.8   0.5
  6.|-- be5261.ccr31.par04.atlas.  0.0%    10    9.8   9.6   8.6  10.2   0.6
  7.|-- be3184.ccr42.par01.atlas.  0.0%    10    8.0   8.8   8.0   9.5   0.5
  8.|-- be12489.ccr42.lon13.atlas  0.0%    10   16.1  16.6  16.1  17.2   0.3
  9.|-- be2101.ccr32.bos01.atlas.  0.0%    10   79.0  79.0  77.9  79.6   0.6
 10.|-- be3600.ccr22.alb02.atlas.  0.0%    10   82.8  82.4  81.4  83.4   0.8
 11.|-- be2879.ccr22.cle04.atlas.  0.0%    10   94.4  93.1  92.3  94.4   0.6
 12.|-- be2718.ccr42.ord01.atlas.  0.0%    10   99.3 100.0  99.3 100.7   0.4
 13.|-- be2832.ccr22.mci01.atlas.  0.0%    10  111.7 112.3 111.4 112.9   0.5
 14.|-- be3036.ccr22.den01.atlas.  0.0%    10  124.0 123.7 122.5 124.4   0.7
 15.|-- be3038.ccr32.slc01.atlas.  0.0%    10  133.2 133.6 133.2 134.0   0.3
 16.|-- 154.54.89.101              0.0%    10  153.9 154.4 153.9 155.0   0.3
 17.|-- be2671.ccr21.pdx01.atlas.  0.0%    10  157.2 157.5 156.8 157.9   0.3
 18.|-- cogent-pdx.nero.net        0.0%    10  158.9 158.5 157.3 160.0   0.9
 19.|-- ptck-p1-gw.nero.net        0.0%    10  157.4 159.5 157.4 165.2   2.8
 20.|-- 207.98.64.45               0.0%    10  160.9 161.5 160.0 162.6   0.8
 21.|-- corv-car1-gw.nero.net      0.0%    10  159.7 160.1 158.9 160.6   0.5
 22.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0

I'm wondering whether there is/was something wrong with the DNS
configuration since on other machines, I get other IP addresses.

Note: I've just switched to NetworkManager, and before that I didn't
have any issue. I hope that it doesn't provide hardcoded IP addresses.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

--- End Message ---
--- Begin Message ---
On Thu, 2020-07-30 at 13:03 +0200, Vincent Lefevre wrote:
> On 2020-07-30 12:48:52 +0200, Vincent Lefevre wrote:
> > Note: I've just switched to NetworkManager, and before that I
> > didn't have any issue. I hope that it doesn't provide hardcoded IP
> > addresses.
> 
> Sorry, I actually had to hardcode an IP address in the past, due to
> an issue with one of the bugs.debian.org IP addresses, which was
> annoying me for several weeks (bug 904311; I don't know whether it is
> still valid, but it is still open!). This hardcoded IP address was
> working until now, so I forgot about it.
> 
> Now solved for bugs.debian.org, but since this still corresponds to a
> Debian machine (beach.debian.org), I let this bug open in case this
> is really unexpected.

beach is being decommissioned and is no longer part of the bugs.d.o
rotation, so I'm closing this bug.

Thanks for the update.

Regards,

Adam

--- End Message ---

Reply via email to