My Linux machine's all Ethernet ports are connected to Cisco 2960SCG switch. Linux machine is having two Ethernet cards. First one is using "e1000" Ethernet driver and the second one is with "nxge" Ethernet driver.
Problem is; I am successful while trying to delete VLAN interfaces over motherboard PCI Ethernet card, but if i try the same on other PCI card the following messages are coming,and soon system getting hanged.
Message from syslogd@ at Wed Feb 10 17:48:11 2010 ... localhost kernel: unregister_netdevice: waiting for eth5.390 to become free. Usage count = 4
Bofore using nxge based Ethernet card I used e1000 based only, for that also I had same problem.
I have configured dhcp3-server on my debian box and I'm wanting to offer dhcp on one of the vlan interfaces. The dhcp is functioning but when I test applying it to a different vlan, the original PC can still get an IP. For example: eth1 has vlan100 and vlan200. Our managed switch has the ports configured such the pc1 is on vlan100 and pc2 is on vlan2. This works fine and I can inter-route between vlans with static IPs. Our dhcp config is currently set as:
I'm preparing to "follow" these directions which will make VirtualBox's networking behave like VMWare's "NAT" networking. Of course, these instructions are for a Ubuntu/Debian setup.
I am quite certain that I can write a script that'll do the equivalent steps on my Fedora 11 box -- which is acceptable to me. I would, however, like to know how to splice this stuff into NetworkManager and/or /etc/sysconfig/networking/devices/, to do this the "right" way.
The desired networking behavior: -VM's get assigned addresses via DHCP on a virtual network -VM's can talk to each other and to their physical host -VM traffic out to the 'real world' is NATted
i have configured transparent squid with dansguardian for content filtering i used this squid server ip on client gateway(not on browser) for content filtering, is it possible that i could use this squid server in different VLAN.
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):
I just have installed FC 10 on a box that I will use as a router/firewall box. On the box I have three interfaces (eth0, eth0.704 (VLAN), and eth1). When the machine boots up, only eth0 and eth1 come up. If I run /etc/init.d/network restart, then eth0.704 will come up. If I add that command to rc.local, then all interfaces come up at boot.
I have the directive ONBOOT=yes in ifcfg-eth0.704. What would cause this vlan interface not to start at boot on the machine?
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 184.108.40.206) is the Gateway and the rest, that are calculated from the subnet mask, are assigned to servers(220.127.116.11 up to 18.104.22.168).
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 22.214.171.124 and assign the new IPs as usual. So I assigned to one of the CentOS 5 servers the IP 126.96.36.199 and set the gateway to 188.8.131.52. 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?
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
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?
Our ISP provides us with Layer 2 hardware (Modem?/Switch? (Hatteras)) for our leased line and internet access. I have been told that I should set up a VLAN capable router to separate the internet traffic from the internal traffic. I found that linux is capable of VLAN routing. Nice!
I have setup opensuse 10.3 put in two NICs and did the following vconfig add eth0 10 vconfig add eth0 20 ifconfig public.ip.add.ress netmask 255.255.255.252 eth0.10 up ifconfig 192.168.0.1 netmask 255.255.255.0 eth0.20 up
Plugged this NIC into the HATTERAS hardware (with a straight cable), and thought that this way I should be able to ping the public gateway or any ip out on the internet. My ISP is telling me that I should create a VLAN trunk to be able to 'use the internet', but as I understand in linux if I create any number of VLANs on one NIC they are already trunked. I also got the info, that the traffic is tagged, and I can separate the traffic reading the tags. I already read that some NICs are not able to VLAN because they are not able to handle the increased packet size.
Also that the MTU setting is important (dono' the exact value though, only that its important). I thought that a linux machine can act as a router and firewall in such a case, because proprietary switches/routers use linux as embedded os. This is my first meeting with VLAN so if this whole post does not make any sense or you think that I just need to RTFM more then tell me! I also have some (3) Dlink 3226 Layer2 switches around, but I think it would be waste to use a 24 port switch on this subject.
Upgraded a school network from FastEthernet to GigabitEthernet. Broke the network up into VLANs. Discovered that the router (Cisco 2821) could only route between the VLANs at around 400Mb/s. Tested out some layer three switches. They work very nicely, but are more than we need. So I started putting some spare equipment we had together as a Linux router.
Result: Underwhelmed. The machine has two Intel GigE interfaces. With the machine configured to route between two test VLANs I get about 855Mb/s with a single interface (all VLANs trunked over the single interface). That's about what I'd expect. Maybe a little low. With the two interfaces bonded, I get about the same.
For testing, I set up eight Windows machines, four on each VLAN. The Linux router is the only machine that can route between the two VLANs. I used Iperf to generate traffic and measure throughput between pairs of machines. Two machines on the same VLAN get about 300Mb/s between themselves. With the four machines organized into cross-VLAN pairs, I get about 855Mb/s total throughput on a single interface and very slightly more with two interfaces bonded.
The Linux router has an Intel Xeon E5506 CPU running at 2.13GHz and these are Intel GigE interfaces (built-in). I would expect to get a large boost by adding the second interface. I've confirmed that bonding is working (by pulling either of the cables and watching everything continue to function).
I am running RHEL 5.3 on a blade server w/ 2 NICs that are bonded. I have 2 VLANs that I am trying to configure. I have created the network-scripts ifcfg-bond0.<vlan#>. I can ping the device but the gateway won't ping. I am in console mode so cutting and pasting output doesn't work.
EDIT: I found a sample configuration, sadly without any comments, where there are defined some interfaces named vlan1:0 trough vlan1:3. Could that be the option I've been looking for.However in the definition of the vlan1 device it is configured with the subnetmask 255.0.0.0 . I would like to know the mechanics of that option, too.
2. In the wlan part of the network I want to have a dhcp server distributing ip addresses. However I want hosts the server 'knows' (by mac address) to be in a different vlan than those unknown. Is there any way to achieve that? If yes, do I need special wlan access points or can I do it by my configurable switch or by the server?
I'm having trouble getting Fedora 15 to work with my em/bond/br configuration as it did in Fedora 14. I've got a bonding interface over em1 and em2, and then individual bond vlans (bond0.2, bond0.10, etc...), I then have a similarly named bridge interface (br0.2, br0.10, etc...) for kvm. Regardless of if I assign bond0.2 or br0.2 the IP address, I am unable to ping the gateway, but the native untagged VLAN (bond0, br0) has no issue at all.
To try to isolate this issue down to the switch or Fedora 15, I went with a plain em setup and configured em1, and em1.2 which works as expected. This issue has been plaguing me since Fedora 15 came out and I'm about to trash it and go back to Fedora 14 (Which didn't have this issue), but some of the new kvm features have kept me trying to get over this incomprehensible hump.
I just setup a new LAMP server (CentOS 5.5 x86_64) box with channel bonding on NetXtreme II BCM5709 Gigabit Ethernet (IBM x3650 M3). The problem is I wasn't able to connect to this server when I'm in different VLAN's. This server also unable to ping different VLAN's. But everything works fine when I transact in the same VLAN.Here's the config:
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) DEVICE=eth0
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 have TWO L3 + router switch (say switch1 and switch2). I created VLAN100 with VLAN ID 100 in both the switches. I created router 192.168.1.1/24 in Switch1. I created router 192.168.2.1/24 in Switch2. Switch1 is connected with 1.x/24 PCs. PCs are configured with 1.1 gateway. Switch2 is connected with 2.x/24 PCs. PCs are configured with 2.1 gateway. Both Switch1 and switch2 are connected by a trunk to carry VLAN100 data.
1)I have few PCs of 1.x connected to say Switch1 Is it possible for PC with IP 192.168.1.100(x) to ping PC with IP 192.168.2.100(y)?What are the configuration required in both switches to make them communicate ? All the device in both the subnets should ping/communicate with each other.
2)Move PC (192.168.1.100) to switch2. Move PC (192.168.2.100)to switch1.What will happen when PC(1.100) ping (2.100) and vice versa?What will happen when PC(say 1.80 in switch1) pings PC (say 1.100 in switch2) and vice versa? What will happen when PC(say 1.80 in switch1) pings PC (say 2.100 in switch1) and vice versa?