Primeiro de tudo o mencionado Ubuntu Server é um servidor virtual em execução na rede do campus da minha universidade e eu posso ssh para ele de casa através de vpn. No entanto, enquanto eu estou logado via ssh eu posso pingar nem o gateway padrão do servidor nem qualquer outro ip (100% de perda de pacotes).
Como isso é possível?
A única coisa que fiz desde que entrei na primeira vez foi alterar o par de chaves ssh, nada mais. E vale a pena mencionar que o servidor deve ter uma conexão com a internet.
Agradeço qualquer ajuda, pois não poderei entrar em contato com os administradores pelos próximos dias de visualização, pelo menos.
ifconfig -a
ens3 Link encap:Ethernet HWaddr fa:16:3e:cf:3f:62
inet addr:139.6.102.145 Bcast:139.6.102.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fecf:3f62/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12546 errors:0 dropped:1591 overruns:0 frame:0
TX packets:1445 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:941130 (941.1 KB) TX bytes:235770 (235.7 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:166 errors:0 dropped:0 overruns:0 frame:0
TX packets:166 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:12344 (12.3 KB) TX bytes:12344 (12.3 KB)
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 139.6.102.1 0.0.0.0 UG 0 0 0 ens3
139.6.102.0 0.0.0.0 255.255.255.0 U 0 0 0 ens3
169.254.169.254 139.6.102.18 255.255.255.255 UGH 0 0 0 ens3
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
status de rede do serviço sudo
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: active (exited) since Thu 2018-04-19 21:00:28 UTC; 1h 0min ago
Docs: man:interfaces(5)
Process: 723 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
Process: 708 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
Main PID: 723 (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0
CGroup: /system.slice/networking.service
Apr 19 21:00:27 Webpraktikum systemd[1]: Starting Raise network interfaces...
Apr 19 21:00:27 Webpraktikum ifup[723]: /sbin/ifup: waiting for lock on /run/network/ifstate.ens3
Apr 19 21:00:28 Webpraktikum systemd[1]: Started Raise network interfaces.
cat / etc / network / interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# Source interfaces
# Please check /etc/network/interfaces.d before changing this file
# as interfaces may have been defined in /etc/network/interfaces.d
# See LP: #1262951
source /etc/network/interfaces.d/*.cfg
ls /etc/network/interfaces.d
50-cloud-init.cfg
cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
auto ens3
iface ens3 inet dhcp
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 139.6.1.2
search openstacklocal