(TP-Link WDR4300) Setting up for Client Bridge

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 18:11    Post subject: Reply with quote
the dmesg looks fine, that time could of been on the server side. default gw mode use what u need, probably depends on the host if it is able to successfully pass down the gw info to the bridge (assuming the gw is the host itself aka using the host internal ip). vap is not required unless u need it, if u only do client bridge with ethernet clients connected to the bridge, dont need vap. i updated it to be more clear
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

Sponsor
TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 20:02    Post subject: Reply with quote
Well damn, perhaps I didn't run the dmesg soon enough or something. Do I need to have any particular settings on my computer itself? Things like the "adapter settings" or anything?

EDIT: When looking through Asus settings again I found this.



The router's LAN IP is 192.168.1.1, which is what I've been setting things like the gateway on the bridge too. However it seems that it has a different WAN IP? Going to be testing around with this but which IP should I be using as the gateway and such?
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 20:19    Post subject: Reply with quote
adapter settings dont need changing. the asus has such an ip cause ur isp device isnt in bridge mode if it offers it, if it doesnt then put the ip of the asus in the dmz (make it static first so the asus always gets the 192.168.0.6). gw on the bridge should stay as the asus ip 192.168.1.1 as its still having to connect to it anyway to reach the isp device (but can try changing it if u want just cause)
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 20:47    Post subject: Reply with quote
So in the DMZ of the Bridge put in 192.168.1.1, or 192.168.0.6 after I've made that IP static on the Asus router?
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 20:50    Post subject: Reply with quote
no on the isp modem, put asus ip 192.168.0.6 in static list & dmz if possible, on asus router do nothing for now, on the tplink bridge leave gw mode as 192.168.1.1
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 21:00    Post subject: Reply with quote
Oh so there's a configuration page or something for my modem? How would I access that. I don't really know much about the modem other than that it's Motorola and our ISP is Bright House Networks.
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 21:03    Post subject: Reply with quote
its a modem/router combo or something with nat or the asus wouldnt have a 192.168.x.x wan ip, id assume it should be 192.168.0.1 or 192.168.0.100 or 192.168.0.254
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 21:39    Post subject: Reply with quote
Ahh okie, just got into it.



Would this be what I'm looking for? What does DMZ even do?
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 21:47    Post subject: Reply with quote
open all ports/completely turns off firewall to selected device, as close to bridge mode on the isp modem as ull get if it doesnt support the feature (some isps u have to call it in & its done remotely by isp, such as mine)
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 22:18    Post subject: Reply with quote
So you're saying that setting DMZ does all of that, or that I need to do all of that? Sorry hard to make you out Razz.

Also I don't see something like a static list? Should I just make the WAN IP static on my Asus router?
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 22:32    Post subject: Reply with quote
dmz does that automatically after enabling it for the selected ip. as in changing the asus from dhcp to static? can try that so it keeps requesting the same ip from the isp modem. after putting the asus wan ip 192.168.0.6 into the isp modem dmz check again for the hanging/lag issue
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 22:57    Post subject: Reply with quote


Alright trying to set the WAN IP to static.What should I set the subnet mask and Gateway to? [/list]
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Thu Oct 30, 2014 23:08    Post subject: Reply with quote
subnet probably as it is now, gateway is the ip of the isp modem, 192.168.0.1 ot whatever ip brings up its config page
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

TooMuchStarbucks
DD-WRT Novice


Joined: 27 Oct 2014
Posts: 20

PostPosted: Thu Oct 30, 2014 23:29    Post subject: Reply with quote
Unfortunately that seemed to not have worked.I set my router to a static IP of 192.168.0.2, turned off DCHP for the modem (wasn't really working with it on anyway), and set the DMZ Address to that IP, still get drops.

I'm not looking at the task manager and, well this is interesting.



Just shows how inconsistent the connection is hah.

Also found something on the modem config page.



Would this be what you're talking about the trying to set it to bridging or something?

Here's the newest dmesg log.

Quote:
<6>[29588.000000] device eth0 left promiscuous mode
<6>[29588.000000] br0: port 2(vlan2) entered disabled state
<6>[29588.110000] ath1: deauthenticating from 74:d0:2b:43:13:34 by local choice (Reason: 3=DEAUTH_LEAVING)
<6>[29588.340000] device br0 entered promiscuous mode
<6>[29588.430000] device vlan1 entered promiscuous mode
<6>[29588.440000] device eth0 entered promiscuous mode
<6>[29588.490000] device vlan2 entered promiscuous mode
<6>[29588.500000] br0: port 2(vlan2) entered forwarding state
<6>[29588.500000] br0: port 2(vlan2) entered forwarding state
<6>[29588.510000] br0: port 1(vlan1) entered forwarding state
<6>[29588.510000] br0: port 1(vlan1) entered forwarding state
<6>[29588.520000] device br0 left promiscuous mode
<6>[29588.530000] device br0 entered promiscuous mode
<6>[29588.590000] cfg80211: Calling CRDA to update world regulatory domain
<3>[29588.620000] cfg80211: Invalid regulatory domain detected:
<6>[29588.630000] cfg80211: Regulatory domain: 00
<6>[29588.630000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29588.640000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.650000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.660000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.670000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.680000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.690000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29588.700000] cfg80211: Calling CRDA to update world regulatory domain
<6>[29588.720000] cfg80211: World regulatory domain updated:
<6>[29588.730000] cfg80211: DFS Master region: unset
<6>[29588.730000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29588.740000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.750000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.760000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.770000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.780000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29588.780000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29588.800000] cfg80211: Calling CRDA for country: US
<6>[29588.800000] cfg80211: Regulatory domain changed to country: US
<6>[29588.810000] cfg80211: DFS Master region: FCC
<6>[29588.810000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29588.820000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29588.830000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
<6>[29588.840000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (N/A)
<6>[29588.850000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29588.850000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
<6>[29589.470000] device br0 left promiscuous mode
<6>[29590.290000] ath1: authenticate with 74:d0:2b:43:13:34
<6>[29590.300000] ath1: send auth to 74:d0:2b:43:13:34 (try 1/3)
<6>[29590.310000] ath1: authenticated
<6>[29590.320000] ath1: associate with 74:d0:2b:43:13:34 (try 1/3)
<6>[29590.320000] ath1: RX AssocResp from 74:d0:2b:43:13:34 (capab=0x11 status=0 aid=4)
<6>[29590.330000] ath1: associated
<6>[29603.520000] br0: port 2(vlan2) entered forwarding state
<6>[29603.520000] br0: port 1(vlan1) entered forwarding state
<6>[29607.510000] device vlan1 left promiscuous mode
<6>[29607.520000] br0: port 1(vlan1) entered disabled state
<6>[29607.550000] device vlan2 left promiscuous mode
<6>[29607.550000] device eth0 left promiscuous mode
<6>[29607.550000] br0: port 2(vlan2) entered disabled state
<6>[29607.910000] ath1: deauthenticating from 74:d0:2b:43:13:34 by local choice (Reason: 3=DEAUTH_LEAVING)
<6>[29607.980000] device br0 entered promiscuous mode
<6>[29608.080000] device vlan1 entered promiscuous mode
<6>[29608.080000] device eth0 entered promiscuous mode
<6>[29608.130000] device vlan2 entered promiscuous mode
<6>[29608.140000] br0: port 2(vlan2) entered forwarding state
<6>[29608.150000] br0: port 2(vlan2) entered forwarding state
<6>[29608.150000] br0: port 1(vlan1) entered forwarding state
<6>[29608.160000] br0: port 1(vlan1) entered forwarding state
<6>[29608.160000] device br0 left promiscuous mode
<6>[29608.170000] device br0 entered promiscuous mode
<6>[29608.220000] cfg80211: Calling CRDA to update world regulatory domain
<3>[29608.250000] cfg80211: Invalid regulatory domain detected:
<6>[29608.250000] cfg80211: Regulatory domain: 00
<6>[29608.250000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29608.260000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.270000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.280000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.290000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.300000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.310000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29608.320000] cfg80211: Calling CRDA to update world regulatory domain
<6>[29608.340000] cfg80211: World regulatory domain updated:
<6>[29608.340000] cfg80211: DFS Master region: unset
<6>[29608.350000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29608.360000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.370000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.370000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.380000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.390000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29608.400000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29608.450000] cfg80211: Calling CRDA for country: US
<6>[29608.450000] cfg80211: Regulatory domain changed to country: US
<6>[29608.460000] cfg80211: DFS Master region: FCC
<6>[29608.470000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29608.480000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29608.480000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
<6>[29608.490000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (N/A)
<6>[29608.500000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29608.510000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
<6>[29609.300000] device br0 left promiscuous mode
<6>[29610.130000] ath1: authenticate with 74:d0:2b:43:13:34
<6>[29610.140000] ath1: send auth to 74:d0:2b:43:13:34 (try 1/3)
<6>[29610.150000] ath1: authenticated
<6>[29610.170000] ath1: associate with 74:d0:2b:43:13:34 (try 1/3)
<6>[29610.170000] ath1: RX AssocResp from 74:d0:2b:43:13:34 (capab=0x11 status=0 aid=4)
<6>[29610.180000] ath1: associated
<6>[29623.200000] br0: port 2(vlan2) entered forwarding state
<6>[29623.200000] br0: port 1(vlan1) entered forwarding state
<6>[29623.660000] br0: port 2(vlan2) entered disabled state
<6>[29623.660000] br0: port 1(vlan1) entered disabled state
<6>[29623.770000] device vlan1 left promiscuous mode
<6>[29623.780000] br0: port 1(vlan1) entered disabled state
<6>[29623.790000] device vlan2 left promiscuous mode
<6>[29623.790000] device eth0 left promiscuous mode
<6>[29623.800000] br0: port 2(vlan2) entered disabled state
<6>[29623.890000] ath1: deauthenticating from 74:d0:2b:43:13:34 by local choice (Reason: 3=DEAUTH_LEAVING)
<6>[29624.080000] device br0 entered promiscuous mode
<6>[29624.190000] device vlan1 entered promiscuous mode
<6>[29624.190000] device eth0 entered promiscuous mode
<6>[29624.240000] device vlan2 entered promiscuous mode
<6>[29624.250000] br0: port 2(vlan2) entered forwarding state
<6>[29624.260000] br0: port 2(vlan2) entered forwarding state
<6>[29624.260000] br0: port 1(vlan1) entered forwarding state
<6>[29624.270000] br0: port 1(vlan1) entered forwarding state
<6>[29624.270000] device br0 left promiscuous mode
<6>[29624.280000] device br0 entered promiscuous mode
<6>[29624.390000] cfg80211: Calling CRDA to update world regulatory domain
<3>[29624.390000] cfg80211: Invalid regulatory domain detected:
<6>[29624.400000] cfg80211: Regulatory domain: 00
<6>[29624.400000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29624.410000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.420000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.430000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.440000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.440000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.450000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29624.500000] cfg80211: Calling CRDA to update world regulatory domain
<6>[29624.520000] cfg80211: World regulatory domain updated:
<6>[29624.530000] cfg80211: DFS Master region: unset
<6>[29624.530000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29624.540000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.550000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.560000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.570000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.580000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29624.580000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29624.600000] cfg80211: Calling CRDA for country: US
<6>[29624.600000] cfg80211: Regulatory domain changed to country: US
<6>[29624.610000] cfg80211: DFS Master region: FCC
<6>[29624.610000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29624.620000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29624.630000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
<6>[29624.640000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (N/A)
<6>[29624.650000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29624.650000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
<6>[29625.260000] device br0 left promiscuous mode
<6>[29626.090000] ath1: authenticate with 74:d0:2b:43:13:34
<6>[29626.100000] ath1: send auth to 74:d0:2b:43:13:34 (try 1/3)
<6>[29626.110000] ath1: authenticated
<6>[29626.130000] ath1: associate with 74:d0:2b:43:13:34 (try 1/3)
<6>[29626.130000] ath1: RX AssocResp from 74:d0:2b:43:13:34 (capab=0x11 status=0 aid=4)
<6>[29626.140000] ath1: associated
<6>[29639.280000] br0: port 2(vlan2) entered forwarding state
<6>[29639.280000] br0: port 1(vlan1) entered forwarding state
<6>[29644.600000] br0: port 2(vlan2) entered disabled state
<6>[29644.600000] br0: port 1(vlan1) entered disabled state
<6>[29644.710000] device vlan1 left promiscuous mode
<6>[29644.720000] br0: port 1(vlan1) entered disabled state
<6>[29644.730000] device vlan2 left promiscuous mode
<6>[29644.730000] device eth0 left promiscuous mode
<6>[29644.740000] br0: port 2(vlan2) entered disabled state
<6>[29644.830000] ath1: deauthenticating from 74:d0:2b:43:13:34 by local choice (Reason: 3=DEAUTH_LEAVING)
<6>[29645.020000] device br0 entered promiscuous mode
<6>[29645.120000] device vlan1 entered promiscuous mode
<6>[29645.130000] device eth0 entered promiscuous mode
<6>[29645.180000] device vlan2 entered promiscuous mode
<6>[29645.190000] br0: port 2(vlan2) entered forwarding state
<6>[29645.190000] br0: port 2(vlan2) entered forwarding state
<6>[29645.200000] br0: port 1(vlan1) entered forwarding state
<6>[29645.200000] br0: port 1(vlan1) entered forwarding state
<6>[29645.210000] device br0 left promiscuous mode
<6>[29645.220000] device br0 entered promiscuous mode
<6>[29645.280000] cfg80211: Calling CRDA to update world regulatory domain
<3>[29645.310000] cfg80211: Invalid regulatory domain detected:
<6>[29645.310000] cfg80211: Regulatory domain: 00
<6>[29645.320000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29645.330000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.340000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.340000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.350000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.360000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.370000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29645.400000] cfg80211: Calling CRDA to update world regulatory domain
<6>[29645.410000] cfg80211: World regulatory domain updated:
<6>[29645.410000] cfg80211: DFS Master region: unset
<6>[29645.420000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29645.430000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.430000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.440000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.450000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.460000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
<6>[29645.470000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
<6>[29645.520000] cfg80211: Calling CRDA for country: US
<6>[29645.520000] cfg80211: Regulatory domain changed to country: US
<6>[29645.530000] cfg80211: DFS Master region: FCC
<6>[29645.540000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
<6>[29645.540000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29645.550000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
<6>[29645.560000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (N/A)
<6>[29645.570000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
<6>[29645.580000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
<6>[29646.200000] device br0 left promiscuous mode
<6>[29647.040000] ath1: authenticate with 74:d0:2b:43:13:34
<6>[29647.050000] ath1: send auth to 74:d0:2b:43:13:34 (try 1/3)
<6>[29647.060000] ath1: authenticated
<6>[29647.080000] ath1: associate with 74:d0:2b:43:13:34 (try 1/3)
<6>[29647.080000] ath1: RX AssocResp from 74:d0:2b:43:13:34 (capab=0x11 status=0 aid=4)
<6>[29647.090000] ath1: associated
<6>[29660.240000] br0: port 2(vlan2) entered forwarding state
<6>[29660.240000] br0: port 1(vlan1) entered forwarding state
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada

PostPosted: Fri Oct 31, 2014 3:43    Post subject: Reply with quote
no thats wds which is different, bridging the isp modem means to disable the router portion of it, then the asus would get an external wan ip like 50.11.4.100 or something like that, the dmesg isnt showing any drops at all..have u confirmed the issue either persists or fixes when connecting to the asus directly over wifi?
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum