similar to: [Bridge] ARP weirdness

Hi guys, Sorry if this is a little offtopic, but I was wandering what can one do to prevent/stop arp flooding ? Thanks, Alex -- This message has been scanned for viruses and dangerous content by LG-Network(http://www.lgnet.ro), and is believed to be clean.

Please bear with me as I know I have included a lot of detail. Description Redhat AS 3 Kernel 2.4.21-47.0.1.ELsmp eth0 HWaddr 00:07:E9:11:30:76 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 eth0:1 HWaddr 00:07:E9:11:30:76 inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0 This interface is up but with no IP address eth1

Hello list, I've posted here about this before, but I realise that it may have been assumed that the bridged vlans simply put a switch port in a blocking state and left my question ignored. So to recap. I have two tg3 interfaces named 'in' and 'out' and a bridge named 'br0' My vlan trunk is on the 'in' side of the network, and set as in.2, in.3 ... The

I have a question about bridges, vlans and switches. We had been using a bridge to provide filtering between our student labs and the main network. All the filtering does is check that a known IP matches a known MAC address, this stops students plugging in laptops and stealing an IP address. (And yes, we know about the MAC spoofing issues too) The connection was nice and simple,

Hi, The attached patches enables the bridge to filter and forward packets according to their IEEE 802.1q headers. The goals behind this change include : - Enable running STP on 802.1q tagged networks. STP packets must be untagged. It isn't obvious how else to enable STP with the current bridge and vlan code. - Add native support for an untagged vlan. Currently an untagged vlan can

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

Thank you everyone. OK, the mystery deepens, I guess. The machine does need to support several VLAN's, it is currently on a trunkport (8021q encapsulated), it made it into the ARP table - which I specifically tested for by physically unplugging the table, clearing the ARP table and plugging it back in. The ARP table currently looks like this: hq#show arp Protocol Address Age (min)

<I apologize if this arrives twice... I sent it first from an non-subscribed address, don't know if that'll get to the list or not --JJ> Hi folks, I have an implementation question regarding bridging on a linux box between a catalyst trunk port and a cisco 26something w/802.1q subinterfaces. So right now, there's no vlan trunking going on on the link my bridging firewall sits

Hello You must add first: vlan (tagged) to eth2 eth2 interface is not tagged by default and not know vlan-s . It is like a cisco if you have 24 ports in cisco by default all ports are in vlan1. if you want to do trunk (with vlans) you myst add (vlans) to this ports (tagged or untagged) So you can compare that all interfaces in linux by default are in one vlan(but not tagged). (only for

Hello, I am creating a configuration where a Redhat server running bridge-tools 0.9.5 will be bridging between different VLANs on the same physical interface (for example: a bridge consisting of eth1.100 and eth1.110). This physical interface is being connected to modern Cisco switches running PVST+. The Cisco switch does not like this configuration as the tags on its BPDUs are being changed

-----Original Message----- >From: Tommy Christensen [mailto:tommy.christensen@tpack.net] >Sent: Wednesday, October 08, 2003 10:09 AM >To: Christian Darnell >Cc: 'Linux 802.1Q VLAN'; Bart De Schuymer; netdev@oss.sgi.com; bridge >Subject: Re: [Bridge] RE: [VLAN] Re: [PATCH/RFC] Let {ip, arp}tables >"see" bridged VLAN tagged{I,AR}P packets > > > >This

> Use an Intel pro/100 or pro/1000 driver..they are known to > work with VLANs. > > I guess it's also possible that it's a problem in the > bridging code, so try the latest kernel > as well... I compiled the latest 2.6.19 kernel and tested it with two 3COM 3c905c fast ethernet interfaces which work fine with vlan 802.1q tagging, but when I have added the eth0 and eth1

Hi List, I'm trying to configure two switches to provide redundancy (i.e. in case one switch goes down), and am wondering if there is a standard way to configure a CentOS box to use different gateways in a bonded interface, depending upon which physical nic is being used? A bit more detail might help answer the "And why do you want to do that?" questions... - Switch 1,

Hello all, I need a virtual firewall/router solution. I''m thinking of a netscreen 1000 but I want to know if it can be done in Linux. Here is my idea: 1 Linux box 2 GigE interfaces 1 interface setup with a public IP address ($PUBIP) 1 interface setup with 802.1q VLAN trunking with 100 vlans assigned ($VLAN1-$VLAN100) a /25 subnet routed to $PUBIP from my core routers All $VLAN

I have 3 machines, T60 thinkpad with e1000 NIC Dell PowerEdge 2950 with bnx2 NIC HP DL360 G4P with tg3 NIC All running xen 3.03 / 2.6.16.29-xen I have a netbootable image with 2.6.16.29-xenU. This image when it boots creates a vlan eth0.4002, and then tries to communicate on that interface to a central server. On the machines with e1000 an bnx2 NICs, this works fine. On the

I am running KVM guests under Redhat 6. I tried to setup a bridge device to an interface with a vlan trunk connected to a Juniper switch. On the KVM host, I am able to define vlans and access them via the vlan trunk. I was not able to access a vlan from the kvm guest connected to the bridged interface. I believe this would be what is commonly called QinQ or 802.1ad. Is this possible to do? I

I''m using bonding in active-fallback mode to guarantee maximum availability on some critical servers. The mii mode is active so I can detect things like dead card and/or unplugged cable even on the inactive slave. But how do I check that the inactive slave is properly configured/connected to the switch/vlan? I ask this question because it has just bitten me in a part I''ll keep

Hi, I want to add 2 vlans by the following steps: 1. add the vlan interfaces: vconfig add eth0 100 --vlan100 vconfig add eth0 101 --vlan101 2. modify the network-bridge script by the websit, http://wiki.xensource.com/xenwiki/XenNetworking#head-04ebcc1760dbc4678e83b116afa310dc0612dc39 Comment each time ifup or ifdown commands are executed.The reason is that ifdown ends with

Hi all, The patch below does four trivial changes and one big change Trivial changes, these are all in br_netfilter.c: - check ar_pln==4 when giving bridged ARP packets to arptables - delete unnecessary if in br_nf_local_in - add more logging for the "Argh" message - add some brag-comments in the file head comment Big change: let {ip,arp}tables see VLAN tagged {I,AR}P packets. This