1.5.9. client-bridge-repeater

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
sly
Posts: 23
Joined: Thu Nov 18, 2010 4:59 pm
Location: Croatia

1.5.9. client-bridge-repeater

Post by sly »

Installed this 1.9.5. experimental build on my WZR-HP-G300NH and I have noticed few things not working.
SITUATION:
Primary router is wifi adsl router (PPPoE client) - 10.3.2.1/24
WZR is (client-bridge-repeater to primary) - 10.3.2.2/24 - GW/DNS -> 10.3.2.1
1) from WZR console cannot ping neither the primary router or NET?
2) DHCP and DNS resolution is not working for wired/wifi clients connected to WZR,
3) if I set on my laptop (wired to WZR) the correct IP addres the NET is OK...
4) ntp is not working too?

NOTE: ALL that is working on last 1.4.7 stable build (no single issue).

How can I help more?

pbix
Developer
Posts: 1373
Joined: Fri Aug 21, 2009 5:09 pm

Re: 1.5.9. client-bridge-repeater

Post by pbix »

I tried to duplicate your results without success.

Connection is good, pings are good. Screen shots below.
router.jpg
router.jpg (103.41 KiB) Viewed 3972 times
  • login as: root
    root@192.168.2.2's password:


    BusyBox v1.19.4 (2013-01-03 08:17:10 EST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    ------------------------------------------------------------------
    | _____ _ |
    | | __ \ | | |
    | | | \/ __ _ _ __ __ _ ___ _ _| | ___ |
    | | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \ |
    | | |_\ \ (_| | | | (_| | (_) | |_| | | __/ |
    | \____/\__,_|_| \__, |\___/ \__, |_|\___| |
    | __/ | __/ | |
    | |___/ |___/ |
    | |
    |----------------------------------------------------------------|
    | Gargoyle version 1.5.9 | OpenWrt Attitude Adjustment branch |
    | Gargoyle revision f73df29 | OpenWrt revision r34879 |
    | Built January 03, 2013 | Target ar71xx/usb_large |
    ------------------------------------------------------------------
    root@Gargoyle:~# ifconfig
    br-lan Link encap:Ethernet HWaddr 02:24:A5:AF:FF:64
    inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:791 errors:0 dropped:0 overruns:0 frame:0
    TX packets:638 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:79687 (77.8 KiB) TX bytes:374348 (365.5 KiB)

    eth0 Link encap:Ethernet HWaddr 00:24:A5:AF:FF:63
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:121 errors:0 dropped:0 overruns:0 frame:0
    TX packets:202 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:16345 (15.9 KiB) TX bytes:26391 (25.7 KiB)
    Interrupt:4

    eth0.1 Link encap:Ethernet HWaddr 00:24:A5:AF:FF:63
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:114 errors:0 dropped:0 overruns:0 frame:0
    TX packets:201 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:13576 (13.2 KiB) TX bytes:24544 (23.9 KiB)

    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:5 errors:0 dropped:0 overruns:0 frame:0
    TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:429 (429.0 B) TX bytes:429 (429.0 B)

    wlan0 Link encap:Ethernet HWaddr 00:24:A5:AF:FF:63
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:261 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:32
    RX bytes:0 (0.0 B) TX bytes:37311 (36.4 KiB)

    wlan0-1 Link encap:Ethernet HWaddr 02:24:A5:AF:FF:64
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:716 errors:0 dropped:0 overruns:0 frame:0
    TX packets:694 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:32
    RX bytes:88817 (86.7 KiB) TX bytes:396246 (386.9 KiB)

    root@Gargoyle:~# ping 192.168.2.1
    PING 192.168.2.1 (192.168.2.1): 56 data bytes
    64 bytes from 192.168.2.1: seq=0 ttl=64 time=1.435 ms
    64 bytes from 192.168.2.1: seq=1 ttl=64 time=1.390 ms
    ^C
    --- 192.168.2.1 ping statistics ---
    2 packets transmitted, 2 packets received, 0% packet loss
    round-trip min/avg/max = 1.390/1.412/1.435 ms
    root@Gargoyle:~# ping http://www.google.com
    PING http://www.google.com (173.194.73.106): 56 data bytes
    64 bytes from 173.194.73.106: seq=0 ttl=47 time=51.331 ms
    64 bytes from 173.194.73.106: seq=1 ttl=47 time=51.118 ms
    ^C
    --- http://www.google.com ping statistics ---
    2 packets transmitted, 2 packets received, 0% packet loss
    round-trip min/avg/max = 51.118/51.224/51.331 ms
    root@Gargoyle:~#
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM

sly
Posts: 23
Joined: Thu Nov 18, 2010 4:59 pm
Location: Croatia

Re: 1.5.9. client-bridge-repeater

Post by sly »

@pbix
Thanks for the effort, after 3,4 hours of flashing/reflashing/reconfiguring the 1.5.9. experimental buid started to functioning as it should in the frst try...

Question: Is this output power level normal (webUI-cannot change), I think it is too high and why the iwconfig report different power level?

Image

Code: Select all

root@Gargoyle:~# iwconfig wlan0-1
wlan0-1   IEEE 802.11bgn  ESSID:"OSNOVNA"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:26:44:77:1E:02
          Bit Rate=54 Mb/s   Tx-Power=17 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=57/70  Signal level=-53 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:8  Invalid misc:8540   Missed beacon:0

root@Gargoyle:~#

sly
Posts: 23
Joined: Thu Nov 18, 2010 4:59 pm
Location: Croatia

Re: 1.5.9. client-bridge-repeater

Post by sly »

@pbix can you plase recheck?

I have found a bug within this build...

SITUATION (as before):
Primary router is wifi adsl router (PPPoE client) -> 10.3.2.1/24
WZR-HP-G300NH (buffalo) is (client-bridge-repeater to primary) -> 10.3.2.2/24 with -> GW/DNS -> 10.3.2.1
Wired to buffalo is dreambox (linux STB)
my laptop is wireless client to buffalo and both of them can get to NET via DHCP/DNS, so far so good.

BUG DESCRIPTION:
Dreambox is not accessible from my laptop???
If my laptop is wired to buffalo then dreambox is accessible...

HELP please!!!

Post Reply