Page 4 of 4 FirstFirst ... 234
Results 46 to 54 of 54

Thread: Firmware v1.9.2.7 CR1 [Oleg]

  1. #46
    Join Date
    Oct 2004
    Location
    Portugal
    Posts
    145

    Unhappy

    Quote Originally Posted by piri
    hmmm, tried both tkip and aes only, but didn't work....
    only when unhiding SSID with those settings you can connect, but without a password (i.e. no encryption at all!!!) - seems that the whole wpa encryption is broken....

    strangs that only I seem to have this problem - no other people out there using wpa-psk?
    I have this problem to!! with the whole wpa
    Home Page
    Marco Sousa from PORTUGAL
    [ WL-500g - fw: 1.9.2.7-7e [Oleg] | WL-500gP - fw: 1.9.2.7-7f-USB-1.63 [Oleg&koppel.cz] ]

  2. #47
    Join Date
    Dec 2004
    Location
    Skopje, Macedonia
    Posts
    13

    scp yes - ssh no

    Strange thing..it appears that scp is present in the firmware, but ssh lacks. So because scp cannot work without ssh, it is a waste of space to hold it, but it would also be nice if it worked too .
    "What's the color of a chameleon put onto a mirror?" - Stewart Brand.

  3. #48
    Join Date
    Dec 2003
    Location
    Russian Federation
    Posts
    8,353
    Quote Originally Posted by chupra
    Strange thing..it appears that scp is present in the firmware, but ssh lacks. So because scp cannot work without ssh, it is a waste of space to hold it, but it would also be nice if it worked too .
    You just need to start scp from the PC, not from the wl500g itself.

  4. #49

    Question Bridge - changing topology?

    Quote Originally Posted by Oleg
    Mine logs:
    Code:
    Jan  1 03:00:02 kernel: br0: port 2(eth2) entering forwarding state
    Jan  1 03:00:02 kernel: br0: topology change detected, propagating
    Jan  1 03:00:02 kernel: br0: port 1(eth0) entering forwarding state
    Jan  1 03:00:02 kernel: br0: topology change detected, propagating
    So, looks like this a part of propag-ating.

    Hello Oleg,

    since I upgrade FW to 1.9.2.7-3b, my syslog is filling with these messages from Bridge:

    Code:
    Jan 17 11:57:03 kernel: br0: received tcn bpdu on port 1(eth0)
    Jan 17 11:57:03 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 11:57:05 kernel: br0: received tcn bpdu on port 1(eth0)
    Jan 17 11:57:05 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 11:57:07 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:07 kernel: br0: received tcn bpdu on port 1(eth0)
    Jan 17 11:57:07 kernel: br0: topology change detected
    Jan 17 11:57:09 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:11 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:13 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:15 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:17 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:19 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:21 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:23 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:25 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:28 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:57:28 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 11:57:30 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:31 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:57:31 kernel: br0: topology change detected
    Jan 17 11:57:32 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:57:32 kernel: br0: topology change detected
    Jan 17 11:57:32 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:34 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:35 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:57:35 kernel: br0: topology change detected
    Jan 17 11:57:36 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:38 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:57:38 kernel: br0: topology change detected
    Jan 17 11:57:38 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:40 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:41 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:57:41 kernel: br0: topology change detected
    Jan 17 11:57:42 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:44 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:57:46 kernel: br0: retransmitting tcn bpdu
    Jan 17 11:58:10 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 11:58:10 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:45:43 kernel: br0: received tcn bpdu on port 1(eth0)
    Jan 17 12:45:43 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:45:45 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:45:47 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:12 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:12 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:46:13 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:13 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:46:15 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:15 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:15 kernel: br0: topology change detected
    Jan 17 12:46:17 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:17 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:46:19 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:19 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:19 kernel: br0: topology change detected
    Jan 17 12:46:21 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:23 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:24 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:24 kernel: br0: topology change detected
    Jan 17 12:46:25 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:26 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:26 kernel: br0: topology change detected
    Jan 17 12:46:27 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:29 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:29 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:29 kernel: br0: topology change detected
    Jan 17 12:46:31 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:32 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:32 kernel: br0: topology change detected
    Jan 17 12:46:33 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:34 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:34 kernel: br0: topology change detected
    Jan 17 12:46:35 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:36 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:36 kernel: br0: topology change detected
    Jan 17 12:46:37 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:37 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:37 kernel: br0: topology change detected
    Jan 17 12:46:39 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:40 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:46:40 kernel: br0: topology change detected
    Jan 17 12:46:41 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:43 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:45 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:46:47 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:47:12 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:47:12 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:47:13 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:47:13 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 12:47:14 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:47:14 kernel: br0: topology change detected
    Jan 17 12:47:15 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:47:16 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:47:16 kernel: br0: topology change detected
    Jan 17 12:47:17 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:47:18 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:47:18 kernel: br0: topology change detected
    Jan 17 12:47:19 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:47:21 kernel: br0: retransmitting tcn bpdu
    Jan 17 12:47:43 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 12:47:43 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 21:25:31 kernel: br0: received tcn bpdu on port 1(eth0)
    Jan 17 21:25:31 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 21:25:33 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:02 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:02 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 21:26:02 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:02 kernel: br0: topology change detected
    Jan 17 21:26:04 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:06 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:08 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:10 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:12 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:14 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:16 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:18 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:20 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:22 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:24 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:26 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:28 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:28 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 21:26:30 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:31 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:31 kernel: br0: topology change detected
    Jan 17 21:26:32 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:33 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:33 kernel: br0: topology change detected
    Jan 17 21:26:34 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:37 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:37 kernel: br0: topology change detected, sending tcn bpdu
    Jan 17 21:26:39 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:39 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:39 kernel: br0: topology change detected
    Jan 17 21:26:41 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:41 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:41 kernel: br0: topology change detected
    Jan 17 21:26:43 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:43 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:43 kernel: br0: topology change detected
    Jan 17 21:26:45 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:45 kernel: br0: received tcn bpdu on port 3(wds0.49156)
    Jan 17 21:26:45 kernel: br0: topology change detected
    Jan 17 21:26:47 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:49 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:51 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:53 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:55 kernel: br0: retransmitting tcn bpdu
    Jan 17 21:26:57 kernel: br0: retransmitting tcn bpdu
    There is several WL500g connected to this one in WDS mode.
    Operation mode is set to Router, but no routing is currently used (WAN interface isn't connected).
    During this, WLAN hardly respond to ping for about 2 minutes. After then, everything works well (as before).

    I have also several WL500g running FW 1.7.5.9-5 in similar setup and there is no such messages in the syslog as there are no blackouts with continuous ping.

    What's wrong?

  5. #50

    Bridge

    Forgot to add bridge configuration:

    Code:
    brctl showbr br0
    br0
     bridge id              8000.00112fde2120
     designated root        8000.00112f90e834
     root port                 5                    path cost                100
     max age                  20.00                 bridge max age            20.00
     hello time                2.00                 bridge hello time          2.00
     forward delay             0.00                 bridge forward delay       0.00
     ageing time              42.30                 gc interval                4.00
     hello timer               0.00                 tcn timer                  0.00
     topology change timer     0.00                 gc timer                   3.74
     flags
    
    
    eth0 (1)
     port id                8001                    state                   forwarding
     designated root        8000.00112f90e834       path cost                100
     designated bridge      8000.00112fde2120       message age timer          0.00
     designated port        8001                    forward delay timer        0.00
     designated cost         100                    hold timer                 0.66
     flags
    
    eth2 (2)
     port id                8002                    state                   forwarding
     designated root        8000.00112f90e834       path cost                100
     designated bridge      8000.00112fde2120       message age timer          0.00
     designated port        8002                    forward delay timer        0.00
     designated cost         100                    hold timer                 0.66
     flags
    
    wds0.49156 (3)
     port id                8003                    state                   forwarding
     designated root        8000.00112f90e834       path cost                100
     designated bridge      8000.00112fde2120       message age timer          0.00
     designated port        8003                    forward delay timer        0.00
     designated cost         100                    hold timer                 0.66
     flags
    
    wds0.49154 (4)
     port id                8004                    state                   forwarding
     designated root        8000.00112f90e834       path cost                100
     designated bridge      8000.00112fde2120       message age timer          0.00
     designated port        8004                    forward delay timer        0.00
     designated cost         100                    hold timer                 0.66
     flags
    
    wds0.49155 (5)
     port id                8005                    state                   forwarding
     designated root        8000.00112f90e834       path cost                100
     designated bridge      8000.00112f90e834       message age timer          0.66
     designated port        8004                    forward delay timer        0.00
     designated cost           0                    hold timer                 0.00
     flags
    
    wds0.49153 (6)
     port id                8006                    state                   forwarding
     designated root        8000.00112f90e834       path cost                100
     designated bridge      8000.00112fde2120       message age timer          0.00
     designated port        8006                    forward delay timer        0.00
     designated cost         100                    hold timer                 0.66
     flags

  6. #51
    Pekr--try a more recent firmware, like 1.9.2.7-3c or 1.9.2.7-4. I think I read something previously about there being annoying debug messages in one of the earlier firmwares, and this might be one of them.

  7. #52
    tomilius:
    Thanks for tip, I will try.

    To be more specific - I haven't problem with these messages but with link unavailability during these 'topology changes'. Last time it took about 15 minutes.

    Now I've try to disable STP:

    Code:
    brctl stp br0 disable
    Seems to help so far...

  8. #53
    Join Date
    Dec 2003
    Location
    Russian Federation
    Posts
    8,353
    Code:
    nvram set lan_stp=0
    nvram commit

  9. #54

    Bridge STP disabled

    Quote Originally Posted by Oleg
    Code:
    nvram set lan_stp=0
    nvram commit
    After few days with:
    Code:
    brctl stp br0 disable
    everything looks good (no error at any AP).

    Thanks for nvram setting Oleg!

Page 4 of 4 FirstFirst ... 234

Similar Threads

  1. Firmware v1.9.2.7 CR2 [Oleg]
    By Oleg in forum WL-500g Firmware Releases
    Replies: 64
    Last Post: 11-01-2005, 18:22
  2. Firmware v1.7.5.9 CR2 [Oleg]
    By Oleg in forum WL-500g Firmware Releases
    Replies: 38
    Last Post: 06-10-2004, 08:12
  3. Firmware v1.7.5.6 CR2 [Oleg]
    By Oleg in forum WL-500g Firmware Releases
    Replies: 37
    Last Post: 05-05-2004, 03:10
  4. Firmware v1.7.5.6 CR2.1 [Oleg]
    By Antiloop in forum WL-500g Firmware Releases
    Replies: 18
    Last Post: 03-05-2004, 11:13
  5. Firmware v1.7.5.6 CR1 [Oleg]
    By Antiloop in forum WL-500g Firmware Releases
    Replies: 15
    Last Post: 07-04-2004, 17:22

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •