Lynksys modo cliente com Switch para 24 pcs

Troquei o Firmware de um WRT54G Versão 6 para DD-WRT v.26 SP1 que tem as opções de colocar o radio em modo Cliente e Cliente Bridge.

Agora é o seguinte, quero receber o sinal de um provedor de rádio com antena externa nesse WRT, e usar umas das 4 portas Lan que ele tem pra ligar um Switch de 24 portas e compartilhar a net numa lan house, alguém sabe se isso dá certo?
Resumindo: Receber o sinal pelo WRT e compartilhar via cabo com 24 máquinas.

Postado Originalmente por henriquejensen

Troquei o Firmware de um WRT54G Versão 6 para DD-WRT v.26 SP1 que tem as opções de colocar o radio em modo Cliente e Cliente Bridge.

Agora é o seguinte, quero receber o sinal de um provedor de rádio com antena externa nesse WRT, e usar umas das 4 portas Lan que ele tem pra ligar um Switch de 24 portas e compartilhar a net numa lan house, alguém sabe se isso dá certo?
Resumindo: Receber o sinal pelo WRT e compartilhar via cabo com 24 máquinas.

O que vai acontecer é que vc vai se conectar via client-bridge ao AP base e compartilhar o sinal pela LAN a partir desse seu AP local.

Postado Originalmente por mferreira

O que vai acontecer é que vc vai se conectar via client-bridge ao AP base e compartilhar o sinal pela LAN a partir desse seu AP local.

Brother, valeu pela ajuda, era isso mais ou menos que eu tinha em mente. Mas vc saberia me dizer onde vou por a chave WEP e o SSID do provedor nele? Tipo, como ficaria a configuração?

EDITADO:

Achei um tuto em espanhol que ensina a fazer essa configuração mas com firmware Alchemy da Sveasoft, creio que com o DD-WRT seja a mesma coisa.
Configuración del WRT54G como cliente bajo Alchemy 5.2.3
No final do tudo o cara disse que as faixas de IP da wireless e lan devem estar diferente senão não irá funcionar. (vou fazer uns testes quando tiver tempo)

Aqui tem outro link com mais um tuto WWW.ANDRATX.TK - ANDRATX WIRELESS

Aqui vai um tuto bem legal sobre ligação client-bridge:

Okay. After fighting a lot of with different wireless client modes I decided to concentrate and make it work. Now I'll share information to others too.

If you don't know what client-bridge is, then use search of this forum. Search also information about client-routed and WDS. I don't say this because I'd like you to waste your time in reading. Nope. I say this to actually save your time, as there are differencies between these modes and it's really slow to make these setups even when we don't need to use anything else expect graphical web interface

And also, read this message (and possibly whole thread if people write to this thread) completely before starting, if you follow these two rules, you don't need to regret that you messed up your routers and need to reset them and fully set them up again and waste your time and your nerves.

Okay, my network is little bit larger than in this setup, but I introduce you a setup with only 2 WRT's to make it simpler.

#1 10.0.0.1 Bridge [this router is about to share it's connection wirelessly]
#2 10.0.0.5 Client [this router is about to have a wireless connection to network]

Now on, I call them Bridge-router and Client-router. Let's face up some facts first.

Client-bridged mode is buggy. RJ-45 ports won't get IP if a client connected with cable isn't pinging the router constantly when it boots up. Using development snapshots doesn't help us at all with this, actually it makes it worse, atleast with latest devsnap while writing this (12.21.2005) rj-45 ports even loose their IP's if client renews it's IP address, therefore we will use latest Talisman release version 1.1 (latest while writing this howto).
You can use development snapshot version on Bridge-router if you want to.

And now, let's start setup. First we setup our Bridge-router.
It's pretty simple, just set everything as you like your router to act, and on Wireless page, set it up as AP, give it a SSID (in this example we use SSID "bridge.ssid" ) and select channel you want to use. Also make sure that SSID is visible, I wasn't able to make client-bridged to work with hidden SSID.

Next we start configuring our Client-router.
First make sure that you are running non dev-snap version of Talisman 1.1 and then start setting up with these instructions..

We will start at first page, Setup->Basic Setup.
Set Internet connection to Disabled. Setup router's name and hostname, domain.. Then setup DNS #1 to IP address of Bridge-router ( 10.0.0.1 )
Set local IP address to 10.0.0.5 and Gateway again to same as Bridge-router, 10.0.0.1.
You can also setup Timezone if you wish to.
Router re-boots now.

Next, go to Setup->Advanced Routing, select Enable and make sure there's no other selections made or settings written. Neighbor IP says 0.0.0.0. That doesn't matter, also AS# says 1 and Neighbor AS# says 1. That's ok. When you save, router re-boots propably again.

Then we go to Setup->VLANs
Un-check WAN port from VLAN1 and make it member of VLAN0, we get our network connection wirelessly, so we want to make our WRT a 5 port router to get advantage of all ports. You can also make it tagged like other ports are, now WAN port should act identically to LAN ports. Save settings and router re-boots [ I told you this is slow ]

When router has done bootup, go to Security->Firewall and un-check all marks from page and set Firewall Protection to Disabled state. We don't need a firewall inside our network as our Bridge-Router already is firewalling us from outside and using firewall with client-bridged.. Not a good idea, we might end-up with a failure. After you save changes, router reboots once again.

Next we go to Administration->Management
Select what you like, but make sure the following settings:
Spanning Tree Protocol: Disabled
802.1x: Disabled
PPTP Server: Disabled

You might wanna setup Telnet and/or SSHD to enabled.
After saving router re-boots.

DHCP server
Client-router needs to be in same subnet with bridge-router. Also it needs to give IP addresses from same network, but from different area. Configure it that way..
For example, if you bridge-router gives IP addresses from area: 10.0.0.50-10.0.0.99
Let your client-router to give IP's from range 10.0.0.100-10.0.0.105
or a bigger area if you connect another router with rj-45 to this bridge.

Final settings..
Go to Wireless->Basic Settings
Select Client-bridge mode from Wireless Mode list. Select desired network mode. Propably Mixed? And then set SSID to bridge.ssid

Then, reboot your router and wait for it to come back up.
Try to ping your Client-router ( 10.0.0.5 ). You propably can't ping it. Your machine either can't get a IP address from it. This is the bug I earlier told to you. Check if your network card still has it's previous IP address, if it has lost it or is having an invalid IP address then configure your NIC with static IP, set it to 10.0.0.101 or something. Open a prompt and type "ping -t 10.0.0.5" and power-cycle your Client-router.
Amazing isn't it? After a short period after boot process begun, your router starts replying to pings. Don't stop pinging yet. After it started pinging, it will once more time-out ping when it changes to client-bridge mode. After this you can stop pinging, and start pinging of your bridge-router ( 10.0.0.1 ) to check that you are connected. If you aren't connected, go to web interface and check settings and Status->Wireless to see that you are connected and find out what is the problem.

In worst case, you need to reset your router, re-flash firmware and set it all up once again from factory settings.

---

Okay, how about some tips? Sure, I haven't measured if speeds are any better.. But, I didn't chose Mixed mode in Wireless Network Mode, I chose G-only. Also as my routers are GS not just G routers, I gone to Wireless->Advanced Settings and set Afterburned on.
Do these settings to both, router and client.

In my network, I have 5 wrt54gs's. So I have this kind of setup:
10.0.0.1 gateway
10.0.0.2 extends network to another room with wired connection
10.0.0.3 bridge
10.0.0.4 client1
10.0.0.5 client2

So, bridge is just supposed to give me 4 more rj-45 ports ( wan port is connected to gateway ) to connect my computers there and share connection wirelessly to client1 and client2, so wireless AP of bridge isn't being used for anything else, so I also enabled Frame burst in both clients and with bridge. This might speed up a bit too. I also set up MAC filtering so only client1 and client2 are allowed to connect to bridge, this way all wireless traffic that happens in bridge is between client-bridged WRT's so I should have pretty nice speed since it's not being interrupted by my PDA's and laptops that are connected with WLAN to my network. All broadband on it's wireless is given to these 2 routers.

---

Don't you hate that you need to have 2 DHCP servers? I mean, wouldn't it be nice to setup just one DHCP server where you enter your Static IP leases and other settings? WDS would be an answer, but it propably would slow down your network, right? Well, another answer would be a dhcp-proxy that current talisman doesn't provide. I tried several proxies from openwrt and didn't got any of them to work. Talisman also has bcrelay command, but I am not sure if this would work, so I compiled my own dhcp-proxy.

http://www.roadrunner.cx/sveasoft/dhcp-helper.tar.gz

Enable your RW partition, disable DHCP server on Applications & Gaming->DHCP and disable dnsmasq at Administration->Management. Then download dhcp-helper, I changed it's source so it runs as admin instead of default nobody user, which is missing from talisman. Now it doesn't bug when you tell it to start without telling it to start as admin or root [same user in talisman, they share a UID]. Unpack dhcp-helper.tar.gz to your RW partition on Client-router ( /usr/local ) it extracts dhcp-helper to /usr/local/bin and also extracts startup and kill scripts to /usr/local/etc/rc.d which as default uses gateway address as a proxied dhcp server. Script is setup to autostart on boot. If you don't it to autostart on boot, telnet in and:
Code:chmod -x /usr/local/etc/rc.d/S99dhcp-relay

Now, reboot your client-router while pinging it's IP ( ping -t 10.0.0.5 ) and when you are sure that router has booted and ping is replying, and you are sure that it is connected wirelessly ( ping 10.0.0.1 to check it out ) you can release and renew your IP from DHCP, tadaa! It works

Hopefully in next release sveasoft could have fixed the problem that rj-45 ports loose their IP if one of 'em isn't being pinged during bootup as after integrating a DHCP proxy client-bridged mode would be complete.

Also, I hope someone could find a solution for that pinging, maybe a bootup script on wrt or something? I didn't find and ain't gonna look for one in a while as my development process is about to brake now for a moment as I need to go to work to pay my rent etc

Valeu brother!