Problem of shape of network

M

mercier

New Member
Mar 9, 2011
4
0
1
I do not succeed in configurer several networks since proxmox 1.6 and 1.7
My /etc/network/interfaces:
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

iface eth2 inet manual

iface eth3 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.54.174.148
netmask 255.255.255.0
gateway 192.54.174.250
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet static
address 192.54.175.56
netmask 255.255.255.0
bridge_ports eth1
bridge_stp off
bridge_fd 0
this shape works correctly on proxmox1.5

Thank you for your help!
 
mercier said:
I do not succeed in configurer several networks since proxmox 1.6 and 1.7
My /etc/network/interfaces:
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

iface eth2 inet manual

iface eth3 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.54.174.148
netmask 255.255.255.0
gateway 192.54.174.250
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet static
address 192.54.175.56
netmask 255.255.255.0
bridge_ports eth1
bridge_stp off
bridge_fd 0
this shape works correctly on proxmox1.5

Thank you for your help!
Click to expand...
Hi,
looks ok.
I use for eth* static, but this is not the problem i guess:
Code: 
auto eth0
iface eth0 inet static
        address  0.0.0.0
        netmask  0.0.0.0

auto eth1
iface eth1 inet static
        address  0.0.0.0
        netmask  0.0.0.0

auto vmbr0
...
Is your eth1 the right one? With kernel changes it can happen that udev rename eth1 to another eth.
Take a look with "dmesg | grep eth" and /etc/udev/rules.d/70-persistent-net.rules

Udo
 
Dear Udo,

Result from dmsg : dmsg|grep eth
from proxmox1.7
*********************

device eth0 entered promiscuous mode
bnx2: eth0: using MSIX
ADDRCONF(NETDEV_UP): eth0: link is not ready
device eth1 entered promiscuous mode
bnx2: eth1: using MSIX
ADDRCONF(NETDEV_UP): eth1: link is not ready
bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
vmbr0: port 1(eth0) entering forwarding state
bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Result from more /etc/udev/rules.d/70-persistent-net.rules
from proxmox1.7
*********************
# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:6b", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:6d", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:6f", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:71", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

Result from dmsg : dmsg|grep eth
from proxmox1.5
*********************
bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
vmbr0: port 1(eth0) entering learning state
vmbr0: port 1(eth0) entering forwarding state
bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex
vmbr1: port 1(eth1) entering learning state
vmbr1: port 1(eth1) entering forwarding state
eth0: received packet with own address as source address

Result from more /etc/udev/rules.d/70-persistent-net.rules
from proxmox1.5
*********************
more /etc/udev/rules.d/70-persistent-net.rules


# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:53", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth2"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:4f", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:51", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:55", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth3"

Thanks again for your help!
JM
Le mercredi 09 mars 2011 à 17:14 +0100, Proxmox Support Forum a écrit :
> dmesg | grep eth"
 
mercier said:
Dear Udo,

Result from dmsg : dmsg|grep eth
from proxmox1.7
*********************

device eth0 entered promiscuous mode
bnx2: eth0: using MSIX
ADDRCONF(NETDEV_UP): eth0: link is not ready
device eth1 entered promiscuous mode
bnx2: eth1: using MSIX
ADDRCONF(NETDEV_UP): eth1: link is not ready
bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
vmbr0: port 1(eth0) entering forwarding state
bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Result from more /etc/udev/rules.d/70-persistent-net.rules
from proxmox1.7
*********************
# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:6b", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:6d", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:6f", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="b8:ac:6f:95:40:71", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

Result from dmsg : dmsg|grep eth
from proxmox1.5
*********************
bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
vmbr0: port 1(eth0) entering learning state
vmbr0: port 1(eth0) entering forwarding state
bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex
vmbr1: port 1(eth1) entering learning state
vmbr1: port 1(eth1) entering forwarding state
eth0: received packet with own address as source address

Result from more /etc/udev/rules.d/70-persistent-net.rules
from proxmox1.5
*********************
more /etc/udev/rules.d/70-persistent-net.rules


# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:53", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth2"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:4f", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:51", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:26:b9:7d:33:55", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth3"

Thanks again for your help!
JM
Le mercredi 09 mars 2011 à 17:14 +0100, Proxmox Support Forum a écrit :
> dmesg | grep eth"
Click to expand...
Hi,
your interfaces are the same! That's not the problem. I mean something like this:
Code: 
Mar  7 15:27:41 prox kernel: e1000e 0000:0d:00.0: eth1: (PCI Express:2.5GB/s:Width x1) 00:15:17:f0:27:b8
Mar  7 15:27:41 prox kernel: e1000e 0000:0d:00.0: eth1: Intel(R) PRO/1000 Network Connection
Mar  7 15:27:41 prox kernel: e1000e 0000:0d:00.0: eth1: MAC: 1, PHY: 4, PBA No: d50861-004
Mar  7 15:27:41 prox kernel: e1000e 0000:0e:00.0: eth2: (PCI Express:2.5GB/s:Width x1) 00:15:17:c8:e4:7f
Mar  7 15:27:41 prox kernel: e1000e 0000:0e:00.0: eth2: Intel(R) PRO/1000 Network Connection
Mar  7 15:27:41 prox kernel: e1000e 0000:0e:00.0: eth2: MAC: 1, PHY: 4, PBA No: d50861-003
Mar  7 15:27:41 prox kernel: [B]udev: renamed network interface eth0 to eth2[/B]
Mar  7 15:27:41 prox kernel: [B]udev: renamed network interface eth2_rename to eth0[/B]

Hmm,
you can do further investigations with
Code: 
ifconfig -a
brctl show
tcpdump -i eth1
While tcpdump you must try to use the vmbr1 - if all is running you should see the traffic.
Do you have special things (routing/firewall/nat)?

Udo
 
Hi,

ifconfig -a:
eth0 Link encap:Ethernet HWaddr b8:ac:6f:95:40:6b
inet6 addr: fe80::baac:6fff:fe95:406b/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:20944 errors:0 dropped:0 overruns:0 frame:0
TX packets:886 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2982191 (2.8 MiB) TX bytes:98883 (96.5 KiB)
Interrupt:36 Memory:d6000000-d6012800

eth1 Link encap:Ethernet HWaddr b8:ac:6f:95:40:6d
inet6 addr: fe80::baac:6fff:fe95:406d/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:8704 Metric:1
RX packets:20337 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2911593 (2.7 MiB) TX bytes:862 (862.0 B)
Interrupt:48 Memory:d8000000-d8012800

eth2 Link encap:Ethernet HWaddr b8:ac:6f:95:40:6f
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:32 Memory:da000000-da012800

eth3 Link encap:Ethernet HWaddr b8:ac:6f:95:40:71
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:42 Memory:dc000000-dc012800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7223 errors:0 dropped:0 overruns:0 frame:0
TX packets:7223 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:946865 (924.6 KiB) TX bytes:946865 (924.6 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:3473 errors:0 dropped:0 overruns:0 frame:0
TX packets:3217 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:216792 (211.7 KiB) TX bytes:314218 (306.8 KiB)

vmbr0 Link encap:Ethernet HWaddr b8:ac:6f:95:40:6b
inet addr:192.54.174.148 Bcast:192.54.174.255 Mask:255.255.255.0
inet6 addr: fe80::baac:6fff:fe95:406b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20809 errors:0 dropped:0 overruns:0 frame:0
TX packets:834 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2586657 (2.4 MiB) TX bytes:91203 (89.0 KiB)

vmbr1 Link encap:Ethernet HWaddr b8:ac:6f:95:40:6d
inet addr:192.54.175.56 Bcast:192.54.175.255 Mask:255.255.255.0
inet6 addr: fe80::baac:6fff:fe95:406d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:8704 Metric:1
RX packets:20197 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2526503 (2.4 MiB) TX bytes:552 (552.0 B)

********************************************
sudo brctl show
bridge name bridge id STP enabled interfaces
vmbr0 8000.b8ac6f95406b no eth0
vmbr1 8000.b8ac6f95406d no eth1
***********************************************
tcpdump -i eth1 or vmbr1:
10:32:32.228272 IP 10.252.1.32.netbios-ns > 10.252.1.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
10:32:32.233308 arp who-has azurvo.oca.eu tell ocandns1.obs-nice.fr
10:32:32.350729 IP dhcp2-19.oca.eu.1900 > 239.255.255.250.1900: UDP, length 442
10:32:32.350996 IP6 fe80::2032:e35c:a1cc:b64d.1900 > ff02::c.1900: UDP, length 452
10:32:32.419685 IP zogotounga.oca.eu.0 > 225.0.0.225.9191: UDP, length 122
10:32:32.468235 IPX 00555555.00:01:e6:b3:b7:b8.0452 > 00555555.ff:ff:ff:ff:ff:ff.0452: ipx-sap-resp IntelNetport2/HP JetDirect/HP Quicksilver '0001E6B3B7B880DZNPIB3B7B8[|ipx 64]

etc...

****************

When I try to be connected of network 192.54.174.0 towards the proxmox waiter
(vmbr1 192.54.175.56) that doesn't work.
When I try to be connected of network 192.54.175.0 towards the proxmox waiter (vmbr1 192.54.175.56) this works correctly.
I say that on proxmox 1.5 this works.

Thanks for your help,
JM
 
mercier said:
Hi,

...
vmbr1 Link encap:Ethernet HWaddr b8:ac:6f:95:40:6d
inet addr:192.54.175.56 Bcast:192.54.175.255 Mask:255.255.255.0
inet6 addr: fe80::baac:6fff:fe95:406d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:8704 Metric:1
RX packets:20197 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2526503 (2.4 MiB) TX bytes:552 (552.0 B)
...

When I try to be connected of network 192.54.174.0 towards the proxmox waiter
(vmbr1 192.54.175.56) that doesn't work.
When I try to be connected of network 192.54.175.0 towards the proxmox waiter (vmbr1 192.54.175.56) this works correctly.
I say that on proxmox 1.5 this works.

Thanks for your help,
JM
Click to expand...
Hi,
arhh - there was an misunderstanding. In your first post you said, you can't use different bridges - now i would say bridges worked (traffic in both directions), only you can't get the pve-host-gui with the browser?! Is this the issue?

Look on the host, if you listen to all ips:
Code: 
netstat -an | grep -i listen
look on the host for routing:
Code: 
ip route
look for firewall-rules:
Code: 
iptables --list

Udo
 
Hi,

I would like to make acknowledge two networks (we have 3 classes C without vlan)
on the proxmoxserver. I cannot attain the server if I try a crossed connection it does not work.
(ok in proxmox 1.5)
netstat -an | grep -i listen
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:83 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:38619 0.0.0.0:* LISTEN
tcp 0 0 192.54.174.148:5666 0.0.0.0:* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::443 :::* LISTEN
**********************************************************************************
ip route
10.254.1.11 dev venet0 scope link
192.54.174.218 dev venet0 scope link
192.54.174.0/24 dev vmbr0 proto kernel scope link src 192.54.174.148
192.54.175.0/24 dev vmbr1 proto kernel scope link src 192.54.175.56
default via 192.54.174.250 dev vmbr0

**********************************************************************************
sudo /sbin/iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
 
You must log in or register to reply here.
Top Bottom