Just purchased and installed an EVE- Pro instance.
This has been registered successfully.
Every time I issue: /opt/unetlab/wrappers/unl_wrapper -a fixpermissions I get the below output:
root@eve-ng:~# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
Q1: Why am I getting: Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid ??
Q2: What does Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid mean?
Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
Moderator: mike
-
- Posts: 92
- Joined: Tue Oct 24, 2017 2:42 pm
-
- Posts: 92
- Joined: Tue Oct 24, 2017 2:42 pm
Re: Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
Also, this is my EVE´s routing table:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.5.1 0.0.0.0 UG 0 0 0 pnet0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.29.129.0 0.0.0.0 255.255.255.0 U 0 0 0 nat0
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0 pnet0
AND
root@eve-ng:~# ifconfig pnet0
pnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.5.50 netmask 255.255.255.0 broadcast 192.168.5.255
For the management cloud and my EVE´s internal devices to have outbound connectivity to the internet, do I need to set my internal device´s next hop pointing at:
a) EVE's gateway: 192.168.5.1
OR
b) EVE´management IP: 192.168.5.50
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.5.1 0.0.0.0 UG 0 0 0 pnet0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.29.129.0 0.0.0.0 255.255.255.0 U 0 0 0 nat0
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0 pnet0
AND
root@eve-ng:~# ifconfig pnet0
pnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.5.50 netmask 255.255.255.0 broadcast 192.168.5.255
For the management cloud and my EVE´s internal devices to have outbound connectivity to the internet, do I need to set my internal device´s next hop pointing at:
a) EVE's gateway: 192.168.5.1
OR
b) EVE´management IP: 192.168.5.50
-
- Posts: 92
- Joined: Tue Oct 24, 2017 2:42 pm
Re: Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
Ping is not working, please advise:
config system interface
edit "port1"
set vdom "root"
set ip 192.168.50.100 255.255.255.0
set allowaccess ping https ssh snmp http
set type physical
set alias "port1"
set snmp-index 1
next
FortiGate-VM64-KVM # get system arp
Address Age(min) Hardware Addr Interface
192.168.5.1 0 00:09:0f:d3:3d:59 port1
FortiGate-VM64-KVM # get router info routing-table static
Routing table for VRF=0
S* 0.0.0.0/0 [10/0] via 192.168.5.1, port1
FortiGate-VM64-KVM # execute ping 192.168.5.1
^Cbinding source interface address error.
PING 192.168.5.1 (192.168.5.1): 56 data bytes
--- 192.168.5.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
config system interface
edit "port1"
set vdom "root"
set ip 192.168.50.100 255.255.255.0
set allowaccess ping https ssh snmp http
set type physical
set alias "port1"
set snmp-index 1
next
FortiGate-VM64-KVM # get system arp
Address Age(min) Hardware Addr Interface
192.168.5.1 0 00:09:0f:d3:3d:59 port1
FortiGate-VM64-KVM # get router info routing-table static
Routing table for VRF=0
S* 0.0.0.0/0 [10/0] via 192.168.5.1, port1
FortiGate-VM64-KVM # execute ping 192.168.5.1
^Cbinding source interface address error.
PING 192.168.5.1 (192.168.5.1): 56 data bytes
--- 192.168.5.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
-
- Posts: 92
- Joined: Tue Oct 24, 2017 2:42 pm
Re: Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
This has been sorted but despite having IP connectivity to port1 I´m unable to http onto it.
Also, I don´t see an ARP entry for 192.168.5.100 on EVE, why is this?
root@eve-ng:~# ping 192.168.5.100
PING 192.168.5.100 (192.168.5.100) 56(84) bytes of data.
64 bytes from 192.168.5.100: icmp_seq=1 ttl=255 time=0.655 ms
64 bytes from 192.168.5.100: icmp_seq=2 ttl=255 time=0.616 ms
64 bytes from 192.168.5.100: icmp_seq=3 ttl=255 time=0.617 ms
64 bytes from 192.168.5.100: icmp_seq=4 ttl=255 time=0.461 ms
64 bytes from 192.168.5.100: icmp_seq=5 ttl=255 time=0.644 ms
64 bytes from 192.168.5.100: icmp_seq=6 ttl=255 time=0.588 ms
^C
--- 192.168.5.100 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5109ms
rtt min/avg/max/mdev = 0.461/0.596/0.655/0.071 ms
root@eve-ng:~# arp -a
? (192.168.5.100) at 50:00:00:01:00:00 [ether] on pnet0
_gateway (192.168.5.1) at 00:09:0f:d3:3d:59 [ether] on pnet0
Also, I don´t see an ARP entry for 192.168.5.100 on EVE, why is this?
root@eve-ng:~# ping 192.168.5.100
PING 192.168.5.100 (192.168.5.100) 56(84) bytes of data.
64 bytes from 192.168.5.100: icmp_seq=1 ttl=255 time=0.655 ms
64 bytes from 192.168.5.100: icmp_seq=2 ttl=255 time=0.616 ms
64 bytes from 192.168.5.100: icmp_seq=3 ttl=255 time=0.617 ms
64 bytes from 192.168.5.100: icmp_seq=4 ttl=255 time=0.461 ms
64 bytes from 192.168.5.100: icmp_seq=5 ttl=255 time=0.644 ms
64 bytes from 192.168.5.100: icmp_seq=6 ttl=255 time=0.588 ms
^C
--- 192.168.5.100 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5109ms
rtt min/avg/max/mdev = 0.461/0.596/0.655/0.071 ms
root@eve-ng:~# arp -a
? (192.168.5.100) at 50:00:00:01:00:00 [ether] on pnet0
_gateway (192.168.5.1) at 00:09:0f:d3:3d:59 [ether] on pnet0
-
- Posts: 92
- Joined: Tue Oct 24, 2017 2:42 pm
Re: Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
root@eve-ng:~# arp -a
? (192.168.5.100) at 50:00:00:01:00:00 [ether] on pnet0
_gateway (192.168.5.1) at 00:09:0f:d3:3d:59 [ether] on pnet0
? (192.168.5.100) at 50:00:00:01:00:00 [ether] on pnet0
Security policy
Allow promiscuous mode Yes
Allow forged transmits Yes
Allow MAC changes Yes
NIC teaming policy
Notify switches Yes
Policy Route based on originating port ID
Reverse policy Yes
Failback Yes
Shaping policy
Enabled No
? (192.168.5.100) at 50:00:00:01:00:00 [ether] on pnet0
_gateway (192.168.5.1) at 00:09:0f:d3:3d:59 [ether] on pnet0
? (192.168.5.100) at 50:00:00:01:00:00 [ether] on pnet0
Security policy
Allow promiscuous mode Yes
Allow forged transmits Yes
Allow MAC changes Yes
NIC teaming policy
Notify switches Yes
Policy Route based on originating port ID
Reverse policy Yes
Failback Yes
Shaping policy
Enabled No
-
- Posts: 5080
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Oct 22 10:25:42 Oct 22 10:25:42 Online Check state: Valid
For lab nodes connected to cloud0 obviously GW is EVE's GW IP 5.1
And do you have bound of NIC team on esxi? if yes it can be issue then
And do you have bound of NIC team on esxi? if yes it can be issue then