I am new to networking trying get cumulus pass my internet connect to the vm. PS OSPF works good.


I have set up Proxmox and virtual box env. One of my interfaces is on the public side of the network and one intent network that has quest running on it. Form the quest I can ping all the interfaces. I can ping google form the CumulusLinux but not form quest.

16 replies

Userlevel 5
I am unfamiliar with the Proxmox software. Is it possible you may have missed a configuration in there that would allow the quest to see out of the virtualization? Is it possible for you to post configuration for the routing on both setups?
cumulus@cumulus$ 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

#auto bridge
#iface bridge inet static
# address 192.168.0.98
# netmask 255.255.255.0
# gateway 192.168.0.1
# bridge_ports swp1 swp2
# up /usr/sbin/brctl stp bridge off

# The primary network interface
auto eth0
iface eth0 inet dhcp
# up ip route add 0.0.0.0/0 192.168.0.1
# post-up route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.1
# pre-down route del -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.1
# Static setup
#iface eth0 inet static
# address 10.0.2.15
# netmask 255.255.255.0
# gateway 10.0.2.2

auto swp1
iface swp1
# bridge access 100
address 192.168.1.1/24
# up ip route add 0.0.0.0/0 via 192.168.0.1

auto swp2
iface swp2
# gateway 192.168.0.1
# bridge access 100
address 192.168.0.99/16
# up ip route add 0.0.0.0/0 via 192.168.0.1
cumulus@cumulus$

cumulus@cumulus$ cat /etc/quagga/Quagga.conf
service integrated-vtysh-config

router-id 192.168.0.99

router ospf
ospf router-id 192.168.0.99
network 192.168.0.0/24 area 0
network 192.168.1.0/24 area 0
cumulus@cumulus$ sudo nano /etc/quagga/Quagga.conf
[sudo] password for cumulus:

opps here you go
Userlevel 5
What does the routing look like on the quest part? Can you do a traceroute on the quest to see where the link dies?



I hope this is what you needed

it stops at 192.168.1.1
Userlevel 5
Can you try those again using an external IP like google.com or the like?


If i can see outside ip's why would i be use DNS? Cumulus and all the other VM's work see network fine. But cumulus is not pass traffic to the other side.
Userlevel 5
OK, so lets take a look at this.

What is the routing table on the kali VM?
Does the Kali VM have a Firewall built in that may be blocking it?
Your internal traceroutes are fine because it is internal. I want to see where it dies from there.
Run the following command: traceroute 8.8.8.8
What is the networking configuration on the Kali VM?

Firewall on kali on lol. 8.8.8.8 dies at the same point all. 192.168.1.1 is gateway netmask 255.255.255.0 address 192.168.1.10
is this what you need to know.
scott what do you to help you still?
Userlevel 5
From what I can see it looks like everything is OK. There must be a setting in ProxMox that is blocking this VM. Are you routing it through the Cumulus VM?
I should be routing it though cumulus but that part not sure about.

Reply