OpenWrt Forum Archive

Topic: Wrt160nl?

The content of this topic has been archived between 9 Mar 2018 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.

hello calltrace,
I have installed openwrt and chillispot, configured the system following this guide:
"https://forum.openwrt.org/viewtopic.php?id=11536"

However, I am having problems with VPN, this is the msg I am getting from chillispot; I am relating this error to the switch driver.  Any ideas?
thanks,
edward

/code
root@OpenWrt:~# chilli -fd
ChilliSpot version 1.1.0 started.
chillispot[1060]: ChilliSpot 1.1.0. Copyright 2002-2005 Mondru AB. Licensed under GPL. See http://www.chillispot.org for credits.
chillispot[1060]: tun.c: 705: 2 (No such file or directory) open() failed
chillispot[1060]: chilli.c: 3920: Failed to create tun
root@OpenWrt:~#
/code

I was testing switch/vlan stuff with today trunk.

Sudenly LAN stop working. I entered failsafe and did "firstboot". Reboot and...nothing. Repeated failsafe, "firstboot" and reboot. Impossible to reach at 192.168.1.1.

Is there something "firstboot" doesn't reset? NVRAM config words?

nunojpg wrote:

I was testing switch/vlan stuff with today trunk.

Sudenly LAN stop working. I entered failsafe and did "firstboot". Reboot and...nothing. Repeated failsafe, "firstboot" and reboot. Impossible to reach at 192.168.1.1.

Is there something "firstboot" doesn't reset? NVRAM config words?

Hello nunojpg,

do you have a serial console? If so, please could you verify wether you have the same behaviour I noted with trunk revision r19885 (see posting 521)?

@duez
Why switching driver or vpn ? Maybe I just not understand to you well.
But according to lines you posted, this look like your system missing tun.c  (TUN is virtual network device for userspace programs - in this case for chillispot)
Do you have installed tun kernel module ? if yes , is it insmodded ?
( lsmod | grep tun )

EDIT: on the fly reading of guide you fallowed (I have different configuration of chillispot ,freeradius  also integrated database into this router) - you have to install tun ,thats not mentioned there

(Last edited by calltrace on 5 Mar 2010, 11:06)

mine worked, before this VLAN/SWITCH experiments.

nunojpg wrote:

I was testing switch/vlan stuff with today trunk.

Sudenly LAN stop working. I entered failsafe and did "firstboot". Reboot and...nothing. Repeated failsafe, "firstboot" and reboot. Impossible to reach at 192.168.1.1.

Is there something "firstboot" doesn't reset? NVRAM config words?

Try this while in failsafe mode

mtd -r erase rootfs_data

It worked for me after similar problem and 1 month fighting ;]

(Last edited by kra4ol4e on 5 Mar 2010, 13:19)

@calltrace
first of all, thanks for your help.  You got me on the right track.  I have kmod-tun installed however it's not insmodded.
When I type "insmod tun" or even "insmod kmod-tun", I get no errors, however nothing really happens because I get no results with "lsmod | grep tun"

Any help please?

Thanks,
Edward.

Still have the problems with squashfs and trunk revision r19990:

Creating 6 MTD partitions on "spi0.0":
0x000000000000-0x000000040000 : "u-boot"
0x000000040000-0x000000180000 : "kernel"
0x000000180000-0x0000007e0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=490000, len=350000 
0x000000490000-0x0000007e0000 : "rootfs_data"
0x0000007e0000-0x0000007f0000 : "nvram"
0x0000007f0000-0x000000800000 : "art"
0x000000040000-0x0000007e0000 : "firmware"

...

switching to jffs2
mini_fo: using base directory: /
mini_fo: using storage directory: /jffs
jffs2 not ready yet; using ramdisk
mini_fo: using base directory: /
mini_fo: using storage directory: /tmp/root

Except for telnetd and dnsmasq no processes get started, therefore no LAN, no WAN access, just console access.
Since with jffs2-only fs it works perfectly, I guess it is a SW bug, not HW/flash fault. Will switch to jfss2 for now.

(Last edited by lbcd on 5 Mar 2010, 15:31)

@duez
Do you have serial console ? I had some problems with "no error message" at  lan
check /lib/modules/your_kernel_version  for tun.ko , then insmod tun.ko
then it should be listed in lsmod
and then chillispot should start  ok.

kra4ol4e wrote:
nunojpg wrote:

I was testing switch/vlan stuff with today trunk.

Sudenly LAN stop working. I entered failsafe and did "firstboot". Reboot and...nothing. Repeated failsafe, "firstboot" and reboot. Impossible to reach at 192.168.1.1.

Is there something "firstboot" doesn't reset? NVRAM config words?

Try this while in failsafe mode

mtd -r erase rootfs_data

It worked for me after similar problem and 1 month fighting ;]

You are right, this achieved the "reset", thanks.
Probably "firstboot" is not doing is job?

Regards

@ calltrace.....did it, just overcome the tun problem.....thanks
however, I am not being redirected to the login page.....i think i have top tweak "firewall.user"
thanks any way
due

I think No smile But dont know what configuration you have, I have login page inside this router so in this case:
You just need to install php-cgi and tell to httpd where it is
(if you using .php or .cgi file which you must place somewhere and tell this secret to chillispot  (in /etc/chilli.conf  )
chilli in debug nondeamonized mode can provide you a good explanation of where the problem is.

(Last edited by calltrace on 8 Mar 2010, 19:46)

I am quite lost.:(  It seems that there is no channel to the external WAN interface.  I can't ping websites, not even nslookup works....maybe a bad switch configuration?
Thanks,
Edward

After Kmod-ath9k, kmod-atheros package installation wi-fi interfaces appeared
--------------------------------------------------------------------------------------------------------------------------------------
root@OpenWrt:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:69:7F:BA:6B 
          inet addr:192.168.6.1  Bcast:192.168.6.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1367 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:110894 (108.2 KiB)  TX bytes:854 (854.0 B)
          Interrupt:4

eth1      Link encap:Ethernet  HWaddr 00:23:69:7F:BA:6C 
          inet addr:192.168.2.120  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1656 errors:0 dropped:0 overruns:0 frame:0
          TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:174622 (170.5 KiB)  TX bytes:69509 (67.8 KiB)
          Interrupt:5

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:23:69:7F:BA:6D 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
--------------------------------------------------------------------------------------------------------------------------------------

But after I've got next errors:

root@OpenWrt:~# /etc/init.d/network restart
/sbin/wifi: eval: line 1: can't create /proc/sys/dev/wl0/countrycode: nonexistent directory
/sbin/wifi: eval: line 1: can't create /proc/sys/dev/wl0/outdoor: nonexistent directory
cat: can't open '/proc/sys/dev/wl0/dev_name': No such file or directory
sysctl: error: 'dev.wl0.softled' is an unknown key
wlanconfig: ioctl: No such device
enable_atheros(wl0): Failed to set up ap vif

What shall I do with this problem?

Seems like you put a wireless config made for broadcom on a router using ath9k, this will not work. Regenerate the wifi config with

rm /etc/config/wireless; wifi detect > /etc/config/wireless

... and start over.

~ JoW

I have an wrt160nl with openwrt on it.
I have a laptop with intel 3945abg card, and when i do a ping to the router at different interval i got one "request time out" even if i'm near the router and when i have a replay from the router the response time is 7ms.
With the original linksys firmware i haven't that problem.
I think is from openwrt wireless driver.
Anyone has this problem "request time out"?

(Last edited by gogu_beb on 26 Mar 2010, 09:25)

@gogu_beb
I have a little worst issue with intel 3945 smile my kernel krash evetitime i try connect ...but mi last fw was 198xx , i will try wit latest

(Last edited by calltrace on 6 Apr 2010, 15:24)

hi All,
    Has anybody tested the OpenWRT trunk with 2.6.33, on WRT160NL, if yes then can you please share the svn revision.
Thanks,
mohnkhan

I experienced similar problems with my wifi client (Intel WiFi Link 5300 under kernel 2.6.32, Fedora 12)

At some point I was still associated (at least so it seemed), but i couldn't reach the router anymore. After some thousand pings the average was also like 7ms.


Sometimes i was just being deassociated without any obvious reason (very strong signal, just next to router).

As a 'workaround' i put the router in 11g only mode. Now ping average is 1ms and the connection is very stable.

Running 10.03-rc2





gogu_beb wrote:

I have an wrt160nl with openwrt on it.
I have a laptop with intel 3945abg card, and when i do a ping to the router at different interval i got one "request time out" even if i'm near the router and when i have a replay from the router the response time is 7ms.
With the original linksys firmware i haven't that problem.
I think is from openwrt wireless driver.
Anyone has this problem "request time out"?

after some fiddling I have come to this conclusion, the N mode is not yet ready for use with ath-9k, its a drivers issue., the G mode though works fine.

(Last edited by mohnkhan on 9 Apr 2010, 05:46)

androsyn wrote:

I've got a hacked up copy of uboot that I built from the Linksys sources.  It reenables saveenv and for shits and giggles I added support for bzip2 and lzma compressed kernels, the image is at:  http://squeaker.ratbox.org/u-boot.bin

To flash it from tftp, do an upgrade boot.bin and tftp it to the router.  Be careful as if this goes wrong you *will* end up with a brick.  Also it seems to blow away some of the settings like your mac address etc so make a note of what your printenv environment looked like before doing this. 

-Aaron

I tried the u-boot upgrade listed here and the flash went ok, but on reboot no serial or lan lights came up so i'm pretty sure the unit is bricked. Does anyone have some tips for recovery, is jtag a possibility?

I have a second unit here but that has u-boot 1.1.6 and it won't boot openwrt automatically, what's the best way to get around this?

please can  anybody guide me with how to detect the uboot version and replace it ?
I would really appreciate the help.
I am not sure which version of uboot to use for openwrt to work.

PLEASE HELP....
I bought two routers, of the first one I tried the latest openwrt image
http://downloads.openwrt.org/backfire/1 … uashfs.bin   copied it to my linux desktop
(timestamp as shown in browser 06-Apr-2010 13:03             Size - 2621472)
then connected to the router via the LAN port.
used firefox to get the administrative section of web interface
selected this above image
and pressed the button to upgrade.

I got a progress bar.... for sometime
then a upgrade failed message..

I tried telnet it gave connection refused.
tried ssh it gave connection refused.

I tried to NMAP the router to check which ports are open..
except 80 and some 2869 tcp port no other port was open.

now I reboot the router to retry the upgrade and wanted to make sure that I haven't caused any stress based issues while I upgrade.

next time I reboot the router...

the power light keeps blinking
and after about 10 seconds or so.. all the ethernet port lights switch on for hald a second and go off.
nothing else happens


I have tried to check if TFTP is still alive..

I tried the reset button trick which I used to do on 54GL, but to no avail.
I tried continuous ping to the router and power cycling it to check if TFTP is alive
also tried to check wireshark, other than the ARP request I don't get any reply

sad
a bad day for me..

I am trying to check if serial cable can be of any help.

anybody have any directions to point me to
sad sad

(Last edited by chromesheild on 13 Apr 2010, 13:03)

Sorry, posts 551 to 550 are missing from our archive.