Maybe a dumb question, but are JumboFrames supported?
(Last edited by belliash on 3 Apr 2015, 20:22)
The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Maybe a dumb question, but are JumboFrames supported?
(Last edited by belliash on 3 Apr 2015, 20:22)
@ethereal
You need to modify the file smb.conf located in /etc/samba from security = user to security = share and restart samba (/etc/init.d/samba restart)
nitroshift
thank you.
i hate to bother people but i don't have a clue how to edit the files (i think cd takes me to the folder)
ethereal wrote:nitroshift wrote:@ethereal
You need to modify the file smb.conf located in /etc/samba from security = user to security = share and restart samba (/etc/init.d/samba restart)
nitroshift
thank you.
i hate to bother people but i don't have a clue how to edit the files (i think cd takes me to the folder)
You can also use WinSCP via port 22 and edit via GUI text editor.
i've found the edit template tab in Luci, and found security = user - if i change this to security = share then save & apply and reboot the router will that work ?
Curious behavior after ~24 hours-- everything was very slow-- DNS queries taking seconds, web pages taking forever to completely load. No load on the router-- nothing in the logs. Restarted the router and everything is back to speedy. Will continue to watch it.
ethereal wrote:l3333 wrote:You can also use WinSCP via port 22 and edit via GUI text editor.
i've found the edit template tab in Luci, and found security = user - if i change this to security = share then save & apply and reboot the router will that work ?
It should work. I tried on mine for the first time and it did.
i can see the Backups folder but i can't access it
Still very curious as to why some people have issues with upgrades. I switch between various builds, kernel versions, etc. all the time, with zero issues. There is no logical reason at all why switching between kernel versions would require a different upgrade procedure. The kernel part of flashing is just a simple erase/write regardless of which upgrade mechanism is used.
If anyone has such a failed upgrade and can report a (failed) boot log from serial and a log of sysupgrade's output, I would greatly appreciate it.
The only problematic upgrade I can think of is McWRT to mainline OpenWrt trying to use a sysupgrade tar file. That will absolutely not work because McWRT has no idea how to write that properly and doesn't check to see if it is a standard image. Aside from that particular case, I have not been able to get it to fail.
(Last edited by leitec on 3 Apr 2015, 21:31)
The only problematic upgrade I can think of is McWRT to mainline OpenWrt trying to use a sysupgrade tar file. That will absolutely not work because McWRT has no idea how to write that properly and doesn't check to see if it is a standard image. Aside from that particular case, I have not been able to get it to fail.
Thats how i bricked it
(Last edited by belliash on 3 Apr 2015, 21:33)
alirz wrote:Well dangit...I always go from stock linksys to CC. But this time around i was running the custom image by @I3333 kernel 3.1.8 and decided to take a risk and flash the rc6 4.0 custom image directly without going to linksys. i unchecked "keep settings".
Flashed the image, and bricked the router!!!!!Lesson learned? = Force yourself to always go to stock Linksys first despite the urge of being lazy!
You can try to use reset button then connect to 192.168.1.1. It did work with the latest builds. Luci should work as well with the blank password after reset.
Could you please elaborate on this reset button trick? maybe im missing something.
Current state of my router looks to be bricked. I power it on, the power led flashes for about 3 secs and then goes solid!!! and thats where it seems to stay. The router has no ip of its own and doesnt issue ips at all also., no wan led...
The above reset button to 192.168.1.1 (assuming that was my IP, which it wasnt) is for telnet, ssh or serial ?
@belliash
Yeah, that's probably something that should go in the wiki page. I'll add that in a bit. (edit: done)
I also thought of another issue specific to switching between 3.18 and 4.0, which is that the wifi might not come up with the same configuration. I think the reason is the path as defined in /etc/config/wireless is slightly different, so "wifi detect" will think there are two new adapters. Although that's not really bricking the device, if somebody was trying to use only wireless that could be interpreted as such.
(Last edited by leitec on 3 Apr 2015, 22:29)
Samba and the NEW wifi driver work GREAT
i just picked up a wrt1900ac and well and of course after the first firmware flash failed, i ended up getting a serial cable and going through all that. i seem to be picking up the device pretty well but in all honestly at a loss on the images and kernel builds. i am a network engineer by trade and a "wanna-be" programmer, and a poor one at that. would someone be willing to give me a eli5 break down of what my best options are for this router? i see a lot of people are having custom packages built for them, and would love to be able to do my own but i just don't have the know how on that yet. basically what i am looking for is stability, stability, stability. that along with obviously solid wifi performance, possibly some routing protocols (ospf, maaaaaybe bgp just for honkin around), nfs storage would be great (yes, nfs not ntfs), tcpdump is a must, and possibly afp / appletalk / bonjour file sharing, ohhh and bandwidth tuning (being able to throttle certain wireless networks). i would have thought most of this stuff would have been available via packages but as someone else alluded to, not everything is there. i wanted to simply install nano and still can't get a straight answer. some say its there, some say its not. i can't seem to find it. anyways, ill try and wrap this up quickly. i've downloaded a few images that were posted marked as builds 45222, 45250, etc but every time i try and flash the router i ended up back on 45204. again, any recommendations would be greatly appreciated. i tend to be the type that once its working, leave it alone. and thats sorta what I'm after here minus making actual network changes. thanks in advance.
COUNT=3
HOST=$(/sbin/route | awk '/default/ { print $2 }')
STATUS=0
TIMEOUT=5while true; do
/bin/ping -q -c $COUNT -w $TIMEOUT $HOST 2>&1 > /dev/null
NEWSTATUS=$?if [ $NEWSTATUS -ne $STATUS ]; then
if [ $NEWSTATUS -eq 0 ]; then
echo 'none' > /sys/class/leds/mamba\:amber\:wan/trigger
echo '0' > /sys/class/leds/mamba\:amber\:wan/brightness
/etc/init.d/led restart 2>&1 > /dev/null
else
echo '0' > /sys/class/leds/mamba\:white\:wan/brightness
echo 'timer' > /sys/class/leds/mamba\:amber\:wan/trigger
echo '255' > /sys/class/leds/mamba\:amber\:wan/brightness
fi
STATUS=$NEWSTATUS
fi
sleep 30
done
Should be launched during boot and monitor WAN connection. For everyone interested ;-)
(Last edited by belliash on 3 Apr 2015, 22:36)
ok soi had bricked my router as mentioned in the prior post. I've gotten serial connection going. I see a kernel panic.
long story short i had tried to flash from CC 3.18.10 (r4222) to rc6 4.0 (r45250 i believe) without going to linksys firmware.
here is the serial log if anyone wants to see: https://www.dropbox.com/s/al2rnr17pbes2 … panic?dl=0
Now my question.. im trying to interrupt the U-boot process, but apparently non of keyboard keys are making it stop..
Im on a laptop. Tried with putty and with secure CRT....any ideas?
thanks
ok soi had bricked my router as mentioned in the prior post. I've gotten serial connection going. I see a kernel panic.
long story short i had tried to flash from CC 3.18.10 (r4222) to rc6 4.0 (r45250 i believe) without going to linksys firmware.
here is the serial log if anyone wants to see: https://www.dropbox.com/s/al2rnr17pbes2 … panic?dl=0Now my question.. im trying to interrupt the U-boot process, but apparently non of keyboard keys are making it stop..
Im on a laptop. Tried with putty and with secure CRT....any ideas?
thanks
check to make sure your pins from your serial cable are making contact with the header pins on the router. i had a similar issue and ended up taking off the black plastic sleeves and crimped the connections a bit to get a tighter fit. ended up solving my issue. i had a similar issue with the kernel panic as well, and i just rebooted the router and it seemed fine.
Can somebody compile a 4.0 image with the latest wifi driver + luci, My goal is to have optimal traffic over cable and ac over wifi.
Any advice and pointers will be help full.
Greetz a noob on this image
ok soi had bricked my router as mentioned in the prior post. I've gotten serial connection going. I see a kernel panic.
long story short i had tried to flash from CC 3.18.10 (r4222) to rc6 4.0 (r45250 i believe) without going to linksys firmware.
here is the serial log if anyone wants to see: https://www.dropbox.com/s/al2rnr17pbes2 … panic?dl=0
Thanks for the boot log. Something went wrong while writing the filesystem part, but what exactly is hard to tell. Did you do this from LuCI? I wonder if there's a chance the upload didn't complete all the way but the flash went on anyway.
edit: or maybe it's one of the options at the bottom of this message: http://lists.infradead.org/pipermail/li … 35416.html
I'll investigate when I have more time. Not sure why this would happen sometimes, but not always, and why I have not been able to duplicate it.
(Last edited by leitec on 3 Apr 2015, 23:28)
I just flashed to @Kaloz's March 31st build (did full without keeping settings) I have WIRED access, no luci (I know how to install) I can putty into it but I can't seem to log in. I have tried root with (blank),password,admin and nothing seems to work.
Anyone know what the initial login creds are for this build? (angry family with no wifi lol)
the 3.18.10 not the 4.0
(Last edited by craig.reiners on 3 Apr 2015, 23:37)
I just flashed to @Kaloz's March 31st build (did full without keeping settings) I have WIRED access, no luci (I know how to install) I can putty into it but I can't seem to log in. I have tried root with (blank),password,admin and nothing seems to work.
Anyone know what the initial login creds are for this build? (angry family with no wifi lol)
the 3.18.10 not the 4.0
if the router has no password you should be able to telnet 192.168.1.1
you can use telnet to install luci and/or set the router password then you can use putty and ssh (telnet is turned off after setting the password)
the default user name is root
you don't need user name or password for telnet
http://wiki.openwrt.org/doc/howto/firstlogin
(Last edited by ethereal on 3 Apr 2015, 23:49)
@ethereal THANKS!!!! .. I was trying to ssh.
well i managed to recover the router using serial..
i had one issue though... apparently the "setenv firmware_name.img" wasnt working for me. The kept expecting the image name "blk-mamba.128mb.img" so i renamed my firmware that and the file uploaded to the router...
alirz wrote:ok soi had bricked my router as mentioned in the prior post. I've gotten serial connection going. I see a kernel panic.
long story short i had tried to flash from CC 3.18.10 (r4222) to rc6 4.0 (r45250 i believe) without going to linksys firmware.
here is the serial log if anyone wants to see: https://www.dropbox.com/s/al2rnr17pbes2 … panic?dl=0Thanks for the boot log. Something went wrong while writing the filesystem part, but what exactly is hard to tell. Did you do this from LuCI? I wonder if there's a chance the upload didn't complete all the way but the flash went on anyway.
edit: or maybe it's one of the options at the bottom of this message: http://lists.infradead.org/pipermail/li … 35416.html
I'll investigate when I have more time. Not sure why this would happen sometimes, but not always, and why I have not been able to duplicate it.
yes i had flashed the full image through luci.
@ethereal THANKS!!!! .. I was trying to ssh.
my pleasure - you asked the only question i know the answer to
ethereal wrote:nitroshift wrote:@ethereal
You need to modify the file smb.conf located in /etc/samba from security = user to security = share and restart samba (/etc/init.d/samba restart)
nitroshift
thank you.
i hate to bother people but i don't have a clue how to edit the files (i think cd takes me to the folder)
You can also use WinSCP via port 22 and edit via GUI text editor.
okay - worked out how to use WinSCP here is my smb.conf - i still can't access the Backups folder
[global]
netbios name = OpenWrt
display charset = UTF-8
interfaces = 127.0.0.1/8 lo 192.168.1.1/24 br-lan
server string = OpenWrt
unix charset = UTF-8
workgroup = WORKGROUP
browseable = yes
deadtime = 30
domain master = yes
encrypt passwords = true
enable core files = no
guest account = nobody
guest ok = yes
invalid users = root
local master = yes
load printers = no
map to guest = Bad User
max protocol = SMB2
min receivefile size = 16384
null passwords = yes
obey pam restrictions = yes
os level = 20
passdb backend = smbpasswd
preferred master = yes
printable = no
security = share
smb encrypt = disabled
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY IPTOS_LOWDELAY
syslog = 2
use sendfile = yes
writeable = yes
[homes]
comment = Home Directories
browsable = no
read only = no
create mode = 0750
[Backups]
path = /Backups
read only = no
guest ok = yes
i went back to the latest linksys firmware - it was stable about 45 days and i could connect to my external hdd
(Last edited by ethereal on 4 Apr 2015, 13:19)
Trying to use the OpenWrt-ImageBuilder-mvebu.Linux-x86_64 (https://downloads.openwrt.org/snapshots … 64.tar.bz2)
https://dev.openwrt.org/ticket/19405#ticket
root@ubuntu:/opt/openwrt/OpenWrt-ImageBuilder-mvebu.Linux-x86_64# uname -a
Linux ubuntu 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Any ideas what I'm doing wrong?
I see others mentioning they are building it - what's the alternative for builds?
(Last edited by jesus on 4 Apr 2015, 01:20)
well i managed to recover the router using serial..
i had one issue though... apparently the "setenv firmware_name.img" wasnt working for me. The kept expecting the image name "blk-mamba.128mb.img" so i renamed my firmware that and the file uploaded to the router...
Likely because the u-boot variable name isn't "firmware_name.img" but "firmware_name"