openwrt

//-- 检查可用 channels root@OpenWrt:~# wlanconfig ath0 list chan Channel 36 : 5180 Mhz 11na C CU V VU V80- 42 V160- 50 H HU H80- 42 H160- 50 Channel 64 : 5320 *~ Mhz 11na C CL V VL V80- 58 V160- 50 H HL H80- 58 H160- 50 Channel 40 : 5200 Mhz 11na C CL V VL V80- 42 V160- 50 H HL H80- 42 H160- 50 Channel 149 : 5745 Mhz 11na C CU V VU V80-155 H HU H80-155 Channel 44 : 5220 Mhz 11na C CU V VU V80- 42 V160- 50 H HU H80- 42 H160- 50 Channel 153 : 5765 Mhz 11na C CL V VL V80-155 H HL H80-155 Channel 48 : 5240 Mhz 11na C CL V VL V80- 42 V160- 50 H HL H80- 42 H160- 50 Channel 157 : 5785 Mhz 11na C CU V VU

代码如下： echo 0xDEADBEEF > /etc/config/google_fu_mode 来源： https://www.cnblogs.com/vaemaxsky/p/11576076.html

WRTnode的U-boot使用方法 注：由于uboot里对gpio1和gpio2的特殊定义，因此我们在使用WRTnode核心板时不要碰触这两个针脚。 点击下载 uboot.bin 特点：支持网页刷新固件及uboot；支持U盘启动；波特率是115200。 工具：WRTnode，一根电源线；一根连接WRTnode的网线，一根短接线（如杜邦线）（刷新固件或uboot时用到）；U盘（从U盘启动内核时用到）； 注：如果是U盘启动我们的电源线要用三头usb线，这样可以提供一个接U盘的口。 操作过程： 从flash启动kernel 在没有插存有内核镜像的U盘并且没有将gpio1或gpio2接地的情况下，给WRTnode上电，WRTnode会选择从flash启动内核。 从U盘启动kernel WRTnode U-Boot U盘启动的优先级大于从flash启动，WRTnode U-Boot检测是否有U盘（或是SD卡），再检测U盘是否有uimage，如果有则从U盘启动，如果没有则从flash启动。 启动过程流程图 WRTnode U-Boot支持网页刷新固件及uboot 在WRTnode上电之前，先用网线连接好WRTnode的LAN口与PC网口，用一根短接线将gpio1或者是gpio2接地（参照[ 针脚定义 ]）。 打开网络连接，手动设置一个192.168.1.x网段的ip地址。给WRTnode上电

Led configuration The Led configuration is located in system uci subsystem, and written in the /etc/config/system file. Leds section The leds section contains settings that apply to non-default leds (default leds are usually “power connected” led, “system alive” led, leds showing ethernet port activity and leds showing wifi radio status. Their settings are defined somewhere else, see development guides) This is an example of leds on a tp-link router with usb port. root@lede:/# uci show system | grep "system.led" system.led_usb=led system.led_usb.name='USB' system.led_usb.sysfs='tp-link:green

I have built a custom toolchain from scratch for a MIPS 24kc (dragino) target platform, using gcc-6.3.0, musl-1.1.16 and binutils-2.27. That toolchain is completely functional. However, the size of my-custom toolchain is five times bigger than size of equivalent OpenWRT generated toolchain (557M vs 113M). Toolchain binaries generated by OpenWRT (mips-openwrt-linux-musl-*) are dynamically linked against libstdc++ and libgcc_s libraries. However, my toolchain binaries are linked with these libs statically: $ ldd mips-openwrt-linux-musl-gcc-5.3.0 linux-vdso.so.1 => (0x00007ffc4d534000) libstdc++

openwrt支持： USB Supprot------------------------------- kmod-usb-ohci kmod-usb-uhci kmod-usb-storage-extras kmod-usb2 Utilities------------------------------- bluez-utils bluez-daemon Utilities------------------------------- openobex openobex-apps 工具说明： bluez-utils依赖bluez-libs，dbus 生成工具：bccmd，bluemoon，btattach，btmon，btmgmt，ciptool，hciattach，hciconfig，hcidump，hcitool，hex2hcd，l2ping，l2test，mpris-proxy，rctest，rfcomm，sdptool，gatttool bluez-libs依赖kmod-bluetooth蓝牙hci驱动 bluez-daemon生成工具：bluetoothd，bluetoothctl，obexd openobex-apps生成工具：obex_test kmod-bluetooth驱动 openwrt蓝牙驱动ko参考：kmod-bluetooth $(LINUX_DIR

openwrt支持： USB Supprot------------------------------- kmod-usb-ohci kmod-usb-uhci kmod-usb-storage-extras kmod-usb2 Utilities------------------------------- bluez-utils bluez-daemon Utilities------------------------------- openobex openobex-apps 工具说明： bluez-utils依赖bluez-libs，dbus 生成工具：bccmd，bluemoon，btattach，btmon，btmgmt，ciptool，hciattach，hciconfig，hcidump，hcitool，hex2hcd，l2ping，l2test，mpris-proxy，rctest，rfcomm，sdptool，gatttool bluez-libs依赖kmod-bluetooth蓝牙hci驱动 bluez-daemon生成工具：bluetoothd，bluetoothctl，obexd openobex-apps生成工具：obex_test kmod-bluetooth驱动 openwrt蓝牙驱动ko参考：kmod-bluetooth $(LINUX_DIR

问题具体表现如下 这个问题困扰了我两个多星期，总算解决了。解决方案如下： 首先，先应该把配置菜单调好。 我的硬件是7620a，要编译的ipk包为helloworld，所以应该使用 make menuconfig命令进入配置菜单 进入后 将1号框选择为7620a，2号框选你要编译的包 保存后退出。 其次，应该在openwrt目录下用root用户进行编译 如果还提示有错，再 检查自己Linux系统内核和你编包的Makefile中的内核版本是否一致 ，不一致更改为系统内核版本。 helloworld下Makefile 查看 /lib/ 所以要将Makefile里的i386更改为x86_64 这些工作都没错以后再次编译 在openwrt/bin/ramips/packages/base目录下就可以找到你编的ipk包了 将他传到你的设备上，使用 opkg install ***.ipk命令 即可安装。 来源： https://www.cnblogs.com/area-h-p/p/11457161.html

I need to configure an "Accton MR3201A" access point running OpenWrt. I want it to provide an open WiFi with an HTTP authentication webpage on which users must provide a username & password before being able to access the internet. Is there an existing package ( http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/ ) that allows this ? 0xception This may be a little bit of an old post, but figured it might be helpful for anyone else searching: There are a few captive portal solutions out there and the best solution depends on your flexibility, customization, and technology requirements