1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Real Client/Bridge mode solution found ...

Discussion in 'DD-WRT Firmware' started by MBChris, Jul 1, 2005.

  1. MBChris

    MBChris Network Guru Member

    @all

    searching for a Real Client/Bridging mode i found a solution at AnandTech Forum with ONE minimal issue

    at first the Link AnandTech Forum Link

    and now the post i tried and ..... what can i say .... its the REAL client/Bridge mode

    The only issue is .... how can i administer this Bridge remotely ? Local over the LAN-Ports no problem, i get the admininterface ... but how to do it remotely ? Could it be if we assign a second IP-Addr (production net) to the bridge ?

    greets Chris
     
  2. joebloggs

    joebloggs Network Guru Member


    Have you been able to successfully pull this off? If yes, that's wonderful as I can still return the WET I bought. How do you telnet a router? Thanks.
     
  3. MBChris

    MBChris Network Guru Member

    @joebloggs

    yes it worked, but only one thing i dont find out sofar, How i could control this bridge/client remotely. Wired no problem.

    How to telnet ??

    telnet 192.168.1.1

    greets
    Chris
     
  4. joebloggs

    joebloggs Network Guru Member


    When I type that into "run," a black DOS looking screen pops up and then disappears. What am I doing wrong?
     
  5. Thibor

    Thibor Super Moderator Staff Member Member

    try typing "cmd", in run first
    then your telnet command
     
  6. hotrat

    hotrat Network Guru Member

    gday mate

    have u found it will work with more than one client behind it?

    regards
    Chris
     
  7. joebloggs

    joebloggs Network Guru Member

    Thanks for the help everyone. It works beautifully now. And yes, works with more than one computer behind it. The only thing I note is that it's a little slower than the WET54GS5 in terms of first connecting to it. It seems like the negotiation with the WRT is slower and less stable than the more expensive official WET. But I think I can live with this.
     
  8. joebloggs

    joebloggs Network Guru Member

    I just realized that eventhough with the command that we telnet into the router, the changes are not reflected in the GUI when we log into the router. Anyone have this same experience?
     
  9. XCOM7

    XCOM7 Network Guru Member

    You will not see any changes in the GUI since they where madein the CLI.
     
  10. joebloggs

    joebloggs Network Guru Member


    Does this mean that any changes made in CLI will not be saved after a power off or reboot?
     
  11. RTSAnime

    RTSAnime Network Guru Member

    has anyone gotten this to work with WPA-PSK. I tried but unfortunately could not. I did "wl join MySSID key MyWPAKey amode wpapsk". Any suggestions?
     
  12. MBChris

    MBChris Network Guru Member

    YES, more than one Client behind is possible, i aggree that ! But .... anyone get the "Remote" administration working for that ?

    Greets
    Chris
     
  13. Thibor

    Thibor Super Moderator Staff Member Member

    is windows network neighbourhood working, or is network browsing by IP only?
    are machines behind client on the same subnet as AP?
     
  14. MBChris

    MBChris Network Guru Member

    Windows network Browsing i didnt test, but the PCs behind getting the DHCP-Addresses from the main-ap and they ARE in the same subnet than !
     
  15. kkennedy070790

    kkennedy070790 Network Guru Member

    Actually I should change that - you can give the router IP one in your regular network (just make sure it is not in the DHCP scope on your router..).

    ie: Main router ip: 192.168.7.1 dhcp scope: 192.168.7.100 to 192.168.7.150

    Wrt54 ip: 192.168.7.2

    Temporarily set your nic to 192.168.7.3, follow my previous directions, set local nic back to dhcp.

    Then you can telnet or Web admin to your wrt54 at 192.168.7.2

    btw: yes Windows network browsing works with this setup, yes multiple computers work, yes the main router can be any manufacturer (I have a D-Link DI-524), and I have not figured out how to make it work with any type of security turned on as yet.. (I'll let you know if I do...)

    Kenny
     
  16. Thibor

    Thibor Super Moderator Staff Member Member

    RE: Actually I should change that - you can give the router IP one in your regular network (just make sure it is not in the DHCP scope on your router..).

    ie: Main router ip: 192.168.7.1 dhcp scope: 192.168.7.100 to 192.168.7.150

    Wrt54 ip: 192.168.7.2

    Would that be the Router's Local IP, or WAN ip?
     
  17. dellsweig

    dellsweig Network Guru Member

    Great find

    This works great!! Simple to setup.

    Now, what file do I need to put thise commands in to get them to execute at boot time on DD-WRT 2.2 final. There must be a non-volitile startup script I can use for this.... HyperWRT had the capability to create startup scripts via the gui - does that exist in DD-WRT - matby by directly executin some html somewhere??

    Note: This solution should work fine in ANY firmware that supports telnet or ssh access into the WRT54G. I just tried this with hyperWRT and it worked fine, I have it running in DD-WRT and I assume any flavour of Svesoft would work as well.

    This is true L2 bridging. No routing across subnets are required.

    Pretty Cool
     
  18. MBChris

    MBChris Network Guru Member

    Hi Kenny, nice to meet you (the client/bridge/god) here :))
    Ill try that in the evening .... hoping its also smooth as your directions !

    @dellsweig regarding your question, why not modify nvram/rc_startup. Shouldnt you know that ? (sorry, not tried yet but think it does the trick)

    greets
    Chris
     
  19. Thibor

    Thibor Super Moderator Staff Member Member

    All done, smb browsing(windows network neighbourhood) by name, upnp, and dhcp from main router working wonderfully. Thanks be to Kenny!!!
    i set variables to rc_startup, that's all that needs to be done for it to be rebootable.
    rc_startup="wl ap 0; wl wet 1; wl join $SSID"

    and that's it
     
  20. dellsweig

    dellsweig Network Guru Member

    Brainslayer

    How about adding this to the GUI???
     
  21. hotrat

    hotrat Network Guru Member

    ANY ideas anyone on the wl commands required to join wpa protected ap with this bridging solution??

    Regards chris
     
  22. kkennedy070790

    kkennedy070790 Network Guru Member

    The router's local IP, with this config, the WAN port is not used.
     
  23. joebloggs

    joebloggs Network Guru Member


    What is this rc_startup thing? I'm also looking for a way to make the settings less volatile. Seems like any changes I make to the router resets everything.
     
  24. MBChris

    MBChris Network Guru Member

    Hi Joe, this changes are not done with the gui, so they cant be stored with the gui and they are lost every time when u change something in the gui. For the rc_startup thing ... the router MUST be rebootet.

    Am i right Kenny ????
     
  25. kkennedy070790

    kkennedy070790 Network Guru Member

    dunno about the god part! - After giving this a great deal of thought - I do not think any type of security will work with this setup, every mac address coming through the bridge would have to be encrypted - we need a special kernel to do that I think, or possibly some type of agent running on wrt to take care of each connected client. If you look at your main router with encryption turned off, you will see that the incoming wireless clients through the wrt are tagged with the mac address of the connecting nic - not the wrt's!
     
  26. MBChris

    MBChris Network Guru Member

    ...but I need this, i wanna know exactly which machine behind the bridge is consuming this amount of traffic, so i could treat my client-user :))

    WEP is working ... WPA dont know, also dont know if Radius would work ?!?!?
     
  27. hotrat

    hotrat Network Guru Member

    gday mate
    can you please tell me the steps you took to get wep working thanks

    Chris
     
  28. MBChris

    MBChris Network Guru Member

    for sure
    Code:
    wl join Your_SSID "your_key" 
    and of course the wl ap 0 and wl wet 1 thing
     
  29. hotrat

    hotrat Network Guru Member

    ta for that mate

    really this topic should be condensed into one post wif all the info as a sticky maybe???

    chris
     
  30. kkennedy070790

    kkennedy070790 Network Guru Member

    I got WEP to work also - no WPA-PSK though. I think the WEP part is being handled directly by the hardware, maybe I am just missing something...
     
  31. kkennedy070790

    kkennedy070790 Network Guru Member

    Yep, after you have telneted into your wrt, you can save the startup by doing a command like:

    ~ # nvram set rc_startup="wl ap 0;wl wet 1; wl join <SSID> [WEP key"
    ~ # nvram commit

    that will force those commands to be run between resets..

    Kenny
     
  32. joebloggs

    joebloggs Network Guru Member


    Wow, I'll try that when I get home. If this means that I won't have to type those commands in each time, it would be wonderful. .... If I want to stop those commands from running after each resets or clear the nvram, what would those commands be?
     
  33. sabre

    sabre Network Guru Member

    edit--What is the basic setup status?: auto configuration-DCHP or static IP (which comes up w/ mainly invalid IP) or disabled? and then in DCHP settings, do we enable it after doing the telnet?

    I am trying to do this w/ Freeman 1.04. I assume it should be possible, but have to find some settings under different headings. However, my concern is that the default settings may be different than DD-WRT.

    Also, Kenny, I saw in another post that you are using this with HyperWRT. It seemed like similar HOWTO. Do you find it to have the best connection speeds with HyperWRT, or with DD-WRT? Thanks all.
     
  34. joebloggs

    joebloggs Network Guru Member

    Please help, I got the nvram to commit to an access point even after a power reset with the command given by Kenny. I've tried "nvram erase; reboot" to erase this commitment but it seems like it does not get erased and is still committed to an AP each time it is rebooted. Does anyone know how I can give my router a clean slate to begin anew again. Thank you.
     
  35. MBChris

    MBChris Network Guru Member

    Hi Joe, do a HardReset (30 sec. Resetbutton) and Powercycle 2 times
    this would do the trick
     
  36. dellsweig

    dellsweig Network Guru Member

    Why not just save a blank string in the rc_startup nvram variable??
     
  37. joebloggs

    joebloggs Network Guru Member

    Thanks Chris. Are you doing a hard reset and cycle after you erase the nvram? Or is there no need to erase the nvram at all using your method?

    Dellsweig, I'm not too familiar with these commands, so are you saying that we should type in what Kenny a few posts above and leave the variables blank and make the router commit to that?
     
  38. dellsweig

    dellsweig Network Guru Member

    Joe

    If you set a value in a variable and commit it to nvram, then that value is persistent through reboot and power cycles. If you want to 'erase' only that value - remember, there are MANY nvram variables, simply save a blank entry to that variable and commit it. This way you do not need to reset ALL the variables as when you do a hard reset
     
  39. kkennedy070790

    kkennedy070790 Network Guru Member

    I just leave the internet side set to automatic, but it really does not matter much - that interface is not used at all in this configuration. Dunno about Freeman. I messed with HyperWRT a little (was looking for a way to save the commands). HyperWRT has an editable startup script on the administration tab, which is handy for running the commands. DD-WRT has the rc_startup nvram variable. I did not see any difference in performance or range between Hyper and DD. DD-WRT's interface "feels" faster, and seems to reset quicker...
     
  40. sabre

    sabre Network Guru Member

    Steps taken, but no go

    Ok, perhaps someone can look over and tell me what I am missing (using WRT54G 2.2):

    *I flashed to DD-WRT pre5 firmware
    *Set to factory defaults and reset
    *On basic setup page:
    disabled STP
    set local IP to 192.168.1.200 (my main router IP is 192.168.1.1; DHCP range 2-51)
    disabled DHCP server
    *Wireless mode: AP, mixed, put SSID same as main router, set channel 3 (same as main router), kept broadcast on
    *Admin tab - enable Telnet
    I made no other changes to any settings
    *Reboot router
    *Under TCP/IP of ethernet card, set fixed IP to 192.168.1.250
    *Telnet to WRT router
    *Login as root/admin pw
    ~#wl ap 0
    ~wl wet 1
    ~wl join My SSID (not using WEP yet)
    [see below]
    *Put back ethernet card TCP/IP to automatic

    After this, I see that the main router (netgear WGR614v5) shows the PC connected to the WRT as attached (although it appears erratic), but I am unable to get internet connection. I am also unable to ping the netgear router, other PCs on the netgear router and dont have any other functionality. Any ideas? Thanks

    []To make this script run at startup, I then would run nvram line in Telnet.
     
  41. kkennedy070790

    kkennedy070790 Network Guru Member

    Re: Steps taken, but no go

    Wow - good catch sabre - you must set your internet connection to "Disabled" or to automatic configuration - DHCP. IF you set a static IP address for your LAN under the "Internet" configuration - even if you disable it later - iptables will still be setup to firewall you off!!!! Switch back into Static and set it to a completely different LAN segment save the setting and then set it back to Disabled! (I don't know why it seems to "stick") Does anyone know how to flush the iptables settings and make it stick??

    Kenny
     
  42. sabre

    sabre Network Guru Member

    Hey kenny, can you see anything missing above.

    I am able to show the remote router or PC connected to WRT (although strange the main router keeps switching between them as showing connected), but unable to ping network or get internet connection. Do other folks have this working, and i imagine this is the best and fastest way to create the connection.
     
  43. joebloggs

    joebloggs Network Guru Member

    Besides the obvious steps taken, is this method really that much different from setting up WDS where you have to type in the MAC address of the APs? Or is this essentially the same as WDS without the troubles that one would have to go through?
     
  44. kkennedy070790

    kkennedy070790 Network Guru Member

    Yes they do have it working ( me too obviously)
    2 things to make sure of:

    1. make sure your wireless connection is good! you can check your status after doing wl join <ssid> by typing

    ~ # wl status
    SSID: "netWork"
    Mode: Managed RSSI: -13 dBm noise: -97 dBm Channel: 7
    BSSID: xx:xx:xx:xx:xx:xx Capability: ESS WEP ShortPre ShortSlot
    Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]

    make sure your RSSI: is better than say -80 dBm
    and that you have low noise levels say -80 dBm to -99 dBm

    2. make sure you don't have left over "junk" from a previous configuration. clear the configuration for vlan1 and flush the iptables rules by doing the following:

    ~ # ifconfig vlan1 0.0.0.0 <-- removes the ipaddress from vlan1
    ~ # iptables -F <-- flushes the filter rules
    ~ # iptables -t nat -F <-- flushes the NAT rules

    Step number 2 will clear out the junk if you had previously set a static ip for your "internet"

    Kenny
     
  45. kkennedy070790

    kkennedy070790 Network Guru Member

    From what I understand about WDS, WDS will be slower - it divides your wireless bandwidth in two. This does not extend the wireless network like WDS does either, the WRT54 acts exactly the same way a WET54 does - it is a true layer-2 bridge. It is too bad that at this point there really is no way to simply switch it on in the web interface :( You don't need to play with MAC addresses or anything like that, and once you have it set, it really is plug and play - you could configure several of them the same way and have multiple multiple hardwired devices on each WRT - all talking to the same network.

    Kenny
     
  46. MBChris

    MBChris Network Guru Member

    Hi Kenny, i bet Sebastian aka Brainslayer is working on it ! Sofar we use YOUR solution ! I tried it several ways and get stucked yesterday in the evening ... nothing goes ... But now i read your suggestion about the Internet-IP which ive insert also to try :( Also the IPTABLES thing would help me out i thing .... Ill report this evening more ....

    Thanks again for this 3-liner solution
     
  47. sabre

    sabre Network Guru Member

    Thanks for the tips Kenny.

    I do get a correct wl status after putting in the parameters. But tonight I will use those other commands to try and "clean house". Any other things you can think of that may need to be done? I noticed your posting of the steps at some other sites, and you do not mention the NIC change--is this necessary, or something you learned after those posts?
     
  48. sabre

    sabre Network Guru Member

    Sorry to be a pain, but still no go.

    Does it mean anyting on this line
    Capability: ESS ShortSlot (no WEP yet)

    in your setup, along w/ WEP it showed ShortPre prior to ShortSlot-I have no ShortPre (edit-i did it again and then it did have ShortPre)

    Also, I am not using the basic version of 22.

    The funny thing is the main router shows it connected w/ the proper IP address, but no response.
     
  49. kkennedy070790

    kkennedy070790 Network Guru Member

    I guess I would try a factory reset, and start over again..
     
  50. sabre

    sabre Network Guru Member

    ok , did all resets and tried an "nvram erase;reboot" to clean things out.

    when in telnet, i am able to ping the main router and PC connected to it. But out of telnet still unable to ping main or PC. Turned off MAC and WEP on main router, and turned on Upnp. Anything else that may be restricting access on the main router (turned off firewall on main PC). Main router still shows remote PC/router connected, but no connection.

    The reason i need this is b/c i want to set up MediaMVP to extend my PVR, and it has to be on the same subnet as the server PC. Maybe i should just hope that v23 will do it for me-but even then given my experience perhaps that will not work.
     
  51. kkennedy070790

    kkennedy070790 Network Guru Member

    If you can ping from the WRT to the main router, then you are connected. Make sure that you set the PC that you are using with the WRT back to DHCP! The DHCP server on the main router should set your IP address and default gateway. If you are setting the default gw to the WRT - it will not work (the WRT is not a router in this setup!)

    Btw: I would leave uPNP turned off on the WRT - it really serves no purpose - the WRT should remain "invisible" to windows - I have no idea what the effects might be. (Anyone care to enlighten me??)
     
  52. sabre

    sabre Network Guru Member

    Yes, the PC on the WRT has DHCP turned back on, and I am getting a proper IP address from the main router and the default gateway is the main router IP address. I turned off the uPNP on the main router, but it made no difference - i did not touch it on the WRT.

    I was able to get a good connection using an alternative setup, but not real layer 2 bridge as they are not on the same subnet.

    So close, yet so far...
     
  53. kkennedy070790

    kkennedy070790 Network Guru Member

    Wow - if you are getting a dhcp address from the main router - the setup is working - the problem you were having is obviously not the configuration on the WRT. I have a Dlink DI-524 as my main router, and the dhcp server on it would assign an address, then dump the address about 2 seconds later, then reassign it - back and forth (couldn't see this happening on the windows box), I couldn't get to the internet - etc. It turned out that the dlink didn't like the hostname of my windows box. Make sure the name of your windows pc doesn't have any spaces or punctuation of any kind. Could be that your netgear doesn't like it either. I would make sure that you can get the PC to work with a wireless adapter connected to the Netgear first! btw - I had a lot of problems with the D-link - it needed a firmware update right out of the box.

    Kenny
     
  54. hotrat

    hotrat Network Guru Member

    Does anyone have this solution running STABLE with more than 1 client computer behind the wireless bridge


    Regards
    Chris
     
  55. dellsweig

    dellsweig Network Guru Member

    Greetings

    Has anyone tried to simply set the DDWRT to ad-hoc mode via the GUI to see if it would associate with the main router using the current settings??

    This would save the need to issue the command line to set ad-hoc mode and associate with a known SSID
     
  56. kkennedy070790

    kkennedy070790 Network Guru Member

    Ad-Hoc mode breaks the bridge between the vlan1 and eth1, in order for Ad-hoc mode to work as a bridge you would need to add eth1 back into the bridge with:

    ~ # brctl addif br0 eth1

    of course, in the process you will also break your connection and will need to re-join a known SSID again anyway...

    Kenny
     
  57. sabre

    sabre Network Guru Member

    Success, for a moment.

    So i got it working (I set to remote mgmt and new pw and disabled loopback-not sure if those did it, but hey)

    So after i got it to work, i turned my WEP back on, and tried the rc_statup string in nvram. Bit i think i messed up putting in the key. After that, even after many fresh starts, i am not able to wl join anymore. when i try it says:
    eth1: invalid argument; and says recent associated w/ my SSID.

    Anyone know what the issue is - i tried to clear out nvram and did many hard reboots. again, so close...
     
  58. kkennedy070790

    kkennedy070790 Network Guru Member

    try adding your WEP key manually before the join:

    ~ # wl addwep 0 <WEPKEY>

    I've noticed that some of the firmware available out there are very slow starting up the bridge after the join - the new freeman has some very strange behavior when using this setup ( you have to join twice - dunno why)
     
  59. matt11601

    matt11601 Network Guru Member

    Will this work on a domain?

    I was so happy to read that someone got this working, but I'm wondering if this will work with a windows server setup?

    What I want is for the WRT54G to just as a switch when a client connects either wirelessly or through one of the ports.

    I do not know if this helps, but here's my routing setup: The windows 2003 server handles all the DHCP connections and my actual hardwired router just connects to the cable modem.

    Will DD-WRT and this tutorial still work for me?

    -Matt
     
  60. matt11601

    matt11601 Network Guru Member

    Well I went ahead and tried to get this to work, but I am having a hard time...

    Like I said in my earlier post, Windows 2003 server handles DHCP. The address pool is 192.168.15 to 192.168.0.50 and the IP of the server itself is 192.168.0.100

    My real hardwired router is plugged into the cable modem and has an IP address of 192.168.0.1

    The only thing my real router is doing is running a DMZ for the windows server.

    My linksys wireless router (version 3) is plugged into one of the ports in my real router. Windows server is assigning an IP address of 192.168.0.18 to the linksys (which is in the address pool so linksys displays this as the WAN IP).

    I upgraded my firmware to the latest DD-WRT build. Then I did a factory reset. Then I did this:

    -turned off STP
    -turned off DHCP
    -I left the Router IP address as 192.168.1.1 because this is already outside of the address pool
    -the linksys wireless router already assigned the PC to be 192.168.1.100 as this happened before I logged into the control panel so I left DHCP turned on in my PC
    -Under Wireless I leave the settings as AP, mixed, "linksys" ssid
    -Under wireless security I have "none"
    -I reboot my wireless router
    -I run cmd on the PC
    -I run telnet 192.168.1.1
    -I do the following commands: wl ap 0 / wl wet 1 / wl join linksys
    -When I do wl status I get an error saying eth1 no associaition (or something similar to that)

    So now I am stuck. I have no clue on what to do next. Any ideas? I've got to be doing something wrong. I'm just trying to get the WRT54G to act as switch when it comes to wired and wireless clients connecting to it. That way, my windows server will just see it as another connection on the network. Anyone know what I'm doing wrong?

    Thanks in advance.

    -Matt
     
  61. sabre

    sabre Network Guru Member

    Well, i am able to get a connection w/ no WEP. For some reason i am having no luck when adding WEP commands.

    for this: wl join "MySSID" "12345...26" Do i have to add anything else after the MySSID or WEP key, such as a word or an extra number.

    for: wl addwep 0 "1234...26" do i have to add anything to this as well?

    Thanks Kenny for all the help so far. Just about there.
     
  62. hotrat

    hotrat Network Guru Member

    hmm as soon as i add MORE than 1 client behind this setup i get problems with the throughput stalling...

    ideas?? anyone had this??

    Chris
     
  63. kkennedy070790

    kkennedy070790 Network Guru Member

    I have 3 - make sure STP (Spanning Tree Protocol) is turned OFF!! It really slows the bridge to a crawl w/multiple clients!
     
  64. kkennedy070790

    kkennedy070790 Network Guru Member

    The way it worked for me:
    In the gui - set security to WEP, and enter your wep key(s)

    wl ap 0
    wl wet 1
    wl addwep 0 <my key>
    wl join <SSID> <my key>

    It seems to take my DD-WRT bridge about 30-40 seconds to come up with WEP turned on.

    Kenny
     
  65. sabre

    sabre Network Guru Member

    That did it Kenny! you are a master. I hope others can learn from the great insight here as well. And SageTV (my PVR prog) works great so far w/ the MVP.

    Thanks
     
  66. kkennedy070790

    kkennedy070790 Network Guru Member

    I don't think you are trying to do what is described in this "howto". It looks like you just need to plug the router into one of the 4 switched ports on the WRT, I think you have mistakenly plugged your router into the WAN port. Correct me if I am wrong - but I think you just want to use your WRT as a simple Access Point. Do you have 2 wireless routers??
     
  67. sabre

    sabre Network Guru Member

    Hey, do you think that the v23 of DD-WRT that Brainslayer has sneaked would have any impact on speed in this configuration. In other words, do we get any benefits by upgrading the firmware from v22 when in bridge mode? Thanks
     
  68. MBChris

    MBChris Network Guru Member

    Yes, im sure that the V23 give us more speed ! I'm at heavy testing, speed is georgous. He implemented also a "Client bridge" mode in V23 but .... haven't got running this sofar (with my short tests) but .... if its running i bet its improving our speed !
     
  69. kkennedy070790

    kkennedy070790 Network Guru Member

    hopefully it has the new nas4not WPA2 supplicant that supports this type of bridge!
     
  70. hotrat

    hotrat Network Guru Member

    This solution seems to work really well under v23 :)

    btw for those who have had problems wif WEP i have found that adding ' around the wep key sometimes helps...
    ie.

    wl ap 0
    wl wet 1
    wl join YOURSSID key 'YOURWEPKEY'

    hope it helps someone

    regards Chris
     
  71. dellsweig

    dellsweig Network Guru Member

    Has anyone tried to see if the DDwrt Alpha 23 has GUI support for bridging mode??
     
  72. hotrat

    hotrat Network Guru Member

    It has client, client bridge, adhoc

    unfortunately i couldn't get the client bridge mode working (wireless light stays off and no throughput)

    telnetting in and creating the bridge works REALLY well but!!! :)


    Chris
     
  73. dellsweig

    dellsweig Network Guru Member

    Chris

    Can you email me the v23 alpha link. I have a dedicated bridge WRT54 I can play around a bit on to see if I can come up with anything other than telnet to make this work.

    Dan
     
  74. hotrat

    hotrat Network Guru Member

    EDIT: OK HERE IS THE LATEST LINK

    http://www.dd-wrt.com/dd-wrtv2/sneaks/dd-wrt.v23-alpha.zip

    client bridge now works with WEP but NOT WPA yet, so there is now no need to telnet in :)


    Chris

    NOTE: this is alpha firmware, as BrainSlayer would probably tell u, if u dont know wot u are doing DONT USE IT
     
  75. MBChris

    MBChris Network Guru Member

    Hi all, so i started this thread ... but its obsolete now because we have the REAL Client bridging mode now in V23. Ive tested it with various scebarios and it works like a charm ! Thanks Brainslayer .... and of course kkennedy070790 for the work !

    Greets
    Chris
     
  76. BrainSlayer

    BrainSlayer Network Guru Member

    the very latest, but nas4not is only a link to nas
     
  77. hotrat

    hotrat Network Guru Member

    hey MBChris u managed to get wpa working in client bridge?

    Chris
     
  78. MBChris

    MBChris Network Guru Member

    NO, as Brainslayer wrote there is a problem with the new Linksys drivers ..... but, i bet he is able to get it working in future releases !
     
  79. BrainSlayer

    BrainSlayer Network Guru Member

    just for you information. we got wpa/wpa2 to work with some experiments. we just need to integrate the solution now
     
  80. hotrat

    hotrat Network Guru Member

    mate your the champion/legend/god of this stuff!

    Chris
     
  81. dellsweig

    dellsweig Network Guru Member

    Will this soluition work with mixed mode implementations and possibly WDS as well??
     
  82. sabre

    sabre Network Guru Member

    After setting up bridge in v22 via telnet, tried on v23 alpha via GUI. It worked sweet when using it w/ my laptop, for internet and could ping other network hardware. But, strangely it now does not work w/ my Media MVP extender (using w/ SageTV), as it did fine w/ v22. When the MVP boots up it gets to launching application, and gets stuck there. It does get past the point of getting connected to the network, so seems to be getting an IP address. Now, it would seem to be an issue other than the network, but when going back to v22 and telnet setup, it works ok w/o making another other change. Can it be somehow v23 is not truly a single network on the same subnet (that is the only way MVP will work)?
     
  83. BrainSlayer

    BrainSlayer Network Guru Member

    sorry. it is. its a real transparent bridge between the lan and the wireless lan interface. its on the same subnet and gets also dhcp leases from the ap. no special routing between the networks
     
  84. chrisbolt

    chrisbolt Network Guru Member

    Any ETA, or could you share the commands required (if it's just commands)? I'm debating between waiting for bridge+WPA support and switching to WEP (ick).
     
  85. WisdomWolf

    WisdomWolf Network Guru Member

    I couldn't ping other network hardware with v22, so I decided to try out v23 alpha with the new gui. I got the client bridge working correctly with my laptop, but I have one hiccup. I cannot get into the admin page for the WRT no matter what I do! I have tried setting myself with a static ip and even that doesn't work. The main router is 192.168.1.1, my WRT is 192.168.1.10, but I cannot even ping that. Any ideas?
     
  86. hotrat

    hotrat Network Guru Member

    Do u have the firewall disabled and also ALL the Block WAN Requests unchecked?? because the bridge is behind your main router u don't need them ON

    Chris
     

Share This Page