CentOS 5 Networking :: Create Multiple Virtual Adapter For VLAN'S
Jul 3, 2010
I need to set a NAC (PacketFence) system (CentOS 5.5), i would like to set in my case eth0 to work with several different VLAN'S i created ifcfg-eth0.2 copied from orginal ifcfg-eth0 and changed the ip and append VLAN=yes but when i am triyng to load ifcfg-eth0.2 i get error
my ifcfg-eth0 goes as follow
# Intel Corporation 82578DM Gigabit Network Connection
# Normal VLAN Lan adapter (Managment)(On-boad 1st NIC)
I need to set a NAC (PacketFence) system , i would like to set in my case eth0 to work with several different VLAN'S i created ifcfg-eth0.2 copied from orginal ifcfg-eth0 and changed the ip and append VLAN=yes but when i am triyng to load ifcfg-eth0.2 i get error
We have two recently installed centos machines, each running 5.5, and hosting an elastix pabx distro as well as a Virtual PC instance. On both machines, the network adaptor fails completely every week or so. As they are remote machines, the only option we have when this happens is a manual reboot.
I might be barking up the wrong tree here, but the only significant difference on these machines to others we have deployed is the Virtual PC instance. The machines have dual ethernet ports, with one assigned to the virtual PC. When the network failure occurs, it does not effect the virtual machine, which continues along merrily.
My expert colleague does not think so, but can anyone think of any way that our configuration could be causing the problem? If not, does anyone have any ideas on what the problem could be, or where I would start looking for information on the machine to debug the issue?
I'm trying to connect one computer to two others in an ad-hoc infrastructure.
[computer 1] ---- [computer 2] ---- [computer 3]
computer 2 is running Linux and has a single NIC wlan0. I want to it to connect to both computer 1 and computer 3 so each computer can talk to the other. No switch is available so it needs to be an ad-hoc setup.
Before going to vlan topic I have basic question. I have a gateway as 10.209.108.1/22 if I am connecting gateway to cisco 3750 switch port 1 can I use remaining ports to connect via above gateway? I mean suppose I am connecting NIC to port 2 and IP 10.209.111.200 can i ping 10.209.108.1? Is this valid without configuring any vlan or anything on switch?
I'm trying to setup a Asterisk box with two NIC's. The idea is that one NIC connects to the LAN on VLAN2 (for internal voice) and the other to the SIP trunk on my ISP's Cisco 1811, configured for VLAN3.
Some info: The Cisco's VLAN1 + 2 are available on my switch. VLAN1 = 10.105.44.x with gateway .254 (the Cisco). VLAN2 = 10.106.45.x with gateway .254 (the Cisco). The Cisco's VLAN3 is available on only a single port on de Cisco, connected to one of de NIC's of the Asterisk box, eth1, with IP 10.106.46.1 and gateway .254 (the Cisco). The other NIC, eth0, is connected to the switch, on a port setup for VLAN2.
So, what I'm trying to achieve: Use eth1 tagged with VLAN3 to connect to the SIP trunk. (I could do this with a static route because my provider has a fixed IP to connect to) Use eth0 for all other traffic.
Here are some config files I've setup so far (I'm stuck on connecting to the SIP provider):
My company hosts five Servers with CentOS 5 installed in a Data Center. The Data Center assigns a VLAN to each customer so that they can organize customers and also count traffic. The VLAN assigned to my company is in the form 62.103.X.X with a subnet mask 255.255.255.240 so the IPs that we can use in our Servers are 13. The first IP in the VLAN (for example 22.214.171.124) is the Gateway and the rest, that are calculated from the subnet mask, are assigned to servers(126.96.36.199 up to 188.8.131.52).
The problem I have is that we have run out of IPs in our VLAN. We have used all IPs and we want some more. The Data Center can assign new IPs but not grow our VLAN IPs by expanding the subnet mask. So they gave us a new VLAN with some IPs (for example 62.104.X.X with a subnet mask 255.255.255.192) They told me that I had to use as gateway the gateway of the first VLAN 184.108.40.206 and assign the new IPs as usual. So I assigned to one of the CentOS 5 servers the IP 220.127.116.11 and set the gateway to 18.104.22.168. Unfortunately this did not work and we could not establish connectivity to the Internet.Is it possible to assign a gateway outside of the IPs that are in the subnet? Could it be a problem with the VLAN setup by the Data Center?
Using Fedora 10, can anyone tell me how to setup the network scripts to create two network interfaces for vlan x and y. Both interfaces should obtain an ip from dhcp and both interfaces should run over eth0.
I am running 2.2.4 and CentOS 5.3 (RHEL 5.3 clone). I have two Ethernet cards: eth0 and eth1. Eth1 is connected to the Internet; eth0 is connected to all my virtual machines; iptables connects eth1 to eth0.
A new machine I am adding needs to be off eth0 and eth1 (security reasons). Question: is there a way to make up a third fake Ethernet card that I do not physically have (eth2) and assign it to my new VM? How do I do this? Can I get away with some thing like this?
I am trying to setup a VPN using OpenVPN to allow a secure connection between my smartphone and my LAN. I have been reading an OpenVPN book and some tutorials on how to setup the server side, but I'm stuck at how to create a virtual device. The OpenVPN book says when installing OpenVPN the installer (or aptitude to be more precise) should ask me if it should create a TAP/TUN device. The thing is, it doesn't ask me anything at all. It just installs, that's it.
Most tutorials simply tell me to create a new device in the network/interfaces file. Where is the difference? What should I do now? I like having options, that is one reason I like Linux, but this does confuse me. My second question is about the IP range of the virtual adapter. Should it be in the same range as my LAN, or should I use something entirely different?
I have spent considerable hours searching forums and googling. I have yet to find out what "lm-sensors acpitz-virtual-0 Adapter: Virtual device temp1:" is actually looking at. I have an Abit IP35 motherboard with Ubuntu 9.04 installed.
Here is the output from sensors:
Virtual Device Temp 1 keeps going up to 121 degrees and the computer shuts down. None of the others overheat. Also, my bios does not show my voltages to be set like it lists above. The bios in the motherboard is the latest from Abit.
I am newbie to centos. I am trying to install virtual server in my machine. I have installed the Xen virtual machine monitor which comes with CentOS through add/remove software. Here is the problem, I am unable to open connection with Xen hypervisor. Here is the error i am facing:
Unable to open a connection to the Xen hypervisor/daemon. code...
I had set up 4 virtual machines on centos 5.5 system where I directed the image locations to an external storage. I have lost the image files in the storage, but I have the image files that were copied from the virtual machine image location. I want to put up the same system on the same computer by copying these backup images. However, when I copy the image file to the same exact location and start the corresponding virtual machine I get "no bootable disk" error. When I increase the size of the image using "qemu-img" commands, I can get rid of this error, but get "error reading disk" error. Is there a way to overcome these problems, or is it not possible to restore a virtual machine by copying the machine image file under ..../xen/images?
I'm trying to set up a virtual machine environment in Centos5.5. My hardware fully supports virtualization, and I'm running qemu as the hypervisor with Virtual Machine Manager as the GUI to manage and create VMs. Host hardware is a Dell PowerEdge T710, with a quad core Xenon processor and four 1TB disks in a raid 6 array.
Within the Virtual Machine Manager when trying to create a new VM, there is the option to not "allocate entire virtual disk now". What format is created when you "allocate entire virtual disk now" and when you don't?
I want to create a qcow2 image format, but it doesn't look like it is supported. Does anybody know how to create a VM with a qcow2 image format?
When you create a blank disk with "qemu-img create -f qcow2 disk.qcow2 3700G", it indeed does create a qcow2 image. However, Virtual Machine Manager is unable to read these images, claiming that it is 15 megs or so in size (which is what it actually occupies in host disk space until you try and put a VM into it).
I have CentOS 5.5 and try to create KVM virtual machine with CentOS 5.5 as a guest. But when I exec command: virt-install --connect qemu:///system --name test --ram 1024 --file=/var/lib/libvirt/images/test.img --file-size=10 --vnc --cdrom=/var/lib/libvirt/images/CentOS-5.5-x86_64-bin-DVD-1of2.iso --vncport=10000 --accelerate --os-type=linux --nonsparse --livecd --hvm
I have a CentOS 5.3 box with three network interfaces in it. Each interface is attached to a separate VLAN and I want traffic to stay on each network segment.What I can�t figure out is why I cannot get each interface to have its own gateway and everything gets sent through the default gateway.The basically takes my possible 3Gb total bandwidth and throws it down a single 1Gb pipe.Then on top of that, if I take down the interface (ifdown) that has the current default gateway,I loose contact to the other two interfaces.When I look at the routes, each one of the interfaces shows the gw as 0.0.0.0 and defers to the default route. So I delete the route and try to add a new route with:
[root@testsan ~]# ip route add 10.1.15.0/24 via 10.1.15.1 dev eth2
I've been scanning the apache2 docs for the past few days and have not come up with an answer my following issue:
In my httpd.conf file, at the very end, I have the line
However, when I run apache checkconfig or try to start apache, it gives me the error:
httpd: Syntax error on line 993 of /etc/httpd/conf/httpd.conf: Could not open configuration file /etc/httpd/conf/vhosts/vhost_1.conf: Permission denied
It appears as if the Include line is correct - in terms of it grabbing the first virtual host conf file. However, I'm confused on the permissions. the /etc/httpd folder is owned by root:root, as are the subfolders. As a test, I chown'd the conf/vhost folder combination and all the vhost files to apache:apache to see if that made a difference, and it appeared to make no difference at all. The log files don't contain anything (assumed because apache isn't starting). If I place the contents of the vhosts in a singular vhosts.conf it works - with the permissions set to root:root. I'd like to avoid having to use one vhosts conf for the configuration I'm trying to achieve - as it would make my life a lot easier.
I would like to configure and SAN disk. But I do not have a physical SAN disk. Is it possible to create and configure a Virtual SAN disk and work on it with virtual machines?I have around 400GB of space in my Laptop.
There seems to be a lot written about virtual networking but I am not sure what approach to take in my situation. My local subnet has a public block of 128 addresses. I have a virtual host running on my machine. My machine has a static address and I'd need to assign one to the guest. I have edited the guest's interface file and assigned a public address to it's eth0. However the guest cannot ping out and I can't ping in.
By default the virtual machine manager creates a virtual network (virbr0) and assigned a private address range to it. I have tried to create a new virtual network using a subnet of my public range (/31) but the manager says the range must to a minimum of 16 addresses (/4). It doesn't look possible to achieve my aims using the virtual machine manager.
In the past I have used the procedure laid out here:[URL].. which is to manually create a bridge. I am not sure that is relevant for my 9.10. I think I would have to disable the network manager if I were to do that and I am not sure how to do that.