Support and News Forum

I have EVE set up as a bare metal install. I can telnet to all devices and i have web access to the lab setup. When i try to setup a connection to test dhcp between the cloud and a router, i cannot ping the gateway. my Pnet0 set is below:

# The primary network interface
iface eth0 inet manual
auto pnet0
iface pnet0 inet static
address 192.168.1.240
netmask 255.255.255.0
gateway 192.168.1.1
dns-domain example.com
dns-nameservers 8.8.8.8
bridge_ports eth0
bridge_stp off

jiggamaine wrote: ↑

Wed May 03, 2017 7:27 pm

I have EVE set up as a bare metal install. I can telnet to all devices and i have web access to the lab setup. When i try to setup a connection to test dhcp between the cloud and a router, i cannot ping the gateway. my Pnet0 set is below:

# The primary network interface
iface eth0 inet manual
auto pnet0
iface pnet0 inet static
address 192.168.1.240
netmask 255.255.255.0
gateway 192.168.1.1
dns-domain example.com
dns-nameservers 8.8.8.8
bridge_ports eth0
bridge_stp off

Show us your topology and let us know more details about your setup.

R!

Just a basic setup. R1 Config below:

int fa0/0
ip address dhcp
no shutdown
end

no default route as it is a direct connect.

Hi,I have the same problem too

i have the same problem too

here is my configs

auto wlan0
auto pnet0

iface wlan0 inet manual
wpa-ssid xxxxxxx
wpa-psk xxxxyyyyy

# Cloud device Bridge

iface pnet0 inet static
bridge_ports wlan0
bridge_stp off
address 192.168.1.150
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 163.121.128.134 163.121.128.135



i can ping the internet from cli , but from the RTR can not ???!!!

plz help ,

Thanks

Check do you have DHCP Server offering IP in the network.

Just did a quick test for you. it works straight forward. R!

Hi Guys , I solved the issue

here is the solution I used

# The primary network interface
auto wlan0
auto pnet0





iface wlan0 inet static
wpa-ssid Linksys05420
wpa-psk voda20201010
address 192.168.1.150
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameaerver 163.121.128.134 163.121.128.135


# Cloud device

iface pnet0 inet static
address 10.10.10.1
netmask 255.255.255.0
bridge_ports wlan0
bridge_stp off

=========================================================================================================================================
natting

sudo iptables -A FORWARD -o wlan0 -i pnet0 -s 10.10.10.0/24 -m conntrack --ctstate NEW -j ACCEPT
sudo iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
sudo iptables -t nat -F POSTROUTING
sudo iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE

sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"



The RTR will have IP add of 10.10.10.2 /24 and route as
ip route 0.0.0.0 0.0.0.0 10.10.10.1
ip name-server 8.8.8.8

===================================================================================================================================


sudo iptables-save | sudo tee /etc/iptables.sav

vi /etc/rc.local

and add the following lines before the "exit 0" line:

iptables-restore < /etc/iptables.sav



vi /etc/sysctl.conf edit is required

#net.ipv4.ip_forward=1

... so that it reads:

net.ipv4.ip_forward=1




Now I can reach the internet and all is working just fine .

without wanting to do the natting option here is my configs for eve and my router. Also did a traceroute from R1 and it seems it doesn't know how to get past EVE.

Router#traceroute 192.168.1.240

Type escape sequence to abort.
Tracing the route to 192.168.1.240

1 192.168.1.240 0 msec 0 msec 12 msec
Router#traceroute 8.8.8.8

Type escape sequence to abort.
Tracing the route to 8.8.8.8

1 *
192.168.1.240 4 msec *
2 * * *
3 * * *
4 * * *
5 * * *


# The primary network interface
iface eth0 inet manual
auto pnet0
iface pnet0 inet static
address 192.168.1.240
netmask 255.255.255.0
gateway 192.168.1.1
dns-domain example.com
dns-nameservers 8.8.8.8
bridge_ports eth0
bridge_stp off