Search results
-
N
Network issues
But the venet device uses the same MAC as HN. I've also noticed that a trace from CT with venet shows HN IP as first hop. Means that traveling through CT->HN reduces packet TTL. Didn't thought it is made this way, because that is not a real route, just a virtual bridge... Probably this could be...- NStorm
- Post #6
- Forum: Proxmox VE 1.x: Installation and configuration
-
N
Network issues
As it comes through the same switch port, which is connect to eth0 of the HN and because HN doesn't affected by this issue I can exclude switch as the trouble part. Besides switch it is connected to are unmanaged so it can't be blocking something. I'm going to try opennode or some other openvz...- NStorm
- Post #4
- Forum: Proxmox VE 1.x: Installation and configuration
-
N
Network issues
Anyone? I also add that the iptables of both HN and CT are disabled (empty chains with default ACCEPT policy).- NStorm
- Post #2
- Forum: Proxmox VE 1.x: Installation and configuration
-
N
Network issues
I'm running Linux node1 2.6.32-6-pve #1 SMP Mon Sep 26 06:32:53 CEST 2011 x86_64 GNU/Linux. (Proxmox VE 1.9 distro) I have the following network setup 192.168.X.0/24 local subnet. HN and all CTs have IPs in that subnet. Like HN has 192.168.X.33 and CTs have 192.168.X.34, 192.168.X.35, etc. Also...- NStorm
- Thread
- Replies: 8
- Forum: Proxmox VE 1.x: Installation and configuration