<mirko>
`HOST_LDFLAGS += -Wl,-rpath,$(STAGING_DIR_HOSTPKG)/lib` helps, but how do other host tools handle this?
swalker has quit [Ping timeout: 480 seconds]
vincejv has quit [Remote host closed the connection]
Sawzall has quit [Remote host closed the connection]
Sawzall has joined #openwrt-devel
swalker has joined #openwrt-devel
Sawzall has quit [Read error: Connection reset by peer]
Sawzall has joined #openwrt-devel
valku has joined #openwrt-devel
Tapper has joined #openwrt-devel
Sawzallz has joined #openwrt-devel
guifipedro__ has joined #openwrt-devel
guifipedro_ has quit [Remote host closed the connection]
n3ph has quit [Read error: No route to host]
n3ph has joined #openwrt-devel
Sawzall has quit [Ping timeout: 480 seconds]
Sawzall has joined #openwrt-devel
Sawzallz has quit [Ping timeout: 480 seconds]
n3ph has quit [Read error: No route to host]
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
noltari has quit [Quit: Bye ~ Happy Hacking!]
noltari has joined #openwrt-devel
<f00b4r0>
nbd: dunno if you're the right person to ask: we're observing a super weird VLAN leakage on filogic devices (GL.inet MT6000 / ComFast E393AX): when either is used as a dumb AP with multiple VLANS setup on a single vlan-aware bridge, clients connecting the the SSID associated to e.g. VLAN 5 are also advertised as being members of VLAN 8 (this is visible in "bridge monitor" which shows the MAC being registered simultaneously in both VLANs)
<f00b4r0>
I don't have the slightest idea how to even begin to debug this. It doesn't affect ath79/ramips devices configured identically.