Closed GoogleCodeExporter closed 9 years ago
a typo on step 4. should be read as this:
4. on vpn server side execute: telnet 172.16.1.254 5900 (where 172.16.1.254 -
ip assigned to vpn client)
Original comment by oblikoamorale@gmail.com
on 10 May 2012 at 8:31
I figured that there's no other way to know whats going on other than check the
serial console, so I've soldered TTL-RS232 converter, and... as expected, it's
kernel panic:
http://pastebin.com/raw.php?i=GJHj7GGk
rtn-r4177, and openvpn 2.2.1 from default repository.
any thoughts?
Original comment by oblikoamorale@gmail.com
on 11 May 2012 at 6:14
full kernel boot log: http://pastebin.com/eayhKJC1
Original comment by oblikoamorale@gmail.com
on 11 May 2012 at 6:20
I'm using rtn-r4177 compiled without wl, ntfs-3g and a couple of other modules.
if it helps the case, I'm ready to reproduce the crash and post results on
vanilla rt-n4177. just let me know.
Original comment by oblikoamorale@gmail.com
on 11 May 2012 at 6:23
You have to turn off Fast-NAT, as written in
http://code.google.com/p/wl500g/wiki/News
Original comment by lly.dev
on 11 May 2012 at 7:29
whoa, I'd never have thought about this. turning fastnat does help indeed.
thank you!
and, just for history & google, whoever might need this in future: ASUS RT-N10U
serial console pinout: J4 1.VCC 2.GND 3.TX 4.RX.
Original comment by oblikoamorale@gmail.com
on 11 May 2012 at 7:46
could you please reproduce kernel bug with latest rtn firmware?
the paste you have attached shows nothing, mean incomplete stack trace
Original comment by themiron.ru
on 9 Jun 2012 at 3:43
with latest firmware you mean last trunk build? sure, I'll give it a shot next
week.
unfortunately that paste is everything I managed to retrieve from the device
via serial console. I am unaware of any other way.
Original comment by oblikoamorale@gmail.com
on 9 Jun 2012 at 4:39
nevermind, test r4320 with fastnat *enabled*.
should be no problem.
Original comment by themiron.ru
on 10 Jun 2012 at 10:44
tested 4320, I confirm that kernel panic is gone. thank you!
do you consider 4320 safe enough to use or should I wait for "official" stable
release?
Original comment by oblikoamorale@gmail.com
on 14 Jun 2012 at 12:57
disregard the question - I missed recently featured 4330 release
Original comment by oblikoamorale@gmail.com
on 14 Jun 2012 at 12:59
Original issue reported on code.google.com by
oblikoamorale@gmail.com
on 10 May 2012 at 8:23