Re: [OpenWrt-Users] su utility in OpenWRT "White Russian" release
Problem is, that this White Russian router is in another country :) I can't upgrade this. Hardware is WRT54GS. I downloaded OpenWrt-SDK-Linux-i686-1.tar.bz2(http://downloads.openwrt.org/whiterussian/0.9/OpenWrt-SDK-Linux-i686-1.tar.bz2), but I'm not sure if I should try to build entire coreutils or is it possible also to simply compile the su binary. Martin On Sat, Jan 28, 2017 at 3:56 PM, Aaron Z <aczlan+open...@gmail.com> wrote: > On Sat, Jan 28, 2017 at 8:48 AM, Aaron Z <aczlan+open...@gmail.com> wrote: >> On Sat, Jan 28, 2017 at 7:10 AM, Martin T <m4rtn...@gmail.com> wrote: >>> I need to enable non-root users to log into the router and if needed, >>> execute su to become a root user. >> What hardware is it running on? Will it handle a newer firmware >> (perhaps the LEDE 17.0.1 that is in release testing now?). >> I dont think su can be easily be backported to White Russian... > > Correction, LEDE is/will be 17.01, I put an extra period in the version. > > Aaron Z > A human being should be able to change a diaper, plan an invasion, > butcher a hog, conn a ship, design a building, write a sonnet, balance > accounts, build a wall, set a bone, comfort the dying, take orders, > give orders, cooperate, act alone, solve equations, analyze a new > problem, pitch manure, program a computer, cook a tasty meal, fight > efficiently, die gallantly. Specialization is for insects. > — Robert Heinlein, Time Enough for Love ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
[OpenWrt-Users] su utility in OpenWRT "White Russian" release
Hi, I have an OpenWRT router with "White Russian" release in remote location. It has no "su" command and if I inspect the package/busybox/config/loginutils/Config.in file in http://downloads.openwrt.org/whiterussian/0.9/whiterussian-0.9.tar.bz2, then looks like BusyBox was compiled without "su" command. In addition, there seems to be no "coreutils-su" package for "White Russian" as there is for example for "Backfire"( OpenWRT 10.03). I installed OpenWRT "Backfire" to identical router and installed the coreutils-su_7.2-1_brcm47xx.ipk package and then copied /usr/bin/su to this remote "White Russian" router. While the binary architecture should be correct, it does not run: root@wr:~# /usr/bin/su /usr/bin/su: symbol 'stdout': can't handle reloc type 0x7e root@wr:~# Error above should indicate to library issues. According to ldd "su" binary requires following libraries: libcrypt.so.0 => /lib/libcrypt.so.0 (0x2aabe000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2aae2000) libc.so.0 => /lib/libc.so.0 (0x2ab02000) ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x2aaa8000) In "Backfire", where "su" binary was copied from, they have following versions: libcrypt-0.9.30.1.so libgcc_s.so.1 libuClibc-0.9.30.1.so ld-uClibc-0.9.30.1.so In "White Russian" they have following versions: libcrypt-0.9.27.so libgcc_s.so.1 libuClibc-0.9.27.so ld-uClibc-0.9.27.so I guess it is not safe to simply copy newer libraries into the "White Russian" router as it might break some programs. Should I install OpenWRT "White Russian" to this spare router and try to copile coreutils or coreutils-su there and then again copy the su binary into this remote router? If yes, then which coreutils or coreutils-su source version should I use in order to compile the su binary? I looked into https://github.com/openwrt/packages/tree/master/utils, but didn't find anything suitable. Or maybe there is some smarter way? thanks, Martin ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
Re: [OpenWrt-Users] In which situation it's useful to flash over serial port?
Ok. I wasn't aware that kermit is a protocol supporting file transfers over serial line. I always thought that it's just a software suit supporting xmodem/ymodem/zmodem file transfers over RS-232. As I understand, most popular implementations of kermit protocol are C-Kermit and Kermit95, which both support (over external modules) xmodem/ymodem/zmodem over RS-232 as well. regards, Martin On Thu, Aug 15, 2013 at 9:28 PM, Karl O. Pinc k...@meme.com wrote: On 08/15/2013 03:36:07 PM, Martin T wrote: Ok, thanks for explaining this! Uploading the firmware through the serial itself uses xmodem/ymodem/zmodem protocol? No, it uses kermit. Fortunately the kermit program is now under and open source license. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
Re: [OpenWrt-Users] In which situation it's useful to flash over serial port?
Ok, thanks for explaining this! Uploading the firmware through the serial itself uses xmodem/ymodem/zmodem protocol? regards, Martin On Thu, Aug 15, 2013 at 2:29 PM, Luiz Angelo Daros de Luca luizl...@gmail.com wrote: Some devices do not have an external way to activate tftp boot (like tp-link). You must interact with bootloader in order to ask it to download a new firmware. Other routers, that might be your case, have some kind of konami code to start a firmware recovery mode, like pressing reset while you turn on your device. Also, some bootloaders allows you to upload a new firmware though the serial itself (i.e. via kermit). This allows a reflash even for devices that do not have a working ethernet interface. Generally, this is not recomended as it is much slower than tftp. As I my pc has only one ethernet, I used kermit in order to keep my internet online while flashing my device. Regards, --- Luiz Angelo Daros de Luca, Me. luizl...@gmail.com 2013/8/12 Martin T m4rtn...@gmail.com Hi, there are few guides in OpenWRT wiki which explain how to configure IP settings and download(using TFTP) an OpenWRT firmware file in bootloader(for example CFE) CLI. For example, I have following commands available in my CFE: CFE help Available commands: rndis Broadcom USB RNDIS utility. et Broadcom Ethernet utility. nvram NVRAM utility. reboot Reboot. printdefaultDisplay the environment default variables embeded in the bootloader flash Update a flash memory device autobootAutomatic system bootstrap. batch Load a batch file into memory and execute it go Verify and boot OS image. bootLoad an executable file into memory and execute it loadLoad an executable file into memory without executing it write Write a region of memory to a remote file via TFTP readRead a region of memory to a remote file via TFTP saveSave a region of memory to a remote file via TFTP pingPing a remote IP host. arp Display or modify the ARP Table ifconfigConfigure the Ethernet interface unsetenvDelete an environment variable. printenvDisplay the environment variables setenv Set an environment variable. helpObtain help for CFE commands For more information about a command, enter 'help command-name' *** command status = 0 CFE As far as I know, in order to access the bootloader CLI, a working bootloader and serial connection is required. This means that one can not repair bootloader itself over serial port. And in case the OpenWRT installation is broken and one can not even access the failsafe mode, then OpenWRT can be easily flashed by uploading the OpenWRT firmware from TFTP client in PC without initiating this on bootloader CLI. In which situation it's useful to be able to start the TFTP client on bootloader CLI? Are there situations where router bootloader will not start the TFTP server and one is not able to upload the firmware from TFTP client running in PC? Or are there some other clever maintenance tasks usually carried out from bootloader CLI? regards, Martin ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
[OpenWrt-Users] How does option 'isolate' '1' work?
According to /etc/config/wireless configuration file documentation, option 'isolate' '1' isolates wireless clients from each other in case device is working in WAP mode. In other words 802.11a/b/g/n clients are not able to reach each other in the same collision domain. For example if I set option 'isolate' '1' then I'm not able to ping or arping a host in the same 802.11g network. This setting does not change any firewall rules according to iptables -L. In addition, there is no ebtables installed. How is this technically achieved? Is this part of 802.11 standards? I haven't found an article which explains this. I guess this isolation is done on physical layer(802.11a/b/g/n)? Martin ___ openwrt-users mailing list openwrt-users@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-users
