2 routers - 1 T1 physical connection -- How best to do this?

Our current setup: T1 line to ISP-provided Cisco router >> our 5-line SOHO
router >> server's external NIC; off of the SOHO router, I have a wireless
router connected via cross-over cable with the goal of providing guest
access. IP's as follows:
SOHO router
LAN side: 192.168.1.1
Wireless router
WAN side: 192.168.1.2 Default Gateway: 192.168.1.1
LAN side: 192.168.2.1, and it's set as a DHCP server

Problem: Can't get the wireless side to work. I think it's my setup. Maybe
if I hang it off the Cisco router using a spare public IP I can get it to
work.

What I want to do: run a cable from the Cisco router to a 'dumb' hub, then
connect each router (SOHO and wireless) to it and assign each a public IP,
and each will be on a separate private network.

Will this work? Any problems foreseen?

--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a conservation non-profit (501 (c)(3)) organization
Wood River, NE

Mike in Nebraska <(E-Mail Removed)> wrote:
> Our current setup: T1 line to ISP-provided Cisco router >> our 5-line
> SOHO router >> server's external NIC; off of the SOHO router, I have
> a wireless router connected via cross-over cable with the goal of
> providing guest access. IP's as follows:
> SOHO router
> LAN side: 192.168.1.1
> Wireless router
> WAN side: 192.168.1.2 Default Gateway: 192.168.1.1
> LAN side: 192.168.2.1, and it's set as a DHCP server
>
> Problem: Can't get the wireless side to work. I think it's my setup.
> Maybe if I hang it off the Cisco router using a spare public IP I can
> get it to work.
>
> What I want to do: run a cable from the Cisco router to a 'dumb' hub,

Why not a small Ethernet switch?

> then connect each router (SOHO and wireless) to it and assign each a
> public IP, and each will be on a separate private network.

That sounds perfect.
>
> Will this work? Any problems foreseen?

That's exactly what I'd do.

I'd use a small hub simply because I've got one in a drawer.

Thanks.

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:(E-Mail Removed)...
> Mike in Nebraska <(E-Mail Removed)> wrote:
>> Our current setup: T1 line to ISP-provided Cisco router >> our 5-line
>> SOHO router >> server's external NIC; off of the SOHO router, I have
>> a wireless router connected via cross-over cable with the goal of
>> providing guest access. IP's as follows:
>> SOHO router
>> LAN side: 192.168.1.1
>> Wireless router
>> WAN side: 192.168.1.2 Default Gateway: 192.168.1.1
>> LAN side: 192.168.2.1, and it's set as a DHCP server
>>
>> Problem: Can't get the wireless side to work. I think it's my setup.
>> Maybe if I hang it off the Cisco router using a spare public IP I can
>> get it to work.
>>
>> What I want to do: run a cable from the Cisco router to a 'dumb' hub,
>
> Why not a small Ethernet switch?
>
>> then connect each router (SOHO and wireless) to it and assign each a
>> public IP, and each will be on a separate private network.
>
> That sounds perfect.
>>
>> Will this work? Any problems foreseen?
>
> That's exactly what I'd do.
>
>
>

Mike in Nebraska <(E-Mail Removed)> wrote:
> I'd use a small hub simply because I've got one in a drawer.

You can pick up a 4-port Ethernet switch at Radio Shack for a song - I'd do
it. I tossed out all my hubs a long time ago (except for one, which wouold
be useful when running Ethereal, etc, if I ever managed to figure out how to
interpret Ethereal data).
>
> Thanks.
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> wrote in
> message news:(E-Mail Removed)...
>> Mike in Nebraska <(E-Mail Removed)> wrote:
>>> Our current setup: T1 line to ISP-provided Cisco router >> our
>>> 5-line SOHO router >> server's external NIC; off of the SOHO
>>> router, I have a wireless router connected via cross-over cable
>>> with the goal of providing guest access. IP's as follows:
>>> SOHO router
>>> LAN side: 192.168.1.1
>>> Wireless router
>>> WAN side: 192.168.1.2 Default Gateway: 192.168.1.1
>>> LAN side: 192.168.2.1, and it's set as a DHCP server
>>>
>>> Problem: Can't get the wireless side to work. I think it's my
>>> setup. Maybe if I hang it off the Cisco router using a spare public
>>> IP I can get it to work.
>>>
>>> What I want to do: run a cable from the Cisco router to a 'dumb'
>>> hub,
>>
>> Why not a small Ethernet switch?
>>
>>> then connect each router (SOHO and wireless) to it and assign each a
>>> public IP, and each will be on a separate private network.
>>
>> That sounds perfect.
>>>
>>> Will this work? Any problems foreseen?
>>
>> That's exactly what I'd do.

I'll do that, thanks.

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:%(E-Mail Removed)...
> Mike in Nebraska <(E-Mail Removed)> wrote:
>> I'd use a small hub simply because I've got one in a drawer.
>
> You can pick up a 4-port Ethernet switch at Radio Shack for a song - I'd
> do it. I tossed out all my hubs a long time ago (except for one, which
> wouold be useful when running Ethereal, etc, if I ever managed to figure
> out how to interpret Ethereal data).
>>
>> Thanks.
>>
>> "Lanwench [MVP - Exchange]"
>> <(E-Mail Removed) hoo.com> wrote in
>> message news:(E-Mail Removed)...
>>> Mike in Nebraska <(E-Mail Removed)> wrote:
>>>> Our current setup: T1 line to ISP-provided Cisco router >> our
>>>> 5-line SOHO router >> server's external NIC; off of the SOHO
>>>> router, I have a wireless router connected via cross-over cable
>>>> with the goal of providing guest access. IP's as follows:
>>>> SOHO router
>>>> LAN side: 192.168.1.1
>>>> Wireless router
>>>> WAN side: 192.168.1.2 Default Gateway: 192.168.1.1
>>>> LAN side: 192.168.2.1, and it's set as a DHCP server
>>>>
>>>> Problem: Can't get the wireless side to work. I think it's my
>>>> setup. Maybe if I hang it off the Cisco router using a spare public
>>>> IP I can get it to work.
>>>>
>>>> What I want to do: run a cable from the Cisco router to a 'dumb'
>>>> hub,
>>>
>>> Why not a small Ethernet switch?
>>>
>>>> then connect each router (SOHO and wireless) to it and assign each a
>>>> public IP, and each will be on a separate private network.
>>>
>>> That sounds perfect.
>>>>
>>>> Will this work? Any problems foreseen?
>>>
>>> That's exactly what I'd do.
>
>
>