Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sun May 28, 2017 7:15 Post subject: Re: client bridge mode
franksddwrt wrote:
I purchased a pair of 3200s a month ago to replace a pair of wrt54g I am using as a wireless bridge. The 'official' dd-wrt firmware did function in bridge mode, but suffered from the long list of serious issues in this thread, with the lockups after only a few hours or minutes being the showstopper for me. I've been trying BS's builds, which by now seem to have solved all the serious issues for me on the access point side (range, SSID disappearing, clients connecting put not able to pass traffic, bandwidth decreasing over time), but I haven't been able to get one working in bridge mode in weeks. I know BS is still working hard on various issues (and I deeply appreciate the efforts of him and other contributors), so I'm just patiently waiting for bridge mode to make it to the top of the list, as I doubt there are a lot of people using it in that mode.
as mentioned earlier already. the current marvell driver still does not work in client mode, wds or whatever you may like. that sucks yes. they wrote that they are working on in, but nobody knows when its done. the older driver which we used up to march does support client mode and wds sta (do never use client bridge if you can use wds ap and wds sta, its simply faster and is a real bridge unlike client bridge)
the problem is just the older driver sucks at all and is totally unstable on the wrt3200acm _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sun May 28, 2017 13:02 Post subject:
hw nat isnt implemented. i also dont know if its available. but hw nat will also prevent filtering and custom qos. but however the cpu is that fucking fast that you dont need to take care about it. you can do nat with full gbit speed _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
hw nat isnt implemented. i also dont know if its available. but hw nat will also prevent filtering and custom qos. but however the cpu is that fucking fast that you dont need to take care about it. you can do nat with full gbit speed
Joined: 18 Aug 2009 Posts: 597 Location: Antigua/Seattle
Posted: Sun May 28, 2017 16:08 Post subject: Re: Client mode is working
emorlet1803 wrote:
For me, client mode is working starting from this version.
So you're essentially saying this isn't true?
Quote:
as mentioned earlier already. the current marvell driver still does not work in client mode, wds or whatever you may like. that sucks yes. they wrote that they are working on in, but nobody knows when its done. the older driver which we used up to march does support client mode and wds sta (do never use client bridge if you can use wds ap and wds sta, its simply faster and is a real bridge unlike client bridge)
the problem is just the older driver sucks at all and is totally unstable on the wrt3200acm
I Really doubt you have Client Mode working or else you discovered something BS didn't know? not very likely.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sun May 28, 2017 16:25 Post subject:
indeed. if its now working its a hidden update in the new marvell driver _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Still having guest ath1.1 connection issues on the 2.4 band. Some devieces connect to ath1.1 fine, others do not. Devices can connect on ath1 while ath1.1 is up, so that's good. The guest settings on ath1.1 are mirrored from my WRT1900ACS, so they should be correct.
Still having guest ath1.1 connection issues on the 2.4 band. Some devieces connect to ath1.1 fine, others do not. Devices can connect on ath1 while ath1.1 is up, so that's good. The guest settings on ath1.1 are mirrored from my WRT1900ACS, so they should be correct.
I'll play with it tomorrow and see what I can do.
I was having problems getting devices to connect to my 2.4 after four other devices connected to my ath1.1 (have some smart home devices connecting to guest on a regular basis but still need the 2.4 range at home for my network devices). Like for you, the update fixed this problem. I did have to put my 2.4 settings to BG Mixed and Full 20 MHz and select a channel to get everything connecting consistently, however. It's no serious loss to me because I connect to 5 GHz of most of my networking. I hope this helps. _________________ WRT3200ACM x2 presently running LEDE.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 29, 2017 7:26 Post subject:
aairon wrote:
BrainSlayer wrote:
indeed. if its now working its a hidden update in the new marvell driver
I didn't know that was possible.
sure its possible. the new driver has some driver enhancements which covers the multiple ssid issue, but there was also a new firmware introduced. nobody knows whats changed inside _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 29, 2017 7:28 Post subject:
Dexterity06 wrote:
Dunkelstar wrote:
Installed r32149 yesterday.
Still having guest ath1.1 connection issues on the 2.4 band. Some devieces connect to ath1.1 fine, others do not. Devices can connect on ath1 while ath1.1 is up, so that's good. The guest settings on ath1.1 are mirrored from my WRT1900ACS, so they should be correct.
I'll play with it tomorrow and see what I can do.
I was having problems getting devices to connect to my 2.4 after four other devices connected to my ath1.1 (have some smart home devices connecting to guest on a regular basis but still need the 2.4 range at home for my network devices). Like for you, the update fixed this problem. I did have to put my 2.4 settings to BG Mixed and Full 20 MHz and select a channel to get everything connecting consistently, however. It's no serious loss to me because I connect to 5 GHz of most of my networking. I hope this helps.
i hope wmm was enabled on 2.4. normally there shouldnt be a issue with 2.4. both chipsets are using the same driver and firmware _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s