similar to: [Bridge] Lost TCP packet

Displaying 20 results from an estimated 400 matches similar to: "[Bridge] Lost TCP packet"

2007 Apr 18
1
[Bridge] Information needed about bridge c code
Hello, i need to write a little personal patch in the bridge code. For this patch, i need to know the original src and dst mac addresses of the packet incoming to the bridge. As i work on a brouter (some packets are bridged, some are routed based on ebtable rules), packets that are routed have their mac addresses modified by the IP stack). I put a software probe in br_input.c::br_handle_frame( ),
2013 Aug 26
0
[PATCH] bridge: separate querier and query timer into IGMP/IPv4 and MLD/IPv6 ones
Currently we would still potentially suffer multicast packet loss if there is just either an IGMP or an MLD querier: For the former case, we would possibly drop IPv6 multicast packets, for the latter IPv4 ones. This is because we are currently assuming that if either an IGMP or MLD querier is present that the other one is present, too. This patch makes the behaviour and fix added in "bridge:
2007 Jun 12
3
ip_conntrack table filling up, dropping packets
Hi, my ip_conntrack table is filling up and now my server is dropping packets. I'm running CentOS release 4.4 (Final) on a fairly busy webserver. The table is full of various connections, including a lot of "ESTABLISHED" tcp connections from my webserver (the src is my webserver ip), and some other random connections to my webserver, and many "ASSURED" connections. So why
2007 Apr 18
5
[Bridge] RFC: [PATCH] bridge vlan integration
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
2003 Jun 01
1
Very weird network behaviour with 4.7-RELEASE-p10 (large)
Hi, I have been doing some tests using hping2 and TCP SYN pings targeting local and remote hosts from two FreeBSD 4.7-RELEASE-p10 and one Linux 2.4.18 host. The three machines have the same hardware configuration and have been running for 6 months now. The average load isnt too high (usually 0.01 to 0.15) on the FreeBSD machines. Here is the output from hping2 (excuse me the line wrap),
2013 Apr 30
6
[Bridge] [PATCHv4 net-next 0/2] Add two new flags to bridge.
The following series adds 2 new flags to bridge. One flag allows the user to control whether mac learning is performed on the interface or not. By default mac learning is on. The other flag allows the user to control whether unicast traffic is flooded (send without an fdb) to a given unicast port. Default is on. Changes since v4: - Implemented Stephen's suggestions. Changes since v2: -
2009 Aug 13
4
[Bridge] [PATCH] net/bridge: Add 'hairpin' port forwarding mode
This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge kernel module. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA
2009 Aug 13
4
[Bridge] [PATCH] net/bridge: Add 'hairpin' port forwarding mode
This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge kernel module. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA
2009 Aug 13
4
[Bridge] [PATCH] net/bridge: Add 'hairpin' port forwarding mode
This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge kernel module. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA
2006 Aug 29
0
Daily Xen-HVM Build Testing: cs11278
changeset: 11278:8273f730371b tag: tip user: Ian Campbell <ian.campbell@xensource.com> date: Tue Aug 29 06:23:11 2006 +0100 summary: Fix definition of LINUX_VER so that doesn''t pickup LINUX_VER3 Hardware: x460 ******************** x86_32(no PAE): *************************** * dom0: SLES10 GM * dom0 boots fine * xend starts without problem --- Linux
2006 Aug 03
1
Daily Xen-HVM Build Testing: cs10910
changeset: 10910:aa1ab056bfbf tag: tip user: emellor@leeni.uk.xensource.com date: Wed Aug 2 11:42:38 2006 +0100 summary: Clarify the use of vcpu-set. Closes bug #686. Hardware: x460 ******************** x86_32(no PAE): *************************** * dom0: SLES9 SP2 * dom0 boots fine * xend starts without problem --- Linux HVM domain status: --- * Xm-test
2003 Oct 18
1
MORE ON : [htb] strange problems !?
hello again, I got some just preliminary results .... hope someone can explain them to me... As I already told I have the following config : egress { class (30kbps) {sfq}; class (50kbps) {sfq}; class (80kbps) {sfq}; class (30kbps) {sfq}; class (50kbps) {sfq}; ...hundreds like this... class (10kbps,default) {sfq}; } What I got is traffic starvation very often for a period of ~30 sec.. as
2006 Feb 01
6
[XM-TEST][PATCH] hvm network test fixes
The following patch allows the network tests to pass with hvm support enabled. More specifically: 02_network_local_ping_pos.py REASON: ping loopback failed for size 65507. ping eth0 failed for size 65507. (but all other size pings work) 05_network_dom0_ping_pos.py REASON: Ping to dom0 failed for size 65507. (but all other size pings work) 11_network_domU_ping_pos.py passes 100% (even the large
2005 Jun 01
4
Firewall stress test
Hi all, We want to do some stress testing of firewall configurations/hardware. We have discovered hping that seems a great tool for this, but funny enough Shorewall cuts it !!! even when you leave ports open :) So besides hping, any tool for this? Why is shorewall cutting this traffic? Thanks in advance. Regards. -- Jaime Nebrera - jnebrera@eneotecnologia.com Consultor TI - ENEO
2007 Apr 18
0
[Bridge] [PATCH] Fix deadlock in br_stp_disable_bridge
Looks like somebody forgot to use the _bh spin_lock variant. We ran into a deadlock where br->hello_timer expired while br_stp_disable_br() walked br->port_list. Anush can provide you with a test program. Patch against 2.6.16-rc3 inlined. diff -rup linux-2.6.16-rc3/net/bridge/br_stp_if.c linux-2.6.16-rc3-brfix/net/bridge/br_stp_if.c --- linux-2.6.16-rc3/net/bridge/br_stp_if.c
2007 Apr 18
0
[Bridge] [PATCH] Fix deadlock in br_stp_disable_bridge (2nd try)
Looks like somebody forgot to use the _bh spin_lock variant. We ran into a deadlock where br->hello_timer expired while br_stp_disable_br() walked br->port_list. Anush can provide you with a test program. Patch against 2.6.16-rc3 inlined. Signed-off-by: Adrian Drzewiecki diff -rup linux-2.6.16-rc3/net/bridge/br_stp_if.c linux-2.6.16-rc3-brfix/net/bridge/br_stp_if.c ---
2007 Apr 18
0
[Bridge] bug(?) in br_device_event causes kernel panic for 2.6.14
Hi there- I think I have a bug to report :-( I'm trying to setup up a bridge for use with OpenVPN on my Gentoo box- resulting in a lot of fiddling and creating/destroying bridges (mostly to do with me getting things right in gentoos network config scripts.) What I've noticed is that when I create br0, and try and add eth0, it says it's already part of a bridge (it isn't - no
2007 Aug 23
3
[Bridge] bridge problem when one interface is in blocking mode
Hi, We have a simple bridge setup but the ping (and other network traffic) does not work reliably. After tracing the code, it looks like a software bug. Since bridge software is been running by thousands of people. I guess I am wrong. Anyway, here is the problem. There are 2 boxes and each one has 2 interfaces, 1 ethernet and 1 wifi. STP is enabled for the bridge to avoid the loop. So the box 1
2007 Nov 27
1
[PATCH][BRIDGE] Properly dereference the br_should_route_hook
This hook is protected with the RCU, so simple if (br_should_route_hook) br_should_route_hook(...) is not enough on some architectures. Use the rcu_dereference/rcu_assign_pointer in this case. Signed-off-by: Pavel Emelyanov <xemul@openvz.org> --- diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c index 3cedd4e..b42b192 100644 --- a/net/bridge/br_input.c +++
2007 Apr 18
1
[Bridge] Problem of lock when deleting a bridge
When i want to delete my test bridge, using: ifconfig eth0 down ifconfig eth1 down ifconfig br0 down brctl delif br0 eth0 brctl delif br0 eth1 brctl delbr br0 i get this error message from the kernel on the console: unregister_netdevice: waiting for br0 to become free. Usage count =3D 2 The brctl user-level command is blocked. Could you explain me what could likely be the cause of this error?