do you happend to know a method to trigger by btn?

i misconfigured a wrt1200ac and added a switch section at the end of /etc/config/network
(was hopping to ghet switch tap inside luci)
and now all lan/wan are locked

OpenWrt Failsafe
http://wiki.openwrt.org/doc/howto/gener … lsafe_mode

ty but already tried and not working(maybe the timing was bad)
https://forum.openwrt.org/viewtopic.php … 84#p286984

Briked?

I don't know, you were paying with the swith VLAN's

yea
i told him to add this to the end of network hoping that switch tab will come up
but i think i should also reconfigured vlans

config switch
  option name 'switch0'                  
  option reset '1'
  option enable_vlan '1'

installed on v2:

config wifi-device 'radio0'                                                                          
        option type 'mac80211'                                                                       
        option hwmode '11a'                                                                          
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'                   
        option htmode 'VHT80'                                                                        
        option country 'US'                                                                          
        option channel '149'                                                                         
        option txpower '30'                                                                          
                                                                                                     
config wifi-iface                                                                                    
        option device 'radio0'                                                                       
        option network 'lan'                                                                         
        option mode 'ap'                                                                             
        option ssid 'omitted-5g'                                                               
        option encryption 'psk2+ccmp'                                                                
        option key 'omitted'                                                                        
                                                                                                     
config wifi-device 'radio1'                                                                          
        option type 'mac80211'                                                                       
        option hwmode '11g'                                                                          
        option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'                   
        option htmode 'HT20'                                                                         
        option country 'US'                                                                          
        option channel '6'                                                                           
        option txpower '30'                                                                          
                                                                                                     
config wifi-iface                                                                                    
        option device 'radio1'                                                                       
        option network 'lan'                                                                         
        option mode 'ap'                                                                             
        option ssid 'omitted'                                                                  
        option encryption 'psk2+ccmp'                                                                
        option key 'omitted' 

Tranmissions speeds are:
AC - 380-580Mb/s
N - 130-145Mb/s

compared with OEM:
AC - 878Mb/s
N - 217Mb/s.

Still packet loss...

(Last edited by jmschu02 on 10 Aug 2015, 22:12)

This will bring the switch tab up, and WAN/LAN ports will be fine.

config switch
    option name 'switch0'
    option reset '1'
    option enable_vlan '1'

config switch_vlan
    option device 'switch0'
    option vlan '1'
    option ports '0 1 2 3 5'

config switch_vlan
    option device 'switch0'
    option vlan '2'
    option ports '4 6'

nice ty
but still have to trigger a safemode
this is default switch before adding switch to network(didnt apear as tab in luci)

swconfig dev switch0 show
Global attributes:
    enable_vlan: 0
Port 0:
    mask: 0x004e: (0) 1 2 3 6
    status: link: down
Port 1:
    mask: 0x004d: 0 (1) 2 3 6 
    status: link: down
Port 2:
    mask: 0x004b: 0 1 (2) 3 6 
    status: link: down
Port 3:
    mask: 0x0047: 0 1 2 (3) 6 
    status: link: up, speed: 100 Mbps, duplex: full
Port 4:
    mask: 0x0020: (4) 5 
    status: link: down
Port 5:
    mask: 0x0010: 4 (5) 
    status: link: up, speed: 1000 Mbps, duplex: full
Port 6:
    mask: 0x000f: 0 1 2 3 (6) 
    status: link: up, speed: 1000 Mbps, duplex: full

id say 5 and 6 have to be 4 5t and 0 1 2 3 6t
i went so far couse it didnt had wan connection
i thought it was the switch

Fan
http://www.gypsy-designs.com/fan.pdf

Fan info
http://www.gypsy-designs.com/fan_info.pdf

My setup

Using username "root".
Authenticating with public key "rsa-key-20120810"

BusyBox v1.23.2 (2015-06-18 06:39:10 CEST) built-in shell (ash)

Linksys WRT1900AC (Mamba)
Security is enabled, and your IP address has been logged.

root@AC1900M:~# swconfig dev switch0 show
Global attributes:
        enable_vlan: 1
Port 0:
        mask: 0x0000: (0)
        qmode: 3
        status: link: up, speed: 100 Mbps, duplex: full
        link: 100
        pvid: 1
Port 1:
        mask: 0x0000: (1)
        qmode: 3
        status: link: down
        link: 0
        pvid: 1
Port 2:
        mask: 0x0000: (2)
        qmode: 3
        status: link: down
        link: 0
        pvid: 1
Port 3:
        mask: 0x0000: (3)
        qmode: 3
        status: link: up, speed: 1000 Mbps, duplex: full
        link: 1000
        pvid: 1
Port 4:
        mask: 0x0000: (4)
        qmode: 3
        status: link: up, speed: 100 Mbps, duplex: full
        link: 100
        pvid: 2
Port 5:
        mask: 0x0000: (5)
        qmode: 3
        status: link: up, speed: 1000 Mbps, duplex: full
        link: 1000
        pvid: 1
Port 6:
        mask: 0x0000: (6)
        qmode: 3
        status: link: up, speed: 1000 Mbps, duplex: full
        link: 1000
        pvid: 2
VLAN 1:
        port_based: 0
        vid: 1
        ports: 0 1 2 3 5
VLAN 2:
        port_based: 0
        vid: 2
        ports: 4 6
root@AC1900M:~#

BTY I have a switch tab

(Last edited by gufus on 10 Aug 2015, 23:31)

@gufus
yeap your switch is like that
from imagebuilder wrt1900ac

armada-xp-linksys-mamba)
    ucidef_set_interfaces_lan_wan "eth0" "eth1"
    ucidef_add_switch "switch0" "1" "1"
    ucidef_add_switch_vlan "switch0" "1" "0 1 2 3 5"
    ucidef_add_switch_vlan "switch0" "2" "4 6"

but wrt1200ac
https://img.bi/#/4bkp4p7!A-q7YASZZREgfK … QhTypwTQSm
seems to be

0 1 2 3 6
4 5

yours seem to work ok having www trough wan and nating seems you dont need tagged ports
how does it look you luci > network > switch section? can you post a picture pls?

(Last edited by makarel on 10 Aug 2015, 23:44)

Ah

iptables stops logging on its own.  I've noticed a couple of times where I've set up iptables logging, but only to find out a couple of hours later logging has stopped.

This is what I should see  #iptables -L   

Chain zone_wan_src_DROP (1 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere             LOG level warning prefix "IPTables-Dropped: "

Is there some kind of time out that's happening?

(Last edited by davidc502 on 10 Aug 2015, 23:59)

http://www.gypsy-designs.com/21.jpg

@gufus

whell the device was configured ok apart from the missing switch tab
but it didntnt connected the wan cable and i failed to see that (he sed its all connected fine though)

ty for your help

Your Welcome

Can someone please tell me how i can disable the following logging under system log. I've started seeing this in the recent trunk builds.
Not sure what they mean and why I'm even seeing kernel debug level log under system log. I've already put system log level to "error" but it doesnt help.
From what i think, i say that logging levles are screwed up in the recent build. I also have cron log level set to "WARNING" yet i keep seeing the usual info level cron log

on Aug 10 20:07:40 2015 kern.info kernel: [88711.218582] ieee80211 phy0: wmm:26, rsn:0, rsn48:22, ht:62, vht:0
Mon Aug 10 20:07:40 2015 kern.debug kernel: [88711.233929] ieee80211 phy0: interface: 3, change: 0x3e
Mon Aug 10 20:08:48 2015 kern.debug kernel: [88779.517624] ieee80211 phy0: interface: 3, change: 0x100
Mon Aug 10 20:08:48 2015 kern.info kernel: [88779.517669] ieee80211 phy0: wmm:26, rsn:0, rsn48:22, ht:62, vht:0
Mon Aug 10 20:08:48 2015 kern.debug kernel: [88779.532973] ieee80211 phy0: interface: 3, change: 0x3e
Mon Aug 10 20:09:38 2015 daemon.info hostapd: wlan0: STA 6c:ad:f8:18:2e:a0 WPA: group key handshake completed (RSN)
Mon Aug 10 20:09:49 2015 kern.debug kernel: [88840.351269] ieee80211 phy0: interface: 3, change: 0x100
Mon Aug 10 20:09:49 2015 kern.info kernel: [88840.351314] ieee80211 phy0: wmm:26, rsn:0, rsn48:22, ht:62, vht:0
Mon Aug 10 20:09:49 2015 kern.debug kernel: [88840.366504] ieee80211 phy0: interface: 3, change: 0x3e
Mon Aug 10 20:10:00 2015 cron.info crond[1173]: USER root pid 5194 cmd /sbin/fan_ctrl.sh
Mon Aug 10 20:10:58 2015 kern.debug kernel: [88909.520504] ieee80211 phy0: interface: 3, change: 0x100
Mon Aug 10 20:10:58 2015 kern.info kernel: [88909.520550] ieee80211 phy0: wmm:26, rsn:0, rsn48:22, ht:62, vht:0
Mon Aug 10 20:10:58 2015 kern.debug kernel: [88909.535938] ieee80211 phy0: interface: 3, change: 0x3e
Mon Aug 10 20:11:22 2015 kern.debug kernel: [88933.481654] ieee80211 phy0: interface: 3, change: 0x100
Mon Aug 10 20:11:22 2015 kern.info kernel: [88933.481699] ieee80211 phy0: wmm:26, rsn:0, rsn48:22, ht:62, vht:0
Mon Aug 10 20:11:22 2015 kern.debug kernel: [88933.496890] ieee80211 phy0: interface: 3, change: 0x3e
Mon Aug 10 20:12:28 2015 kern.debug kernel: [88999.522405] ieee80211 phy0: interface: 3, change: 0x100

UPDATE:

hmmm i see the following:
-------------------------------------------------------------------------------------------
root@OpenWrt:/home/alirz# cat /var/run/hostapd-phy0.conf
driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=US
ieee80211d=1
hw_mode=g
channel=11

ieee80211n=1
ht_coex=0
ht_capab=[HT40-][LDPC][SHORT-GI-20][SHORT-GI-40]
-------------------------------------------------------------------------------------------

Shouldnt that log level be 4 if i've set the system logging to Warning from Luci? or that log setting in Luci doesnt apply to the wireless interface logging? OR is the logging screwed up because i manually deplyed the new mlwifif .bin file on my router recently as suggested in previous posts?

just throwing my thoughts out there! Thanks

(Last edited by alirz on 11 Aug 2015, 02:27)

I tried using these commands  from http://wiki.openwrt.org/doc/devel/debugging
to set log level. Even though the log level is set to 3, im still seeing the above mentioned logs under system logs.

root@OpenWrt:~# uci set wireless.radio0.log_level=3
root@OpenWrt:~# uci commit wireless
root@OpenWrt:~# wifi up

(Last edited by alirz on 11 Aug 2015, 02:40)

This was from debug code in one of the recent wireless drivers.

Has since been removed by Marvel in the driver code but not yet pushed to OpenWRT.

@Kaloz: can you push the driver debug removal code to CC + Trunk please?

Shouldnt i be able manually change the log level for the wireless? As per the commands i used above, though they didnt seem to make any difference to the logs, It still looks the same

@DavidMcWRT

Kaloz did push the driver to trunk soon after getting it from Marvell. As for CC, it will be there in RC4 / final release because RC3 was built before Marvell released the driver update.

nitroshift

(Last edited by nitroshift on 11 Aug 2015, 19:32)

The CC branch (nor trunk as far as I can see) isn't presently running mwlwifi aaf953e1, it's still at 36e430f.  That doesn't include the most recent mwlwifi code to remove the debug code which I believe is what DavidMcWRT is requesting.   

I'm running the CC branch which I compiled myself (so somewhere between RC3 and 4).  I haven't seen issue 20 but issue 21 is still there.  The router hard locked a day into the newest build but has been running ok since.  It still appears to be a somewhat random hardlock.

https://dev.openwrt.org/changeset/46521

Was the LAST trunk push of mwlwifi which is

https://github.com/kaloz/mwlwifi/commit … b176f39239

BTY RC3 is using

kmod-mwlwifi     3.18.17+10.3.0.3-20150619-1

also:
Update F/W to version 7.2.8.6.
88W8864.bin

It's EASY to see if trunk is using this, just do a file hash

(Last edited by gufus on 11 Aug 2015, 21:10)

It would be interesting to determine who is still experiencing random lockups on their wrt1900ac and if there is any correlation to whether this is happening to those of us that bought a used/refurbished model. I bought mine used on Amazon.

I am still experiencing lockups with all CC versions including the latest trunk release. At this point my 1900 is offline until this is resolved. It's interesting to see that issue #21 has yet to be addressed. Could I have a bad router with a "flaky" CPU? Was there a problem during the binning process? Are there any V2 owners experiencing this issue?? How do you claim a warranty repair in this case?

(Last edited by tusc on 11 Aug 2015, 21:22)

I was referring to the patch to remove the extra debug information, which to my knowledge hasn't been pushed to trunk/CC yet:

https://github.com/kaloz/mwlwifi/commit … 0bd48f4759