You are not logged in.
edit :
the problem was that systemd-resolvconf was not installed.
Last edited by boreec (2019-09-24 17:09:37)
Offline
Address: 172.18.15.30
The 172.16.x.x to 172.31.x.x range are private ip-addresses.
Can you ping them ?
Ask the sys admins whether those intranet sites need some kind of authentication (possibly a windows domain login).
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I cant tell if it's identically caused from your error messages, but i had the same problem at UCLA. They blacklist IP addresses that belong to VPNs as being "suspicious". Most perniciously, even if off campus, they will bounce an email sent to a ucla.edu email address from a VPN IP address WITHOUT NOTIFYING THE SENDER. So now, you cant get on certain sites, which at least you know is happening, but you also cant send email, which you have no way of knowing is happening. You should consult your university's IT department to determine their policies. Good luck!
Last edited by yggdrasil673 (2019-09-24 12:40:32)
Offline
@Lone_Wolf
I can ping the address 172.x.x.30 (which correspond to the gitlab). I can even do mtr on it. As the regular gitlab, it requires to log in, but it is done on the browser once the vpn is set up.
Here the gitlab homepage does not even appear. Firefox and elinks tell me "server not found". The only other log in step is when connecting with the VPN, but it is done well since I have
"Initialization Sequence Completed" line in the log.
@yggdrasil673
This is not related to my situation, the website I try to access to is provided by the university and claimed as being accessed with the VPN. It worked for me in the past when I used another
linux distro. The VPN configuration is also provided by the university.
Last edited by boreec (2019-09-24 17:10:01)
Offline
Do you use systemd-resolved?
ps aux | grep resolved
Offline
Thanks for pointing that @Seth, I did not see that part of the configuration and I fixed it by installing systemd-resolvconf package.
Now it's working.
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline