Displaying 20 results from an estimated 1000 matches similar to: "[Bridge] Possibility of copying over fdb entries."
2007 Apr 18
2
[Bridge] new ioctl
Hi, all,
I am a newbie. i wish to add another ioctl into brctl for doing some
manipulations. How do i do so??
Please advise on the steps.
Regards,
Munro
2007 Apr 18
1
[Bridge] bridge stp problem
Hi, ppl,
I am using kernel 2.4.25 and having this peculiar problem on my
ixp425. When i have 2 ethernet ports of the board connected to the same
linksys switch running STP. ixp0 and ixp1 are the name of my ethernet
ports enslaved to the same bridge( br0)and my PC is also connected to
the switch.
IXP425 -br0 (192.168.2.1)
|_ixp0|--- |
2007 Apr 18
2
[Bridge] [RFC] bridge kernel API change
Here is the proposed revision to the bridge utilities
interface to the kernel. The driving force is that the
existing interface can't easily be converted to 32/64 bit
compat. Right now, the bridge-utils (brctl) tries to handle
32bit command on 64 bit kernel, but the code is limited to sparc
and wrong.
Here is what I am thinking.
get version - not needed?
get bridges -
2007 Apr 18
1
[Bridge] why ./brctl showmacs br0 display nothing?
hi:
my box use eth0 connect my pc. but I type command "./brctl showmacs br0", no mac addr display and the" brctl showmacs program" not exit,always exec
# ./brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000123456789 no eth0
hdlc0
# ./brctl showmacs br0
2009 Feb 24
3
Polycom Spectralink 8002 Configuration
I have a new Polycom Spectralink 8002 and am having trouble with the
configuration or the unit but I can't see what's wrong. The unit does
not seem to even attempt to register with the Asterisk proxy but I can
make calls to it. I have viewed the syslog from the device which it
will actually write to the asterisk server so I know it can be reached.
I have also run a sip debug and
2007 Apr 18
1
[Bridge] LAN-WAN Bridging Problem
Hello,
I am experiencing what may be a unique problem with operating the
bridge. My hardware is custom Freescale MPC875 processor based with one
ethernet (eth0) and one hdlc (hdlc0) WAN port and I am connecting two of
these boards together using the WAN ports over a long distance -
essentially two bridges in series. They are running Linux 2.6.15 with
bridging enabled in the kernel
2023 Apr 12
1
[Bridge] [PATCH net] net: bridge: switchdev: don't notify FDB entries with "master dynamic"
On Wed, Apr 12, 2023 at 07:00:02PM +0300, Ido Schimmel wrote:
> On Wed, Apr 12, 2023 at 05:27:33PM +0300, Vladimir Oltean wrote:
> > How are extern_learn FDB entries processed by spectrum's
> > SWITCHDEV_FDB_ADD_TO_DEVICE handler?
>
> No different than "BR_FDB_STATIC", which is a bug I'm aware of and
> intend to fix in net-next when I get the time
2023 Apr 12
1
[Bridge] [PATCH net] net: bridge: switchdev: don't notify FDB entries with "master dynamic"
On Wed, Apr 12, 2023 at 07:24:07PM +0300, Vladimir Oltean wrote:
> I'll send v2 with BR_FDB_ADDED_BY_EXT_LEARN not prevented from being
> notified from switchdev.
>
> Unless you have any objection, I won't send v2 like this:
>
> if (test_bit(BR_FDB_ADDED_BY_USER, &fdb->flags) &&
> !test_bit(BR_FDB_STATIC, &fdb->flags) &&
>
2023 Mar 20
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
On Sat, Mar 18, 2023 at 03:10:10PM +0100, Hans J. Schultz wrote:
> +# Test of dynamic FDB entries.
> +locked_port_dyn_fdb()
> +{
> + local mac=00:01:02:03:04:05
> + local ageing_time
> +
> + RET=0
> + ageing_time=$(bridge_ageing_time_get br0)
> + tc qdisc add dev $swp2 clsact
> + ip link set dev br0 type bridge ageing_time $LOW_AGEING_TIME
> + bridge link set dev
2023 Apr 12
1
[Bridge] [PATCH net] net: bridge: switchdev: don't notify FDB entries with "master dynamic"
On Wed, Apr 12, 2023 at 05:27:33PM +0300, Vladimir Oltean wrote:
> How are extern_learn FDB entries processed by spectrum's
> SWITCHDEV_FDB_ADD_TO_DEVICE handler?
No different than "BR_FDB_STATIC", which is a bug I'm aware of and
intend to fix in net-next when I get the time (together with all the
other combinations enabled by the bridge). Entry has ageing disabled,
but
2023 Mar 18
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
Test FDB ageing of user entry created by
bridge fdb replace ADDR dev <DEV> master dynamic
Use LOW_AGEING_TIME variable in forwarding.config to set a low ageing time.
Beware, DSA might not accept the ageing time you want. Check the
age_time_coeff value for your driver.
Signed-off-by: Hans J. Schultz <netdev at kapio-technology.com>
---
.../net/forwarding/bridge_locked_port.sh |
2023 Apr 12
1
[Bridge] [PATCH net] net: bridge: switchdev: don't notify FDB entries with "master dynamic"
On Wed, Apr 12, 2023 at 05:15:03PM +0300, Ido Schimmel wrote:
> > Looking at tools/testing/selftests/net/forwarding/, there is no valid
> > use of the "bridge fdb add ... master dynamic" command there, so I am
> > fairly confident that no one used to rely on this behavior.
>
> Yes, but there are tests that use "extern_learn". If you post a v2 that
>
2023 Apr 12
1
[Bridge] [PATCH net] net: bridge: switchdev: don't notify FDB entries with "master dynamic"
On Mon, Apr 10, 2023 at 11:49:51PM +0300, Vladimir Oltean wrote:
> There is a structural problem in switchdev, where the flag bits in
> struct switchdev_notifier_fdb_info (added_by_user, is_local etc) only
> represent a simplified / denatured view of what's in struct
> net_bridge_fdb_entry :: flags (BR_FDB_ADDED_BY_USER, BR_FDB_LOCAL etc).
> Each time we want to pass more
2023 Mar 26
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
On Mon, Mar 20, 2023 at 10:44, Ido Schimmel <idosch at nvidia.com> wrote:
>> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
>> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q
>> + tc_check_packets "dev $swp2 egress" 1 1
>> + check_fail $? "Dynamic FDB entry did not age out"
>
> Shouldn't this be check_err()? After
2013 Nov 18
0
[PATCH net] bridge: flush br's address entry in fdb when remove the bridge dev
When the following commands are executed:
brctl addbr br0
ifconfig br0 hw ether <addr>
rmmod bridge
The calltrace will occur:
[ 563.312114] device eth1 left promiscuous mode
[ 563.312188] br0: port 1(eth1) entered disabled state
[ 563.468190] kmem_cache_destroy bridge_fdb_cache: Slab cache still has objects
[ 563.468197] CPU: 6 PID: 6982 Comm: rmmod Tainted: G O
2023 Jun 19
1
[Bridge] [PATCH net-next v2 3/3] net: bridge: Add a configurable default FDB learning limit
This adds a Kconfig option to configure a default FDB learning limit
system wide, so a distributor building a special purpose kernel can
limit all created bridges by default.
The limit is only a soft default setting and overridable per bridge
using netlink.
Signed-off-by: Johannes Nixdorf <jnixdorf-oss at avm.de>
---
Changes since v1:
- Added a default limit in Kconfig. (deemed
2013 Nov 18
0
bridge: flush br's address entry in fdb when remove the bridge dev
When the following commands are executed:
brctl addbr br0
ifconfig br0 hw ether <addr>
rmmod bridge
The calltrace will occur:
[ 563.312114] device eth1 left promiscuous mode
[ 563.312188] br0: port 1(eth1) entered disabled state
[ 563.468190] kmem_cache_destroy bridge_fdb_cache: Slab cache still has objects
[ 563.468197] CPU: 6 PID: 6982 Comm: rmmod Tainted: G O
2004 Apr 20
8
[Bug 844] the client copy is over written during scp
http://bugzilla.mindrot.org/show_bug.cgi?id=844
Summary: the client copy is over written during scp
Product: Portable OpenSSH
Version: -current
Platform: Other
OS/Version: AIX
Status: NEW
Severity: trivial
Priority: P2
Component: scp
AssignedTo: openssh-bugs at mindrot.org
ReportedBy:
2023 Mar 28
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
On Tue, Mar 28, 2023 at 19:40, Ido Schimmel <idosch at nvidia.com> wrote:
> On Sun, Mar 26, 2023 at 05:41:06PM +0200, Hans Schultz wrote:
>> On Mon, Mar 20, 2023 at 10:44, Ido Schimmel <idosch at nvidia.com> wrote:
>> >> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
>> >> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q
>>
2023 May 15
3
[Bridge] [PATCH net-next 1/2] bridge: Add a limit on FDB entries
On 15/05/2023 11:50, Johannes Nixdorf wrote:
> A malicious actor behind one bridge port may spam the kernel with packets
> with a random source MAC address, each of which will create an FDB entry,
> each of which is a dynamic allocation in the kernel.
>
> There are roughly 2^48 different MAC addresses, further limited by the
> rhashtable they are stored in to 2^31. Each entry is