Starpoint

Yes I do remember dialup modems.. still have some OLD 2400 baud modems that work, got a bunch of 14.4 modems that I love to use for faxing since they are excellent for that.

__________________
Against the run of the mill, static as it seems

We break the surface tension with our wild kinetic dreams
Curves and lines -- of grand designs...

Tonight's movie "Soylent Green" has been brought to you by our sponsor - Waste Management

My mind is like a Steel trap - Rusty and Illegal in most states

Dutch

This is just to easy...
Unless it's hand jobs done on the side, we want pictures...

The Simpsons has got "Side Show Bob", the NS forums has got "Side Job Starpoint"...

/ducks and runs...

Dutch

__________________
All your answers are belong to Google. SEARCH DAMMIT!
Warning. Warning.
Low C8H10N4O2 level detected. Operator halted....

Starpoint

Well I did cost you a keyboard with the "My name is Beakmyn, James Beakmyn"

__________________
Against the run of the mill, static as it seems

We break the surface tension with our wild kinetic dreams
Curves and lines -- of grand designs...

Tonight's movie "Soylent Green" has been brought to you by our sponsor - Waste Management

My mind is like a Steel trap - Rusty and Illegal in most states

Dutch

Oh yes... I forgot to punish you for that one. Consider yourself banned.... For the next 5 minutes...



Dutch

__________________
All your answers are belong to Google. SEARCH DAMMIT!
Warning. Warning.
Low C8H10N4O2 level detected. Operator halted....

Sleeping Dog

OK Guys...
Still don't have it working right, but here's a tip that falls into the "Good To Know" category.

I thought that I might have bricked #1 when I did a reset to defaults. I couldn't access it through the Web interface 192.168.1.1 - 255.255.255.0
(My NIC in the setup computer was set DHCP)

I found a "tip' that said to first try resetting the NIC in the setup computer to something like 192.168.1.X (where X is not = 1) and set the Gateway to 192.168.1.1

Worked like a charm. Unit is NOT bricked. I can get back into it again. (WHEW!)

__________________
__________________________________________________ ___________________
Thinking "Outside Of The Bachs" can also keep you from going totally Baroque.
__________________________________________________ ___________________
Sleeping Dog

Sleeping Dog

Again, have tried suggested setups. I have to be missing something important somewhere (or too many of my brain-cells flew South for the Winter and aren't coming back.)

I'm going to reset to defaults (again) and try the following setup that I found on:
http://wrt-wiki.bsr-clan.de/index.ph...ireless_Bridge
It is fairly short, so I will include the text in this post. They make it sound SOOOooo simple. If any of you see anything critical missing from these instructions, please let me know. My forehead flat-spot is getting so big that I am looking (and probably thinking) rather Neandertal. Here it is:

Introduction

Wireless Bridging is used to connect 2 LAN segments via a wireless link. The 2 segments will be in the same subnet and looks like 2 ethernet switches connected by a cable, to all computers on the subnet. Since the computers are on the same subnet, broadcasts will reach all machines allowing DHCP clients in one segment to get their addresses from a DHCP server in a different segment. You could use a Wireless Bridge to transparently connect computer(s) in one room to computer(s) in a different room when you could not, or did not want to run an ethernet cable between the rooms. Contrast this with Client Mode Wireless, where the local wireless device running DD-WRT connects to the remote router as a client, creating 2 separate subnets. Since the computers within the different subnets cannot see each other directly, this requires the enabling of NAT between the wireless and the wired ports, and setting up port forwarding for the computers behind the local wireless device. Segments connected via Client Mode Wireless cannot share a DHCP server.

In the case in which we are interested, a wireless device running DD-WRT such as a WRT54G is configured as a Wireless Bridge between a remote wireless router (of any make/brand) and the ethernet ports on the WRT54G.
[edit]
Instructions

A very good forum post was made by kkennedy070790 about running a WRT54G using DD-WRT as a wireless bridging.

Find it here: http://forum.bsr-clan.de/viewtopic.p...t=bridge#11522


A very simple step-by-step description to connect a WRT54G running DD-WRTV23:

To enable Brige-Mode between 2 WRT54G, one WRT54G has to be in AP-Mode in Wirelss/Basic Setup. The other one is joining the first WRT54G as "Client-Bridged"

1. Add WAN MAC-Address of WRT54G to your mac filter list on your base station.

2. Connect to your WRT54G (normally 192.168.1.1) by wire which should act as client bridge.

3. Enable Wireless Security (in Wireless/Wireless Security) as used, eg. WEP and configure it as used in your local network.

4. In Wireless/Basic Settings choose "Client-Bridged" as Wireless Mode and set SSID, Wireless channel and Network Mode can be set to same values as your Base Station, normally Auto / Mixed.

Thats all. On next wired connect to your wrt54g you should get an IP Adress from your network.

If you want to configure your new wrt54g bridge again, set a static ip adress of 192.168.1.x network to your client and you can reach the wrt54g as 192.168.1.1. by wire.
[edit]
V23 Firmware (beta)

In v23 firmware (soon to be final), you can set up the bridge from the Wireless->Wireless Mode menu. Just select "Client Bridged". This will automatically turn off DHCP. Note that only the Network Mode (b/g) and SSID settings are used in Client Bridged mode.

See notes on a 2.3 attempt at Client Bridged with a Belkin A/G AP in Bridge Install

I am also linking these in Client Bridged
[edit]
New to Client Bridging?

Here's some extra information about client bridging and some, perhaps unexpected, side effects. (If you're a wireless networking wizard, you'll know this already.)

When you've switched to Client Bridge mode you won't be accessing the remote AP until your IP changes unless your box and the remote network are on the same subnet. For example, say you have:

linksys box IP: 192.168.1.1
your computer: 192.168.1.100
remote network gateway: 10.0.0.1

Once you've made the configuration changes in your router, you'll need to get a new address to access the remote network. A simple way to do this with most computers is to unplug the network cable count to 10 and plug it in again. When the cable is plugged in again, it will get a new lease, but this time from the remote computer. For example, it will get an address in the 10.0.0.x range, e.g. 10.0.0.100. Now you'll be able to use the internet over the wireless link as you expect.

However, you won't be able to access your Linksys to administer it. The solution is to turn off DHCP and use a static IP (e.g. 192.168.1.99), or, alternatively, assign an address for your Linksys from the remote subnet (e.g. 10.0.0.2). Be careful, however, not to pick an address already in use.

__________________
__________________________________________________ ___________________
Thinking "Outside Of The Bachs" can also keep you from going totally Baroque.
__________________________________________________ ___________________
Sleeping Dog

streaker69

I really haven't been following this too closely because I haven't had a whole lot of time. But from the skimming it would seem you have some basic Networking 101 issues. But hey, I could be wrong, since I haven't been following that closely.

Here's a quick drawing I did, hopefully it'll help you out, I think it kinda represents what you're trying to do, and should give you some pointers as to where you need to be.

Attached Images

QuickBridge.jpg (43.9 KB, 67 views)

__________________
"One of these days, I'm going to cut you to pieces."

If you're offended by this post, please feel free to report it to one of the many helpful moderators of this forum.

Thank you.

Denz

SD, what cams are you puting in the barn ? My farther in-law wants me to do the same thing for him.
best of luck, i'll want a parts list.. heheh
some good reading in this thread and lots of junk too.

wrzwaldo

What's up with the barn cams? You folks like watching bovines screw?

Probably NSFW ----> http://everything2.com/index.pl?node_id=584424

Beef, It's what's for dinner ----> http://www.crazyshit.com/cnt/medias/7951

Thorn

Your post falls into the latter category.

You should read the Rules and the Welcome Desk immediately.

__________________
Thorn
"I'm The Doctor. I'm a Time Lord. I am from the planet Gallifrey in the constellation Kasterborous. I'm 903 years old and I am the man who is going to save your lives and all 6 billion people on the planet below... You got a problem with that?"

MikeP928

Hey Streak,

Are you masking the 172.28.1.x subnet down below a class C?

If not, I don't think you will ever cross the routed segment 172.28.0.x and see any of the other side of the 172.28.1.x network. The first router is not going to pass any traffic for the 172.28.1.x network over the routed interface when it knows that network is local.

Did I miss something? Or did the fumes get to you today?

MikeP

__________________
Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote.
-- Benjamin Franklin, 1759

Sleeping Dog

Two Things:

Barn cams are X-10 color wireless from their website. Cheap if you get a package deal on sale. I had them set up temporarily via coax to the reeiver and a video monitor in the house so that they could watch the foaling (birthing) stalls at all hours. Cams have built in microphones too. By routing them into one of the networked/bridged PC's I can eliminate the long coax and they can be monitored via a network/Internet connection from anywhere.

Item 2:
I got the bridge "sorta" working.

I followed the instructions EXACTLY from the WIKI post that I quoted earlier including enabling WEP. I had the gear set as follows:
WRT54GS #1 - 192.168.1.1
Setup Computer #1 - 192.168.1.105 - 255.255.255.0 - (gateway)192.168.1.1
WRT54GS #2 - 192.168.1.2
Setup Computer #2 - 192.168.1.110 - 255.255.255.0 - (gateway)192.168.1.1
This made the two setup computers see each other across the bridge.
Then I reset both setup computers DHCP and set the WRT's to:
WRT54GS #1 - 192.168.0.200
WRT54GS #2 - 192.168.0.201
After rebooting both WRT's and both PC's, all of the machines on both side of the wireless bridge can "see" each other. However. both setup PC's don't want to see the Internet but the others on the "hardwired" side (my existing network sans wireless) do see it.

My routing PC still has the two NIC's set to DHCP (cable modem side) and 192.168.0.1 (network hub/switch side) Please see drawing page 7 of this thread.

If I can get the "base" side PC to see the Internet through WRT #1, I have a feeling that the other Setup PC #2 on the other side of the wireless bridge will too.

I have tried to keep the initial setup as simple as possible until it all works. Any ideas, folks, about why I'm not seeing the Internet on the setup PC's?

__________________
__________________________________________________ ___________________
Thinking "Outside Of The Bachs" can also keep you from going totally Baroque.
__________________________________________________ ___________________
Sleeping Dog

streaker69

You may be right, and I did draw it rather quickly. But since the two units are bridged, then wouldn't they appear to be on the same segment? The routers should just think that's it's passing traffic as though it was a piece of wire, right? Or am I misunderstanding bridge mode?

__________________
"One of these days, I'm going to cut you to pieces."

If you're offended by this post, please feel free to report it to one of the many helpful moderators of this forum.

Thank you.

MikeP928

Since you had a different subnet on the APs, I thought you were using the router/wan port and routing. If everything is on LAN ports, it should pass traffic fine. You would just have two different subnets running on the same physical segment. Unless you open the mask up to a class B.

My gout is acting up today and I am out of painkillers, so I am running on even fewer cylinders than usual.

MikeP

__________________
Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote.
-- Benjamin Franklin, 1759

streaker69

Yeah, you're right, I do have it drawn using the LAN and WAN ports on the bridges. I did do it quick and didn't think it through real well. Spent most of the day fighting with Vmware and a FreeBSD build, and found out that we have some solid waste haulers sneaking into the plant at night and dumping illegally.

__________________
"One of these days, I'm going to cut you to pieces."

If you're offended by this post, please feel free to report it to one of the many helpful moderators of this forum.

Thank you.