I think that it is alright if we solely depends on the wap_supplicant
for both open mesh and secured mesh.
Chun-Yeow
On Sat, May 7, 2016 at 1:16 AM, Daniel Golle <dan...@makrotopia.org> wrote:
> On Sat, May 07, 2016 at 01:01:30AM +0800, Yeoh Chun-Yeow wrote:
>> authsae and
authsae and wpa_supplicant only trigger if secured mesh.
wpa_supplicant should work correctly for VHT80 but don't think
authsae.
But this patch is intended to allow open mesh to support VHT80.
Thanks
Chun-Yeow
On Sat, May 7, 2016 at 12:53 AM, Daniel Golle wrote:
>
Could someone confirm if WDS and adhoc mode currently don't have support with
this driver?
adhoc is working but not perfect, such as rate control not working, no
HT/VHT rate, and etc. You need to use the firmware version
999.999.0.636.
WDS should be working since 4 addresses has fixed by
Hi, Shinoda
It could be due to old ath9k chipset filtering issue (broadcast packet
is filtered out, such as ARP request) as mentioned in:
https://github.com/cozybit/open80211s/wiki/ath9kFilteringIssueFix
So modify as follow in ath9k/recv.c and see how:
+ if
Hi, all
Anyone can comment on this? I have not seen any minstrel rate
statistic although this rate control algorithm is used for mac80211.
Regards,
Chun-Yeow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
This patch allows the possibility of having the mesh point and AP to be
operated
simultaneously in one single radio. Previously, mesh point fails to
generate the
mesh beacon if virtual AP is created for the same radio.
Signed-off-by: Chun-Yeow Yeoh yeohchuny...@gmail.com
---
Index:
Hi, all
This is mainly for ath5k.
Regards,
Chun-Yeow
On Sat, Mar 3, 2012 at 12:50 AM, Yeoh Chun-Yeow yeohchuny...@gmail.comwrote:
This patch allows the possibility of having the mesh point and AP to be
operated
simultaneously in one single radio. Previously, mesh point fails to
generate
Hi, Jonathan,
Yes.
Regards,
Chun-Yeow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Unfortunately, the driver that you provided not able to detect the switch
correctly ADM6996FC PHY detected.
I have observed the following:
eth0: Atheros AG71xx at 0xb900, irq 4*
eth0: PHY overlaps ADM6996, providing fixed PHY 14.*
eth0: connected to PHY at ag71xx-mdio:14 [uid=1027,
Hi, Peter,
Thanks for you explanation. I have learned some insights on how the PHY/MAC
works and MII.
FYI, the patch works. I have tested with following /etc/config/network to
send out the tagged packet:
config 'switch'
option 'name' 'eth1'
option 'reset' '1'
option
Dear Jonas,
After patching the patch, the messages Trying 100/FULL, Trying 10/HALF,
Trying 10/HALF disappear during startup. However, even the board is up
without Ethernet cable connecting to the LAN port 1 or port 0, the message
eth1: link up (100Mbps/Full duplex) is already printed there.
The
Yes, I am using the backfire version and will report my finding once I do
it.
On Fri, Apr 8, 2011 at 11:00 PM, Jonas Gorski
jonas.gorski+open...@gmail.com wrote:
On 6 April 2011 16:18, Yeoh Chun Yeow yeohchuny...@gmail.com wrote:
Hi, Jonas,
UBNT RS has two ports connected to eth1, port 0
So the two ports 0 and 1 are attached to the switch chip ports with those
numbers?
UBNT RS has three port. From the Left is LAN port 1, LAN port 0 and WAN
port.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
But it is a curious setup. Did you do it just to test the functionality?
Yes, mainly for testing purpose.
Good to hear a more usual setup does work. I assume this is with the patch
you
sent earlier?
Yes, using the patch I posted before.
In that case the common case where a port has
Hi, Peter
You have any clue which datasheet for FC chip should be referred to. For me,
it seems that it is not similar to F chip or not totally same with M chip.
Regards,
Chun Yeow
On Thu, Apr 7, 2011 at 10:54 PM, Peter Lebbing pe...@digitalbrains.comwrote:
It works as I described on the M
with Ethernet
cable, you will only see the message eth1: link up (100Mbps/Full duplex)
and the port 0 will function properly.
Do you know why?
Regards,
Chun Yeow
On Wed, Apr 6, 2011 at 7:40 PM, Jonas Gorski jonas.gorski+open...@gmail.com
wrote:
On 5 April 2011 08:52, Yeoh Chun Yeow yeohchuny...@gmail.com
Untagged packet receive by port 1 is drop. But VLAN 1 and VLAN 2 tagged
packet for port 0 is working perfertly.
config 'switch_vlan'
option 'device' 'eth1'
option 'vlan' '1'
option 'vid' '1'
option 'ports' '0t 1 5t'
config 'switch_vlan'
option 'device'
Hi, Peter and David,
I add the following patch and VLAN tagging working fine for UBNT RS:
--- ./target/linux/generic-2.6/files/drivers/net/phy/adm6996.c 2011-03-29
16:24:22.869595814 +0800
+++ ./build_dir/linux-ar71xx/linux-2.6.32.27/drivers/net/phy/adm6996.c
2011-04-04 18:32:14.188937710 +0800
Interesting find, thanks! Can the port still send *untagged* packets as
well, if
you configure untagged membership? When I wrote the driver, I think I
explicitly
chose not to set this bit, and it was unneeded for my M chip. Perhaps it
means
ALWAYS send tagged packets, but I would need to
Just to confirm adm6996fc is similar to adm6996m or adm6996f.
On Fri, Apr 1, 2011 at 5:34 PM, David Goodenough
david.goodeno...@linkchoose.co.uk wrote:
On Friday 01 April 2011, Peter Lebbing wrote:
On 01/04/11 03:27, Yeoh Chun Yeow wrote:
Ok I found the script.
read-all-adm output
/37 20:59, Yeoh Chun Yeow wrote:
It seems that ADM6996FC is different from ADM6996M. How to ensure the
port get tagged? Is this by simply modifying Configuration register Bit
4?
It's a lot more involved on the M model. A whole bunch of bits need to be
changed before it works as one would
David,
Can you send me the datasheet. Thanks
On Fri, Apr 1, 2011 at 5:34 PM, David Goodenough
david.goodeno...@linkchoose.co.uk wrote:
On Friday 01 April 2011, Peter Lebbing wrote:
On 01/04/11 03:27, Yeoh Chun Yeow wrote:
Ok I found the script.
read-all-adm output attach
It seems that ADM6996FC is different from ADM6996M. How to ensure the port
get tagged? Is this by simply modifying Configuration register Bit 4?
On Thu, Mar 31, 2011 at 3:27 PM, Yeoh Chun Yeow yeohchuny...@gmail.comwrote:
On Wed, Mar 30, 2011 at 10:52 PM, Yeoh Chun Yeow
yeohchuny
.
David
On Thursday 31 March 2011, Yeoh Chun Yeow wrote:
It seems that ADM6996FC is different from ADM6996M. How to ensure the
port
get tagged? Is this by simply modifying Configuration register Bit 4?
On Thu, Mar 31, 2011 at 3:27 PM, Yeoh Chun Yeow
yeohchuny...@gmail.comwrote
Please send me the script that you mentioned
I have run the following:
:~# swconfig dev eth1 vlan 2 set ports '0 1 2 3t 4t 5t'
:~# swconfig dev eth1 get addr
0
:~# swconfig dev eth1 get data
65535
dmesg
Infineon ADM6996 ag71xx-mdio:10: set_pvid port 0 vlan 2
Infineon ADM6996 ag71xx-mdio:10:
Dear all,
I am able to get the patch works by adding the following in mach-ubnt.c:
ar71xx_eth1_data.phy_mask = UBNT_RS_LAN_PHYMASK
However, there is two issues here:
1. RouterStation has two ports on ETH1. One port can only be activated after
the other port is connected with cable. If this port
Dear all,
Any one has tried the patch from Peter Lebbing on VLAN tag on UBNT
RouterStation platform and get it work properly.
Regards,
Chun Yeow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
27 matches
Mail list logo