Search results

ifupdown2 2.0.1-1+pve4 For what it matters, I ditched OVS completely, I honestly can do what I need with pfSense and layer 2 rather than layer 3 and OVS

Chiming in here as I was directed from another thread. Same issue here, using ifupdown2 and OVS. I very specifically did the upgrade, rebooted and every server booped up after that. My temporary fix was to add auto vmbr1 to my OVS bridge, which is not ideal. Following.

Yes indeed using ifupdown2. Will have a look and report back. Thought it may have been something with the OVS update and/or kernel. My temporary fix has been to add auto vmbr1, which drops off if I make any gui changes.

Need a little bit more detail before I start blabing out details. How many hosts do you have, how many NICs, which are WAN facing, which are VXLAN facing? The GRE tunnel is an option, but it really comes down to how you have this deployed and then I can probably guide you from there.

Hey there, so basically you are in the same boat as I am, only difference is I've setup a mesh network instead of using a switch on the backbone for the VXLAN. You want to be looking at openvswitch for your layer 3 switching, and pfSense to connect your vmbr0 to vmbr1/2/3/etc. This way you can...

update, something in the last kernel update stops openvswitch-switch from auto creating the routes. adding auto vmbr1 does add the routes, however making any changes in the webgui removes this line from /etc/network/interfaces. Using purely ifupdown2 (the ip address add) command, how can I...

ifconfig uses net-tools, by default (and more mainstream these days), ethtools is used. try: ip address ip link ip route ip up/down for your commands

update, i'm going to say something went hay wire, my OVS routes are totally gone.

Greetings, has anyone else had issues with OVS on the last update? I see it upgraded to 2.10.1. i had to change my bridges back to standard to even get gui access. ovs-system shows DOWN state, vmbr1 shows UNKNOWN state. any help would be appreciated. usually with my config, rebooting and such...

Confirmed same issue here, Anything internal is not working. I'm running a mesh network with OVS for my layer3. No web access while my vmbr0 was configured for ovs, had to switch it back to a standard bridge, but still my internal network is borked.

root@pve1:/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/PVE/RADOS# pveceph init Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.28/auto/PVE/RADOS/RADOS.so' for module PVE::RADOS: libceph-common.so.0: cannot open shared object file: No such file or directory at...

So here we go, my buddy and I worked through the issue, I do believe this is a ceph bug. We both work as high level ITs. In short, do all the stuff listed above, once done run these 3 commands and you should have a working package again. It appears after doing a purge or removing ceph ceph-mon...

Can you share your configs for shorewall? I'm in need to help

since my last post, tried this now using vmbr0 on x.x.7.145, running the following: root@proxmox:~# traceroute 174.142.7.144 traceroute to 174.142.7.144 (174.142.7.144), 30 hops max, 60 byte packets connect: Permission denied if i try doing same on x.x.7.151, same thing - my DC is confusing me...

stupid datacenter. just talked to them again, ok so all IP have same mac as primary for starters. secondly, i have 8 IP x.x.7.144 - x.x.7.151 they say if using 255.255.255.248 only 6 are usable, but if i use 255.255.255.255 8 are usable. the more the better, does that make sense?

these are the 3 links to bare metal hypervisors they confirm work, so the difference is in using vmbrx? http://kb.iweb.com/entries/21140298-VMware-Configuring-additional-IPs-Linux- http://kb.iweb.com/entries/21247096-Virtualization-Ready-Xen-User-Guide?locale=1...

sigh, that didn't work either. I'm still looking at these and trying to understand how to change it to work with proxmox.

Hmmm, so maybe not all the way there yet. When I do a traceroute, shows x.x.164.207 as first hop, and also can't connect to those secondary IPs (from outside). So from within a vm, I can hit the internet, but can't seem to get in (I installed request tracker from the templates) - updated the IP...

OK! Finally got it working, silly me made a typo, in the above in the iptables line, it should have been x.x.7.144 for both lines, now i get external. But i guess my last question, in my proxmox network gui, it's now set like this: name: eth0 active: yes autostart: no ports/slaves: ip address...

I tried the config in the above link, same story, within the vm, cant ping gateway. i swear its got to be routing, is it iptables2 in proxmox? from the above test, i have eth0, vmbr0, vmbr1 (setup at proxmox gui). then at proxmox vm gui i have venet with x.x.7.145. this produces same result as...