Bug #3089
opennebula 4.6: network mask not setup during contextualisation
Status: | Closed | Start date: | 07/23/2014 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | Javi Fontan | % Done: | 0% | |
Category: | Context | |||
Target version: | - | |||
Resolution: | worksforme | Pull request: | ||
Affected Versions: | OpenNebula 4.6 |
Description
Hello,
using opennebula 4.6.2, the netmask for additional interfaces is not setup correctly.
The netmask for eth0 is setup in /mnt/context.sh from the CONTEXT iso, but it is unset for all other devices.
Thus the scripts from one-context-4.6.0-1.noarch assume a netmask of /24, which in our case is wrong (we use /29, /24 and /22 netmasks).
It seems currently there is no way to find out the netmask within the VM.
[root@firewall-vm-02 ~]# grep -c ^ETH0 /mnt/context.sh 6 [root@firewall-vm-02 ~]# grep -c ^ETH1 /mnt/context.sh 0 [root@firewall-vm-02 ~]# ip l | grep 'eth.:' 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 [root@firewall-vm-02 ~]#
History
#1 Updated by Ruben S. Montero over 6 years ago
- Category set to Context
#2 Updated by Javi Fontan almost 6 years ago
- Status changed from Pending to Closed
- Assignee set to Javi Fontan
- Resolution set to worksforme
It works fine in my setup. NETWORK=YES
in the context section adds the information for all the interfaces.