Two wireless routers wired together

Here is my situation:

I rent an apartment on the first floor of a house. My landlord has his
offices upstairs. There, he has a cable modem and a Linksys WRT54GS.
That router is then connected into a wall socket using an ethernet
cable (I assume the other end is in one of the LAN ports of the
WRT54GS).

Then, on my floor, I connect my wall socket to my router, a Linksys
BEFW11S4 (Version 3). The only way my router works consistently is to
connect the wall socket to the Uplink port of my BEFW11S4. However,
it's only wired connections that work; I have never been able to get
wireless working. Because of client confidentiality, my landlord does
not want me to use his wireless connection, so I need some way to get
mine working.

Several articles explain how to set up my router as an access point. I
have tried the method described (switching the Device IP address,
disabling DHCP, changing SSID and channel), but again, things only
work using the Uplink port. I can never seem to make a direct LAN-LAN
connection (the lights on my router never come on). And I can never
get wireless working.

Any thoughts on where the problem might be? Or maybe a way that my
landlord could give me wireless internet access using his WRT54GS that
would not give me access to computers on his network? I really
appreciate any help!

"Paul Zitarelli" <(E-Mail Removed)> wrote in message
> Here is my situation:
>
> I rent an apartment on the first floor of a house. My landlord has his
> offices upstairs. There, he has a cable modem and a Linksys WRT54GS.
> That router is then connected into a wall socket using an ethernet
> cable (I assume the other end is in one of the LAN ports of the
> WRT54GS).
>
> Then, on my floor, I connect my wall socket to my router, a Linksys
> BEFW11S4 (Version 3). The only way my router works consistently is to
> connect the wall socket to the Uplink port of my BEFW11S4. However,
> it's only wired connections that work; I have never been able to get
> wireless working. Because of client confidentiality, my landlord does
> not want me to use his wireless connection, so I need some way to get
> mine working.
>
> Several articles explain how to set up my router as an access point. I
> have tried the method described (switching the Device IP address,
> disabling DHCP, changing SSID and channel), but again, things only
> work using the Uplink port. I can never seem to make a direct LAN-LAN
> connection (the lights on my router never come on). And I can never
> get wireless working.
>
> Any thoughts on where the problem might be? Or maybe a way that my
> landlord could give me wireless internet access using his WRT54GS that
> would not give me access to computers on his network? I really
> appreciate any help!
>
Actually if you are attached to one of the LAN ports on his router
reguardless of wether you plug into your lan, wan or uplink port YOU are on
his NETWORK and will be able to see all of his machines. Find out exactly
what is going on on the other end.
What happens if you plug the wall jack straight into your computers ethernet
port, do you get an IP address and default gateway via DHCP?
If you do then it would seem that everything on his end is correct and that
something is wrong with your router or it is not configured correctly.
If you need to buy a new router look at the Buffalo WHR-G54, WHR-HP-G54 or a
Linksys WRT54GL.

On Apr 17, 10:54 pm, Paul Zitarelli <zitar...@gmail.com> wrote:
> Here is my situation:
>
> I rent an apartment on the first floor of a house. My landlord has his
> offices upstairs. There, he has a cable modem and a Linksys WRT54GS.
> That router is then connected into a wall socket using an ethernet
> cable (I assume the other end is in one of the LAN ports of the
> WRT54GS).
>
> Then, on my floor, I connect my wall socket to my router, a Linksys
> BEFW11S4 (Version 3). The only way my router works consistently is to
> connect the wall socket to the Uplink port of my BEFW11S4. However,
> it's only wired connections that work; I have never been able to get
> wireless working. Because of client confidentiality, my landlord does
> not want me to use his wireless connection, so I need some way to get
> mine working.
>
> Several articles explain how to set up my router as an access point. I
> have tried the method described (switching the Device IP address,
> disabling DHCP, changing SSID and channel), but again, things only
> work using the Uplink port. I can never seem to make a direct LAN-LAN
> connection (the lights on my router never come on). And I can never
> get wireless working.
>
> Any thoughts on where the problem might be? Or maybe a way that my
> landlord could give me wireless internet access using his WRT54GS that
> would not give me access to computers on his network? I really
> appreciate any help!

In a nutshell, you need to work on an understanding of how IP works,
the functional architecture of a WAP/bridge/router, and the config
and
troubleshooting of same.

Meaning how, on what basis, addresses are assigned to what, and
how routing is done. Understanding of wireless part a plus.

Then it's straightforward. Now it seems to be black-magic to you,
unless you just want to hide all the details from us.

HTH,
J

<(E-Mail Removed)> wrote in message
> In a nutshell, you need to work on an understanding of how IP works,
> the functional architecture of a WAP/bridge/router, and the config
> and
> troubleshooting of same.
>
> Meaning how, on what basis, addresses are assigned to what, and
> how routing is done. Understanding of wireless part a plus.
>
> Then it's straightforward. Now it seems to be black-magic to you,
> unless you just want to hide all the details from us.
>
> HTH,

I don't really see it like that, he supplied the equipment that he was
trying to use however he did not state any info about the network which is
why i asked the question i did.

Adair

On 17 Apr 2007 19:54:09 -0700, Paul Zitarelli <(E-Mail Removed)>
wrote in <(E-Mail Removed) .com>:

>Here is my situation:
>
>I rent an apartment on the first floor of a house. My landlord has his
>offices upstairs. There, he has a cable modem and a Linksys WRT54GS.
>That router is then connected into a wall socket using an ethernet
>cable (I assume the other end is in one of the LAN ports of the
>WRT54GS).
>
>Then, on my floor, I connect my wall socket to my router, a Linksys
>BEFW11S4 (Version 3). The only way my router works consistently is to
>connect the wall socket to the Uplink port of my BEFW11S4. However,
>it's only wired connections that work; I have never been able to get
>wireless working. Because of client confidentiality, my landlord does
>not want me to use his wireless connection, so I need some way to get
>mine working.
>
>Several articles explain how to set up my router as an access point. I
>have tried the method described (switching the Device IP address,
>disabling DHCP, changing SSID and channel), but again, things only
>work using the Uplink port. I can never seem to make a direct LAN-LAN
>connection (the lights on my router never come on). And I can never
>get wireless working.
>
>Any thoughts on where the problem might be? Or maybe a way that my
>landlord could give me wireless internet access using his WRT54GS that
>would not give me access to computers on his network? I really
>appreciate any help!

I'm guessing you need a crossover cable to make a connection to a LAN
port instead of the WAN (uplink) port.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

If the socket goes to the lan port on his WRT then u got just as much access
as if you were on his wireless. reset your BEFW11S4 to factory default and
turn off the DHCP server and knock it up an IP if its the same as the WRT.
Plug her into the wall via a LAN port and way u go.

Easy in theory....


Joe.




"Paul Zitarelli" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Here is my situation:
>
> I rent an apartment on the first floor of a house. My landlord has his
> offices upstairs. There, he has a cable modem and a Linksys WRT54GS.
> That router is then connected into a wall socket using an ethernet
> cable (I assume the other end is in one of the LAN ports of the
> WRT54GS).
>
> Then, on my floor, I connect my wall socket to my router, a Linksys
> BEFW11S4 (Version 3). The only way my router works consistently is to
> connect the wall socket to the Uplink port of my BEFW11S4. However,
> it's only wired connections that work; I have never been able to get
> wireless working. Because of client confidentiality, my landlord does
> not want me to use his wireless connection, so I need some way to get
> mine working.
>
> Several articles explain how to set up my router as an access point. I
> have tried the method described (switching the Device IP address,
> disabling DHCP, changing SSID and channel), but again, things only
> work using the Uplink port. I can never seem to make a direct LAN-LAN
> connection (the lights on my router never come on). And I can never
> get wireless working.
>
> Any thoughts on where the problem might be? Or maybe a way that my
> landlord could give me wireless internet access using his WRT54GS that
> would not give me access to computers on his network? I really
> appreciate any help!
>

On Apr 18, 11:36 am, "Adair Witner" <buhbear...@mail.com> wrote:
> <b...@sme-online.com> wrote in message
> > In a nutshell, you need to work on an understanding of how IP works,
> > the functional architecture of a WAP/bridge/router, and the config
> > and
> > troubleshooting of same.
>
> > Meaning how, on what basis, addresses are assigned to what, and
> > how routing is done. Understanding of wireless part a plus.
>
> > Then it's straightforward. Now it seems to be black-magic to you,
> > unless you just want to hide all the details from us.
>
> > HTH,
>
> I don't really see it like that, he supplied the equipment that he was
> trying to use however he did not state any info about the network which is
> why i asked the question i did.
>
> Adair

IOW, it's never simply a matter of plugging cables. Where (logically)
they're
connected is important. That involves net config (IP specifically) and
"where"
on router. Routing config matters, too- "gateway" addressing.

IE, even if you've a bunch of ethernet connections switched together,
(and
10/100 ports _generally_ automatically handle crossing-over), if
they're
on different subnets based on IP/mask, they won't talk.

Sounds like that's one problem, in addition to your wireless config.

PC Mag, among many others, have good book detailing various aspects
of designing & implementing wired & wireless networks.

Still not heard anything re IP specifics.

J

On Apr 19, 6:36 am, b...@sme-online.com wrote:
> On Apr 18, 11:36 am, "Adair Witner" <buhbear...@mail.com> wrote:
>
>
>
> > <b...@sme-online.com> wrote in message
> > > In a nutshell, you need to work on an understanding of how IP works,
> > > the functional architecture of a WAP/bridge/router, and the config
> > > and
> > > troubleshooting of same.
>
> > > Meaning how, on what basis, addresses are assigned to what, and
> > > how routing is done. Understanding of wireless part a plus.
>
> > > Then it's straightforward. Now it seems to be black-magic to you,
> > > unless you just want to hide all the details from us.
>
> > > HTH,
>
> > I don't really see it like that, he supplied the equipment that he was
> > trying to use however he did not state any info about the network which is
> > why i asked the question i did.
>
> > Adair
>
> IOW, it's never simply a matter of plugging cables. Where (logically)
> they're
> connected is important. That involves net config (IP specifically) and
> "where"
> on router. Routing config matters, too- "gateway" addressing.
>
> IE, even if you've a bunch of ethernet connections switched together,
> (and
> 10/100 ports _generally_ automatically handle crossing-over), if
> they're
> on different subnets based on IP/mask, they won't talk.
>
> Sounds like that's one problem, in addition to your wireless config.
>
> PC Mag, among many others, have good book detailing various aspects
> of designing & implementing wired & wireless networks.
>
> Still not heard anything re IP specifics.
>
> J

Thanks to all for your responses, and I'm sorry if my initial post was
lacking in information. Part of the problem is that my landlord is
paranoid, so I have had trouble accessing his router to see where
things are plugged in. When I have more information, I will send it
along.

Forster Tuncurry wrote:
> After getting connected we should find out why he is so paranoid.... *smerk*
>
> J.
>
> "Paul Zitarelli" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
>> On Apr 19, 6:36 am, b...@sme-online.com wrote:
>>> On Apr 18, 11:36 am, "Adair Witner" <buhbear...@mail.com> wrote:
>>>
>>>
>>>
>>>> <b...@sme-online.com> wrote in message
>>>>> In a nutshell, you need to work on an understanding of how IP works,
>>>>> the functional architecture of a WAP/bridge/router, and the config
>>>>> and
>>>>> troubleshooting of same.
>>>>> Meaning how, on what basis, addresses are assigned to what, and
>>>>> how routing is done. Understanding of wireless part a plus.
>>>>> Then it's straightforward. Now it seems to be black-magic to you,
>>>>> unless you just want to hide all the details from us.
>>>>> HTH,
>>>> I don't really see it like that, he supplied the equipment that he was
>>>> trying to use however he did not state any info about the network which
>>>> is
>>>> why i asked the question i did.
>>>> Adair
>>> IOW, it's never simply a matter of plugging cables. Where (logically)
>>> they're
>>> connected is important. That involves net config (IP specifically) and
>>> "where"
>>> on router. Routing config matters, too- "gateway" addressing.
>>>
>>> IE, even if you've a bunch of ethernet connections switched together,
>>> (and
>>> 10/100 ports _generally_ automatically handle crossing-over), if
>>> they're
>>> on different subnets based on IP/mask, they won't talk.
>>>
>>> Sounds like that's one problem, in addition to your wireless config.
>>>
>>> PC Mag, among many others, have good book detailing various aspects
>>> of designing & implementing wired & wireless networks.
>>>
>>> Still not heard anything re IP specifics.
>>>
>>> J
>> Thanks to all for your responses, and I'm sorry if my initial post was
>> lacking in information. Part of the problem is that my landlord is
>> paranoid, so I have had trouble accessing his router to see where
>> things are plugged in. When I have more information, I will send it
>> along.
>>
>
>
Please don't change posting styles in a thread.

Paul Zitarelli wrote:

>> J
>
> Thanks to all for your responses, and I'm sorry if my initial post was
> lacking in information. Part of the problem is that my landlord is
> paranoid, so I have had trouble accessing his router to see where
> things are plugged in. When I have more information, I will send it
> along.
>
More likely it sounds like he is cautious and clueless. It is his router
so there is no reason you should be accessing it and surely he doesn't
understand how insecure this arrangement is.