Re: Could not visit bgo from my specific IP range.

[Yifan Jiang <yfjiang suse com>]

Hi Andrea,

Thank you!

Currently, the blocked exit address of SUSE office seems only on the specific
IP 45.122.156.254, which is provided by a HK ISP. So, in compare with
releasing a range, I assume it may be safer to release the single IP at the
first place. Then I could do some testing and tell you if it works, how does
it sound?

- Yifan

On Tue, Sep 12, 2017 at 03:12:30PM +0200, Andrea Veri wrote:
> Hey,
>
> yeah, seems that particular IP was banned, got a range I can whitelist
> for the relevant Suse office?
>
> 2017-09-07 4:23 GMT+02:00 Yifan Jiang <yfjiang suse com>:
> > Dear Gnome hackers,
> >
> > Recently when I tried to visit bugzilla.gnome.org from a IP range, it is
> > always blocked :-(
> >
> > Chrome shows:
> >
> >   https://bugzilla.gnome.org/ is unreachable.
> >   ERR_ADDRESS_UNREACHABLE
> >
> > ping shows:
> >
> >   PING bugzilla.gnome.org (209.132.180.186) 56(84) bytes of data.
> >   From bugzilla-attachments.gnome.org (209.132.180.186) icmp_seq=1 Packet filtered
> >
> > From wireshark, it looks ICMP packet was failed to reach 209.132.180.186 via a
> > Code 13 feedback (Communication Administratively filtered).
> >
> > Specifically, from late last week, the issue has been always happening when I
> > visit bgo from a public IP (45.122.156.254). Otherwise, from IP ranges other
> > than that, I could visit bgo smoothly.
> >
> > Would you possibly have a kindly check? Thank you!
> >
> > Best regards,
> > Yifan
> > _______________________________________________
> > gnome-infrastructure mailing list
> > gnome-infrastructure gnome org
> > https://mail.gnome.org/mailman/listinfo/gnome-infrastructure