How to wireless bridge my 2 networks?

Printable View

Show 40 post(s) from this thread on one page

06-10-2004, 00:50
brubber

Quote:

Originally Posted by P Still

This is my wanted setup.

So, how should this be accomplished ?

Very nice and clear picture, however for me still a lot of info missing. Even though it appears to me that you have more then adequate knowledge of TCP/IP it still possible you are overlooking something obvious.

Is there a DHCP server active (on your switch / ap)
Sure the IP adress you assign to to your asus "..185" is free?
for WDS do you use anonymous option or Bridge list?
If bridge list, sure you typed the MAC adress correct
Perhaps you need to define static route(s) to get the thing working
Sure the switch / AP setup is correct? (What kind of rights do you have on the switch / AP?)
Routing table(s)?
Tried a trace route?
Why use DHCP on the asus? Your scheme suggests you only connect desktops and printer

Quote:

Originally Posted by P Still

Setting up my WL-500g (Y) as: Home gateway (want to share IP-address for my 3 PC’s (wired to WL-500g, no wireless)), WDS only, bridge mode, fixed IP on WAN, default on LAN with DHCP. No NAT-settings, no Internet firewall settings, Also want to share printer from WAN and LAN side, share a ftp-server on internet.
Result: Connecting to AP is OK, but 0.0.0.0 is showing as IP-address in the WAN (I have access to the switch). In wl-500g web home page everything looks OK.

Seems to me this is the way to go. Perhaps you should still define static routes.
What do you mean with "looks OK" (What do the relevant status windows report?)

P.S.
For those who don't know, 0.0.0.0 designates a default gateway. This is used in routing tables to represent "All Other Network Addresses".
06-10-2004, 09:32
Styno

To me it seems you need to switch the switch/AP and the Asus router. Configure the WL500g as router/gateway with a DHCP client on WAN side and a DHCP server on LAN/wireless side.
06-10-2004, 22:13
P Still

Hopefully I've missed something

No DHCP server on switch/AP. And no other limitations except WEP.
Yes, ... 185 is free. No other is using it ( I have administration rights to W WAN and switch)
Bridge: tested both, mostly use MAC-list and MAC-address is OK
(I have connection and authentication with the switch/AP from time to time, not always)
I've also set up a special WLAN in the switch with a route to the gateway, no effect.
Set up a route in wl-500g to gateway, no luck.
Trace route: from LAN-side just 1 hop to the WAN IP. from WAN nothing.
DHCP on LAN ? Well, no special reason.
web page "Looks OK". Well, I don't trust what is showing on neither web page or status page with the ASUS firmware. They show different values on IP-addresses and can change value if I just change some setting with let say bridge or AP or ....
So now I moved over to Igors 1.7.9-5. At least it is consistent in behavior
The routing table say:
192.168.1.0 0.0.0.0.0 255.255.255.0 U br0
0.0.0.0 xxx.xxx.xxx.129 0.0.0.0 UG eth2
xxx.xxx.xxx.128 0.0.0.0 255.255.255.192 U eth2
And the last row is a puzzle. Why .... 128.
It's there whatever I set different values.
And if I read all NVRAM values no ....128.

Styno, what You suggess is:
Treat the switch/AP as a wireless client in a wl-500g router/gateway configuration ? Right ?
Interesting idea or is that what Igor ond others have been talking about in different treads ? Not clear what they ment.
I've tried with that ( Op- mode:AP, bridge Hybrid, and manually assign IP-addresses (=my static public IP-address) on W LAN
.No more luck with this than the other.

At the moment there has been a long time when 0.0.0.0 is showing in the switch, but I can see that there is a connection, authentication and some traffic in both ways. But suddenly it can change so I can ping from WAN, but never from Internet. When, how and why I haven't figured out yet.

OK, long answer but many questions.
06-10-2004, 22:42
P Still

Just a new comment about routing table:
I tested with some different setting for static route + Apply and not.
Now the line with ...... 128 is gone, but I now have
82.0.0.0 0.0.0.0 255.0.0.0 U eth2
I can change static route or disable it or ..., line in table is unchanged.

And no change in switch.
06-10-2004, 23:50
brubber

Quote:

Originally Posted by P Still

Hopefully I've missed something

192.168.1.0 0.0.0.0.0 255.255.255.0 U br0
0.0.0.0 xxx.xxx.xxx.129 0.0.0.0 UG eth2
xxx.xxx.xxx.128 0.0.0.0 255.255.255.192 U eth2
And the last row is a puzzle. Why .... 128.
It's there whatever I set different values.
And if I read all NVRAM values no ....128.

xxx.xxx.xxx.128 is there because it's your network IP, that is if you use netmask 255.255.255.192. Reading some basic stuff concerning IP / routing etc. may be good idea, and will perhaps even solve your problem

0.0.0.0 xxx.xxx.xxx.129 0.0.0.0 UG eth2, this is the way to the outside world (WAN). So what is eth2?? I guess this is the wireless connection to your switch?

My routing table looks very similar, I only have an extra line defining multicast boundary on my LAN conn.

If I inderstand you correctly you are able to reach your WAN from the Asus, so i guess you can also reach the internet

Getting to your router from the internet is a different issue which was/ is discussed in a number of topics on this forum
06-10-2004, 23:50
Styno

Yes, what I mean is: Connect the WL-500g directly to the internet. Configure it as gateway using the 'System Setup - Operation Mode' menu. Configure a DHCP server for LAN and WAN. The rest should be piece of cake (Or I'm thinking too simple here :rolleyes: )
07-10-2004, 00:58
Antiloop

@brubber
when quering an Ripe address you should also use the ripe server
this is the real output:

% This is the RIPE Whois secondary server.
% The objects are in RPSL format.
%
% Rights restricted by copyright.
% See http://www.ripe.net/db/copyright.html

inetnum: 82.0.0.0 - 82.0.3.255
netname: CYBERWARE-LTD
descr: Cyberware Ltd
country: GB
admin-c: FO126-RIPE
tech-c: NNMC1-RIPE
status: ASSIGNED PA
mnt-by: AS5089-MNT
changed: hostmaster@ntli.net 20030630
source: RIPE

route: 82.0.0.0/14
descr: NTL-UK-IP-BLOCK
origin: AS5089
mnt-by: AS5089-MNT
changed: hostmaster@ntli.net 20040929
source: RIPE

role: NTLI Network Management Centre
address: NTL Internet
address: Crawley Court
address: Winchester
address: Hampshire
address: SO21 2QA
trouble: -------------------------------------------------------
trouble: For abuse notifications please -
trouble: file an online case @ http://www.ntlworld.com/netreport
trouble: +44 1633 710142 (Voicemail Only)
trouble: -------------------------------------------------------
trouble: For peering issues/requests please -
trouble: email : peering@ntli.net
trouble: -------------------------------------------------------
admin-c: MH22007-RIPE
admin-c: CF2297-RIPE
admin-c: CM1377-RIPE
tech-c: MH22007-RIPE
tech-c: CF2297-RIPE
tech-c: CM1377-RIPE
nic-hdl: NNMC1-RIPE
mnt-by: AS5089-MNT
notify: data.planning@ntl.com
e-mail: data.planning@ntl.com
changed: hostmaster@ntli.net 20030328
changed: hostmaster@ntli.net 20030401
changed: hostmaster@ntli.net 20030603
changed: hostmaster@ntli.net 20030707
changed: hostmaster@ntli.net 20040303
changed: hostmaster@ntli.net 20040312
changed: hostmaster@ntli.net 20040929
source: RIPE

person: Frank Oakes
address: Litton House
address: Global Business Park , Saville Road Westwood
address: Peterborough
address: PE3 7PR
phone: +44 1733765050
nic-hdl: FO126-RIPE
changed: hostmaster@ntli.net 20021104
source: RIPE
07-10-2004, 01:51
brubber

Quote:

Originally Posted by Antiloop

@brubber
when quering an Ripe address you should also use the ripe server
this is the real output:

You're right, removed my post. The idea was only to show that the 82/8 range was allocated to RIPE who then ofcourse assign specific ranges
07-10-2004, 02:21
P Still

Yes Styno, I think that is too simple. Shouldn't be, but ....
That was my 1st, 10th, 20th, 50th, 100th and ...th attempt

From Ripe and WhoIs is a confirmation about IP-address (and right owner ....)

REach WAN from ASUS:
No, when trying to ping from LAN-side I can only ping ASUS LAN and WAN IP.
Not even the switch or anything else, internet or not.
Trying to ping wl-500g from WAN-side is more problematic.
Since most of the time 0.0.0.0 is the identity wl-500g gets in the switch, I can't ping wl-500g even from the WAN.
WHEN I have the right identity in the switch I can ping wl-500g WAN-IP from a PC in the WAN.
When, why and how I can or can't get the right IP identity in the switch I haven't figured out yet.
It can suddenly change without any action from me, it can change when I pull out the power and restart wl-500g. But it's hard/impossible to repeat it.
And when I have contact and then make changes or just reboot I may or may not lose contact or it turn to 0.0.0.0 again.

I am more and more sure that it's a compatibility problem.
But don't lose the hope as someone said earliar in the tread. "The diamond is there". Where ?
07-10-2004, 02:48
brubber

Quote:

Originally Posted by P Still

Since most of the time 0.0.0.0 is the identity wl-500g gets in the switch

Please correct me if I'm wrong but I still think this is because for the switch / AP the asus is the default gateway for the Asus LAN

In your switch routing table there should then be some entry like:
0.0.0.0 192.168.1.1 0.0.0.0 UG brx (G for Gateway)

Also still wondering what eth2 is doing in this line:
0.0.0.0 xxx.xxx.xxx.129 0.0.0.0 UG eth2

Did you try the following setup:
Asus in AP mode (System setup; Operation mode)
Authentication mode "Open System or Shared Key" to start with (Wireless; Interface)
Block Broadcast SSID "No" (Wireless; Interface) SSID take from switch (Case sensitive??)
AP mode "WDS" Or "Hybrid"; Connect to AP's in Remote Bridge List "Yes"; Allow Anonymous "Yes" (Wireless; Bridge)
Add MAC adress of your switch to Remote Bridge List (Wireless; Bridge)
WAN Connection Type "Automatic IP", I guess a DHCP server is active on your switch AP (IPConfig; WAN & LAN)
If no DHCP from switch use "Static IP
IP: xxx.xxx.xxx.185
Netmask: 255.255.255.192
Gateway: xxx.xxx.xxx.129
DNS server xxx.xxx.xxx.129

LAN IP adress 192.168.1.1
Netmask 255.255.255.0
DHCP server NOT enabled

Assign static IP in range 192.168.1.x to workstation(s) connected to the Asus

check your switch / AP firewall / NAT settings!!, make sure access is granted to 192.168.1.x (UTP / UDP / ICMP) or create a DMZ for the asus

Disable all firewalls on the Asus

Make sure RADIO is enabled (Wireless; advanced)

Now Save and Restart

IF this works you can implement more secure settings step by step

Good Luck
07-10-2004, 20:27
P Still

Followed Your advice. But starting with System set up and AP mode did result in a limitation of what to change, for example WAN IP-addresses.
So I started with Factory default. Changed to AP-mode using Telnet and NVRAM ....... ClientMode=0.
From there I entered according to your info. (No, we don't have DHCP-server on switch).
I have done these settings before, BUT the new thing was to set DNS address to xxx.xxx.xxx.129 (=Gateway value). (Why, I asked)
Result:No luck.
And I didn't managed to get this:
In your switch routing table there should then be some entry like:
0.0.0.0 192.168.1.1 0.0.0.0 UG brx (G for Gateway)
Next step:
Changed to Station mode: NVRAM .... ClientMode=1.
Reboot.

Ooops, now the switch showed my IP-address (after 2 days with 0.0.0.0)
Ping from LAN ? WAN-IP OK.
Ooops! Ping to switch OK. Ping to ......... OK
Ping from WAN-PC to ASUS OK. Ping from Internet to ASUS OK
:D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D
I can reach ASUS web page from Internet, I can print from .....,
I can probably reach FTP from internet (need to reboot first), but since I am writing this on a PC connected to ASUS LAN I need to finalise this first.
Security comes next but since our PC's are well protected thats a minor issue.

Now to the great moment of thanking You, Brubber.
Finding the missing part ( DNS IP) was something I probably haven't thought about until ASUS stuff was on the dump.

Without Your help and understanding ...... (sounds like a speach on the Oscar gala).

THANKS !!!
07-10-2004, 23:47
brubber

Quote:

Originally Posted by P Still

Now to the great moment of thanking You, Brubber.
THANKS !!!

:) :) :) :) :)

And all the others that tried to help you I guess!!

Perhaps now is a good time to make a small donation to this forum (http://wl500g.info/showthread.php?t=937)

Wonder if the topic starter "Lord_Moebius" managed to get his stuff working.

DNS is Used to map names to IP addresses and vice versa. Domain Name Servers maintain central lists of domain name/IP addresses and map the domain names in your Internet requests to other servers on the Internet until the specified web site is found.

P.S. is the wl500g still for sale? :p :p :p
28-10-2004, 17:17
duwrt

Simple step by step

I'm new to the world of WiFi, so I didn't understand the full details in this post. Does anyone have a simple step by step or a Visio that has the settings included.

THanks
duwrt

Quote:

Originally Posted by P Still

Followed Your advice. But starting with System set up and AP mode did result in a limitation of what to change, for example WAN IP-addresses.
So I started with Factory default. Changed to AP-mode using Telnet and NVRAM ....... ClientMode=0.
From there I entered according to your info. (No, we don't have DHCP-server on switch).
I have done these settings before, BUT the new thing was to set DNS address to xxx.xxx.xxx.129 (=Gateway value). (Why, I asked)
Result:No luck.
And I didn't managed to get this:
In your switch routing table there should then be some entry like:
0.0.0.0 192.168.1.1 0.0.0.0 UG brx (G for Gateway)
Next step:
Changed to Station mode: NVRAM .... ClientMode=1.
Reboot.

Ooops, now the switch showed my IP-address (after 2 days with 0.0.0.0)
Ping from LAN ? WAN-IP OK.
Ooops! Ping to switch OK. Ping to ......... OK
Ping from WAN-PC to ASUS OK. Ping from Internet to ASUS OK
:D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D
I can reach ASUS web page from Internet, I can print from .....,
I can probably reach FTP from internet (need to reboot first), but since I am writing this on a PC connected to ASUS LAN I need to finalise this first.
Security comes next but since our PC's are well protected thats a minor issue.

Now to the great moment of thanking You, Brubber.
Finding the missing part ( DNS IP) was something I probably haven't thought about until ASUS stuff was on the dump.

Without Your help and understanding ...... (sounds like a speach on the Oscar gala).

THANKS !!!
06-11-2004, 17:59
duwrt

Bridge settings

A few questions about the advice below:

1-Are the addresses below chosen for a specific reason or arbitrary.. More directly, why change from the standard netmask
~~~~~~~~~~~~
IP: xxx.xxx.xxx.185
Netmask: 255.255.255.192
Gateway: xxx.xxx.xxx.129
DNS server xxx.xxx.xxx.129
~~~~~~~~~~~

2- Doesn't it cause an issue if both devices use 192.168.1.1 for their LAN addresses.

3- What do you set as the gateway for the 2nd device in a bridged setup. Should it look to it's own WAN IP or back to the 1st device.

Quote:

Originally Posted by brubber

WAN Connection Type "Automatic IP", I guess a DHCP server is active on your switch AP (IPConfig; WAN & LAN)
If no DHCP from switch use "Static IP
IP: xxx.xxx.xxx.185
Netmask: 255.255.255.192
Gateway: xxx.xxx.xxx.129
DNS server xxx.xxx.xxx.129

LAN IP adress 192.168.1.1
Netmask 255.255.255.0
DHCP server NOT enabled

Assign static IP in range 192.168.1.x to workstation(s) connected to the Asus

check your switch / AP firewall / NAT settings!!, make sure access is granted to 192.168.1.x (UTP / UDP / ICMP) or create a DMZ for the asus
06-11-2004, 23:19
brubber

Quote:

Originally Posted by duwrt

A few questions about the advice below:

1-Are the addresses below chosen for a specific reason or arbitrary.. More directly, why change from the standard netmask
~~~~~~~~~~~~
IP: xxx.xxx.xxx.185
Netmask: 255.255.255.192
Gateway: xxx.xxx.xxx.129
DNS server xxx.xxx.xxx.129
~~~~~~~~~~~

It's not arbitrary, however not relevant to your setup: This subnet is defined on the primary AP in his network. If you're using the WL-500g with default settings you would have 192.168.1.1; 255.255.255.0 and so on.

Quote:

Originally Posted by duwrt

2- Doesn't it cause an issue if both devices use 192.168.1.1 for their LAN addresses.

Yes it would cause a minor issue because it's on a different subnet, so some routing would be necessary.

Quote:

Originally Posted by duwrt

3- What do you set as the gateway for the 2nd device in a bridged setup. Should it look to it's own WAN IP or back to the 1st device.

:confused: Don't understand your question.

To learn some basic TCP/IP this link http://www.pku.edu.cn/academic/resea...ml/TC0400.html will certainly be helpful. It's easy reading and it will help you to understand what you're doing.

For some more advanced reading and a lot of handy network tools go to http://www.subnetonline.com

And an easy subnet calculator: http://jodies.de/ipcalc

Show 40 post(s) from this thread on one page