The content of this topic has been archived between 23 Mar 2017 and 13 Apr 2018. Unfortunately there are posts – most likely complete pages – missing.
OK - meanwhile I also have two Easyboxes working on WDS. But then they're a mixed pair...one of them a 802 and the other a 803. Trying to replace the 802 against an 803 always ends up in a quirky connection and I can't find the cause of that misbehaviour.
Is there a way to set the MAC addresses by manipulating NVRAM maybe?
Did I understand it correctly, you would like to use one 803 as access point and another 803 as repeater with the same image? If so, thats exactly what I am doing and it works fine. It is enough to set different MAC addresses in the config file. How did you set them?
(Last edited by puma14 on 26 Jul 2014, 21:54)
The kernel modules are dependent on the image version. If you do not want to change the image, you have to find someone who install the source with the same image release as snk and generate the kmod files.
But you can also install the image from the snapshot http://downloads.openwrt.org/snapshots/trunk/lantiq/ with all related modules and configure it, which seems currently even newer than my image, or you use the image I have posted in the past. It might be compatible to the one from snk, so perhaps you can keep your settings. Then I can create the suitable kmod files for you.
When I download openwrt-lantiq-xway-ARV4525PW-squashfs.image from snapshot I get a kernel panic. So what do you mean by "all related modules and configure"?
And what is exactly creating a kmod file?
Taking a kmod file from trunk and somehow make it work for the image I´m using? Is there a description around what steps need tobe done?
BTW:
Of course I can take your image and it would be nice if you could provide the kmod files, but then I still don't know the process behind it and it would might be better for the future that I´m able to do this on my own....
When I download openwrt-lantiq-xway-ARV4525PW-squashfs.image from snapshot I get a kernel panic. So what do you mean by "all related modules and configure"?
And what is exactly creating a kmod file?
Taking a kmod file from trunk and somehow make it work for the image I´m using? Is there a description around what steps need tobe done?BTW:
Of course I can take your image and it would be nice if you could provide the kmod files, but then I still don't know the process behind it and it would might be better for the future that I´m able to do this on my own....
The process behind is just to download the source, to install all package feeds and to generate the image with the needed modules. The steps are described in http://wiki.openwrt.org/doc/howto/build.
maybe theory is missing on my side, but where is then the difference to install BB from here:
http://downloads.openwrt.org/barrier_br … ntiq/xway/
and install the packages I need from the packages folder with opkg?
That should be the same as including the packages to a personal build or not?
(I tried to use BB from the link above but I always get "segmentation error" when I want to install a small package to mount usb-storage....)
So my fear is that when I spend days to understand how to build my own image I´ll end up in the same situation....
Did I understand it correctly, you would like to use one 803 as access point and another 803 as repeater with the same image? If so, thats exactly what I am doing and it works fine. It is enough to set different MAC addresses in the config file
Well, yes and no...:-)
Yes, I intend to have one AP and one repeater and I want both to be Easybox 803 models...and
No, it's not working properly in my case (though keeping to your config example as close as possible).
Everything works fine as long as the AP is an 803 model and the repeater an 802 one. Today I set up my second 803 model in addition to the former and it gives me the same results as with two 803s.
Here is the situation:
You can see the AP and two associated repeaters plus the laptop computer (the one that shows the IP number).
Everything looks fine, but connecting the laptop to the 803-repeater results in no internet connection. The log of that repeater comes with messages like that:
Sun Jul 27 15:05:02 2014 kern.warn kernel: [ 665.488000] br-lan: received packet on wlan0 with own address as source address
Sun Jul 27 15:05:06 2014 kern.warn kernel: [ 669.884000] br-lan: received packet on wlan0 with own address as source address
Sun Jul 27 15:13:43 2014 kern.warn kernel: [ 884.324000] br-lan: received packet on wlan0 with own address as source address
Sun Jul 27 15:13:58 2014 kern.warn kernel: [ 899.336000] br-lan: received packet on wlan0 with own address as source addressWhen I try to ping the AP I get this:
root@laptop:/home/user# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.3: icmp_seq=2 Redirect Host(New nexthop: 192.168.1.1)
From 192.168.1.3: icmp_seq=4 Redirect Host(New nexthop: 192.168.1.1)
From 192.168.1.3: icmp_seq=7 Redirect Host(New nexthop: 192.168.1.1)
From 192.168.1.3: icmp_seq=13 Redirect Host(New nexthop: 192.168.1.1)The webserver on 192.168.1.1 is unreachable, whereas the LAN-connected box X.X.X.3 and the repeater in the other room (X.X.X.2), the Easybox 802, reply the way they should.
Sure, I could simply stay with the 803/802 pair, but I'd rather have two 803s.
So what can I do?
maybe theory is missing on my side, but where is then the difference to install BB from here:
http://downloads.openwrt.org/barrier_br … ntiq/xway/and install the packages I need from the packages folder with opkg?
That should be the same as including the packages to a personal build or not?(I tried to use BB from the link above but I always get "segmentation error" when I want to install a small package to mount usb-storage....)
So my fear is that when I spend days to understand how to build my own image I´ll end up in the same situation....
The default folder for opkg is a snapshot from the trunk, which is updated periodically. The problem is that some modules (especially the kernel modules) works only with suitable image versions. You can use another folder for opkg by adopting /etc/opkg.conf, but sometimes some modules are missing. Nevertheless there is a way to create a package by combining to different packages as discussed in the past. But some missing modules could still remain.
The included versions of the modules in the personal build does not necessarily correspond to the versions of the opkg list.
The webserver on 192.168.1.1 is unreachable, whereas the LAN-connected box X.X.X.3 and the repeater in the other room (X.X.X.2), the Easybox 802, reply the way they should.
Sure, I could simply stay with the 803/802 pair, but I'd rather have two 803s.
So what can I do?
Could you post the output of "ifconfig" with the AP and the 803 repeater?
Sure....here you are (having all the three Easyboxes connected):
root@Hacker-1:~# ifconfig
br-lan Link encap:Ethernet HWaddr 00:00:83:89:D0:00
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fdaa:9195:9547::1/60 Scope:Global
inet6 addr: fe80::200:83ff:fe89:d000/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:125802 errors:0 dropped:0 overruns:0 frame:0
TX packets:190579 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10919544 (10.4 MiB) TX bytes:229166755 (218.5 MiB)
eth0 Link encap:Ethernet HWaddr 00:00:83:89:D0:00
inet6 addr: fe80::200:83ff:fe89:d000/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:98625 errors:0 dropped:0 overruns:0 frame:0
TX packets:130592 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12249129 (11.6 MiB) TX bytes:129504018 (123.5 MiB)
eth0.1 Link encap:Ethernet HWaddr 00:00:83:89:D0:00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:98625 errors:0 dropped:0 overruns:0 frame:0
TX packets:130588 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10276629 (9.7 MiB) TX bytes:128720034 (122.7 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:261 errors:0 dropped:0 overruns:0 frame:0
TX packets:261 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18404 (17.9 KiB) TX bytes:18404 (17.9 KiB)
nas0 Link encap:Ethernet HWaddr 00:00:01:00:00:00
inet6 addr: fe80::200:1ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:199460 errors:0 dropped:0 overruns:0 frame:0
TX packets:130455 errors:579 dropped:0 overruns:579 carrier:0
collisions:0 txqueuelen:1000
RX bytes:225484046 (215.0 MiB) TX bytes:12744166 (12.1 MiB)
pppoe-wan Link encap:Point-to-Point Protocol
inet addr:125.22.162.22 P-t-P:81.114.74.137 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:175479 errors:0 dropped:0 overruns:0 frame:0
TX packets:106459 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:222976983 (212.6 MiB) TX bytes:8376941 (7.9 MiB)
wlan0 Link encap:Ethernet HWaddr 00:0C:43:30:62:00
inet6 addr: fe80::20c:43ff:fe30:6200/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41536 errors:0 dropped:0 overruns:0 frame:0
TX packets:79147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3031284 (2.8 MiB) TX bytes:106825514 (101.8 MiB)
wlan0.sta2 Link encap:Ethernet HWaddr 00:0C:43:30:62:00
inet6 addr: fe80::20c:43ff:fe30:6200/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6170 errors:0 dropped:0 overruns:0 frame:0
TX packets:9819 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1297039 (1.2 MiB) TX bytes:1801077 (1.7 MiB)
wlan0.sta3 Link encap:Ethernet HWaddr 00:0C:43:30:62:00
inet6 addr: fe80::20c:43ff:fe30:6200/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2410 errors:0 dropped:0 overruns:0 frame:0
TX packets:2517 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:537317 (524.7 KiB) TX bytes:352122 (343.8 KiB)Could switching off vlan functionality on X.X.X.3 make any difference?
And how is the output on the 803 repeater?
Oh, sorry....might have got you wrong.
Here's the repeater's ifconfig:
root@Hacker-3:~# ifconfig
br-lan Link encap:Ethernet HWaddr 00:00:83:89:D2:00
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::200:83ff:fe89:d200/64 Scope:Link
inet6 addr: fd25:9f54:184::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5618 errors:0 dropped:0 overruns:0 frame:0
TX packets:5498 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:583928 (570.2 KiB) TX bytes:1389605 (1.3 MiB)
eth0 Link encap:Ethernet HWaddr 00:00:83:89:D0:00
inet6 addr: fe80::200:83ff:fe89:d000/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:47541 (46.4 KiB)
eth0.1 Link encap:Ethernet HWaddr 00:00:83:89:D0:00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:46503 (45.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:24204 errors:0 dropped:0 overruns:0 frame:0
TX packets:24204 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1645860 (1.5 MiB) TX bytes:1645860 (1.5 MiB)
nas0 Link encap:Ethernet HWaddr 00:00:01:00:00:00
inet6 addr: fe80::200:1ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:3 dropped:0 overruns:3 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:328 (328.0 B)
wlan0 Link encap:Ethernet HWaddr 00:0C:43:30:60:00
inet6 addr: fe80::20c:43ff:fe30:6000/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5618 errors:0 dropped:0 overruns:0 frame:0
TX packets:5498 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:662580 (647.0 KiB) TX bytes:1532314 (1.4 MiB)You need 2 wifi interfaces on the repeater with different MAC addresses, you have just one.
If you post the wireless config of the repeater, I can check, what has to be added.
Ok, well that's something I don't understand, I must admit.
Left side is the 802 repeater (which works!) and right side is the 803 (which doesn't work properly)
config wifi-device 'radio0' config wifi-device 'radio0'
option type 'mac80211' option type 'mac80211'
option hwmode '11ng' option hwmode '11ng'
option path 'pci0000:00/0000:00:0e.0' option path 'pci0000:00/0000:00:0e.0'
option channel '6' option channel '6'
option country 'US' option txpower '30'
option txpower '30' option htmode 'HT40'
option htmode 'HT40' option country 'US'
config wifi-iface config wifi-iface
option device 'radio0' option device 'radio0'
option macaddr '00:0c:43:28:60:00' option macaddr '00:0C:43:30:60:00'
option network 'lan' option network 'lan'
option ssid 'HackerMaster' option ssid 'HackerMaster'
option mode 'sta' option mode 'sta'
option wds '1' option wds '1'
option encryption 'psk2' option encryption 'psk2'
option key 'noneofyourbusiness' option key 'noneofyourbusiness'
option bssid '00:0C:43:30:62:00' option bssid '00:0C:43:30:62:00'Ok, well that's something I don't understand, I must admit.
Left side is the 802 repeater (which works!) and right side is the 803 (which doesn't work properly)config wifi-device 'radio0' config wifi-device 'radio0' option type 'mac80211' option type 'mac80211' option hwmode '11ng' option hwmode '11ng' option path 'pci0000:00/0000:00:0e.0' option path 'pci0000:00/0000:00:0e.0' option channel '6' option channel '6' option country 'US' option txpower '30' option txpower '30' option htmode 'HT40' option htmode 'HT40' option country 'US' config wifi-iface config wifi-iface option device 'radio0' option device 'radio0' option macaddr '00:0c:43:28:60:00' option macaddr '00:0C:43:30:60:00' option network 'lan' option network 'lan' option ssid 'HackerMaster' option ssid 'HackerMaster' option mode 'sta' option mode 'sta' option wds '1' option wds '1' option encryption 'psk2' option encryption 'psk2' option key 'noneofyourbusiness' option key 'noneofyourbusiness' option bssid '00:0C:43:30:62:00' option bssid '00:0C:43:30:62:00'
I do not know why it works with 802, but I know how I configured it with both 803s.
Just add the additional device with:
config wifi-iface
option device 'radio0'
option macaddr '00:0C:43:30:60:11'
option mode 'ap'
option wds '1'
option network 'lan'
option ssid 'HackerMaster'
option encryption 'psk2'
option key 'noneofyourbusiness'Sorry, but that seems to break everything:
The second device can't be activated, encryption is no longer visible and the repeater is inaccessible on wireless. I'm helpless now...asking myself if something with my image could be wrong, but then the AP has exactly that image and it's working flawlessly.
In addition to that I have tried a number of different attempts with other images and whenever I wanted STA and AP on identical devices the attempt failed. Still, I can't see why this should work on your boxes.
Thanks for your help for now.
a) You should really start your own thread since this is a wireless misconfiguration issue and nothing to do with the Arcor EasyBox
b) Your problem as stated above, is you are using duplicate MAC addresses where you shouldn't. You should remove *all* option macaddr and option bssid directives from both router's wireless configuration files and start again.
Some questions still remain. It might be really the best to start from the beginning, do the configuration step by step and discuss this in a seperate thread.
(Last edited by puma14 on 28 Jul 2014, 17:34)
Just for Information: Building my own image solved all my problems we have discussed before...
Thx @all for your help
That's good. After trying and playing with prebuild images it is the best way.
I made the same expierence, building own images solves a lot of things and it leads to more independency.
I can't find any uboot in trunk or BB download section.
Is this uboot the best choice atm for latest barrier breaker releases?
https://forum.openwrt.org/viewtopic.php … 24#p240324
Does it provide httpd to upload a full image?
How do you get uboot loaded into memory or written to flash?
When i try to erase "[1] configuration" (for testing) in BRN nothing happens. Just the command line appears again. Also when i try to flash area [1].. again, just the command line appears. Is write protection or something causing this?
2) How do you upload uboot-brn to memory? There is no 'sx' binary (for xmodem transfer) in Arch Linux. Where is that coming from? Alternatively, i tried Windows ExtraPuTTY with xmodem support but it brakes with 'user abort' every time when i initiate xmodem send.
My theory so far is to delete area [0] and [1] in BRN (bootloader and configuration, 128KB + 512KB) and then flash uboot (that is greater than 128KB) and then boot up uboot to look what options are there to upload the squashfs image.
But i'm stuck at getting uboot on the device or in memory (as 2nd bootloader)... any ideas?
(Last edited by HectoPascal on 14 Oct 2014, 23:15)
Alternatively, i tried Windows ExtraPuTTY with xmodem support but it brakes with 'user abort' every time when i initiate xmodem send.
I had problems with ExtraPUTTY, but I do not remember which. Therefore I used Tera Term. It works also with Win7.
I didn't get ExtraPuTTY running in the end either but fortunately i finally found sx. Its in the 'lrzsz' package available for most distros and then it all worked flawlessly.
I did everything in UBoot as the original bootloader didn't allow me to do anything. I couldn't erase or write to flash memory at all. But on uboot-brn i could flash real uboot and from there the squashfs image via loady and then Barrier Breaker was alive. Thanks to @snk for providing proper uboot stubs.
(Last edited by HectoPascal on 17 Oct 2014, 21:16)
'Failsafe' mode doesn't work properly on @snk's uboot. The led blinks (when using 'wifi' button) but there's no response on any ethernet port. I had to solder serial connection again and do a 'firstboot'. I guess its because only the 1st phy port is enabled but its n/c on this board. Uboot should use the 2nd port.
Can someone compile a fixed version?
Edit: Not sure.. there are other routers that need an additional button press or something after the initial led blinking (so it blinks even faster). Unfortunately, i haven't had the serial console attached at that point to look that up more in-depth. Fortunately, i've found another method to recover the device if stuck. The (needle pin) 'reset' button does work in stock configuration. 1sec for soft reset and >5sec for hard reset (flush /overlay). That should bring you back on track.
Most buttons are not recognized but the 'wifi' one is. Create a 'wps' file in /etc/rc.button and edit as you like.
(Last edited by HectoPascal on 30 Oct 2014, 23:21)
I have an 3G Stick (Huawei E1750C). It works in the side and back USB port but not in the 3G dedicated top port even though the modems /dev/ttyUSB0,1,2 are present and set up as 'modem mode'. Everything looks identical as used in working ports but when trying to bring the 3g interface up nothing happens. Logs just say 'bringing up device' or don't show any error at all. But nothing happens.
Any ideas what could be wrong or how to debug that?
Btw, my 'RT2860.eeprom' (wlan) was empty as well (0xFF). I had to extract the firmware from original backup and byte swap it. After that WiFi worked properly. Again, thanks @snk.
(Last edited by HectoPascal on 7 Dec 2014, 22:59)