Page 1 of 1

Telnet Terminal Can't Resolving Domain Names

Posted: Sun Jun 21, 2020 3:54 am
by ron.allen.smith
Hi,
I could not find an answer for this in my search. I set up a basic lab to connect VPCS node to Management(Cloud0) over eth0.
Everything pings correctly. But when pinging google.com, or any other domain, in the telnet session, the telnet console hangs, then disappears. After that, I have to Stop/Start the VPC again and start a new telnet session.

Using VMWare Pro 11.5.5
Using EVE-NG Community
Using NAT
EVE-ClientPack.dmg is installed

Hardware Overview:

Model Name: MacBook Pro
Processor Name: Quad-Core Intel Core i7
Processor Speed: 2.2 GHz
Number of Processors: 1
Total Number of Cores: 4
Memory: 16 GB
Hyper-Threading Technology: Enabled

root login to EVE-COMM-VM says:
Use http://192.168.195.128 on Ubuntu 16.04.6
the root 'route' command says:
Destination Gateway defaults to 192.168.195.2
Root can ping 'google.com' with 0 packet loss.
Root can also ping 172.217.8.14 (google.com)

VPC telnet says:

VPCS> show ip

NAME : VPCS[1]
IP/MASK : 192.168.195.3/24
GATEWAY : 192.168.195.2
DNS : 8.8.8.8

VPCS> ping 192.168.195.2

84 bytes from 192.168.195.2 icmp_seq=1 ttl=128 time=0.327 ms
84 bytes from 192.168.195.2 icmp_seq=2 ttl=128 time=0.366 ms
84 bytes from 192.168.195.2 icmp_seq=3 ttl=128 time=0.334 ms
^C
VPCS> ping 8.8.8.8

84 bytes from 8.8.8.8 icmp_seq=1 ttl=128 time=8.295 ms
84 bytes from 8.8.8.8 icmp_seq=2 ttl=128 time=12.175 ms
84 bytes from 8.8.8.8 icmp_seq=3 ttl=128 time=14.293 ms
^C
VPCS> ping 172.217.8.14

84 bytes from 172.217.8.14 icmp_seq=1 ttl=128 time=72.832 ms
84 bytes from 172.217.8.14 icmp_seq=2 ttl=128 time=78.021 ms
84 bytes from 172.217.8.14 icmp_seq=3 ttl=128 time=61.950 ms
^C
VPCS> ping google.com
Telnet window hangs and blows up. Then I have to Stop/Start VPC and start new telnet session.

What am I missing?

TIA

Re: Telnet Terminal Can't Resolving Domain Names

Posted: Sun Jun 21, 2020 8:41 am
by Uldis (UD)
do not use VPCS it is very buggy image, especially for cloud and internet.
Take any simple router instead