Discussion:
[IPCop-user] How to setup Linksys router?
Larry Alkoff
2009-01-18 16:13:18 UTC
Permalink
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL router
for wifi and have problems connecting.

On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.

At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green I can ping the IPCop gateway at 192.168.1.254.

I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.

How can I get the Linksys router working?

Larry
Carl E Meece III
2009-01-18 17:36:02 UTC
Permalink
Post by Larry Alkoff
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL router
for wifi and have problems connecting.
On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.
At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green I can ping the IPCop gateway at 192.168.1.254.
I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.
How can I get the Linksys router working?
Larry
------------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
I'm assuming you've tried more than one Cat5 cable. Bad cables do happen.

I also have a Linksys router on Blue. I have Blue connected to a LAN
port so all routing is handled by IPcop. Check IPcop DHCP Server and
make sure the "IP Address/Netmask" for Blue Interface is the same as the
LAN IP Address/Netmask on the Linksys.

It should just work. If not, try a different router or access point.
If it still doesn't work, swap out the Blue NIC.

~ Carl
Carl E Meece III
2009-01-18 17:40:37 UTC
Permalink
Post by Carl E Meece III
Post by Larry Alkoff
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL router
for wifi and have problems connecting.
On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.
At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green I can ping the IPCop gateway at 192.168.1.254.
I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.
How can I get the Linksys router working?
Larry
------------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
I'm assuming you've tried more than one Cat5 cable. Bad cables do happen.
I also have a Linksys router on Blue. I have Blue connected to a LAN
port so all routing is handled by IPcop. Check IPcop DHCP Server and
make sure the "IP Address/Netmask" for Blue Interface is the same as the
LAN IP Address/Netmask on the Linksys.
It should just work. If not, try a different router or access point.
If it still doesn't work, swap out the Blue NIC.
~ Carl
I also have Blue setup to use the same gateway and DNS server as green,
try that...

~ Carl
Larry Alkoff
2009-01-25 18:59:28 UTC
Permalink
Carl I have not had much luck setting up the Linksys
and would like to try your method. That is, I would like to seup my
Linksys and configuration the same as yours. My comments inline.
Post by Carl E Meece III
Post by Carl E Meece III
Post by Larry Alkoff
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL router
for wifi and have problems connecting.
On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.
At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green I can ping the IPCop gateway at 192.168.1.254.
I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.
How can I get the Linksys router working?
Larry
------------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
I'm assuming you've tried more than one Cat5 cable. Bad cables do happen.
Yes I have tried several cables.
Post by Carl E Meece III
Post by Carl E Meece III
I also have a Linksys router on Blue. I have Blue connected to a LAN
port so all routing is handled by IPcop.
I have a Linksys wrt54gl connected from the Linksys lan port to the Blue
nic on IPCop. I have also tried a Linksys wrt54g (not the l=linux
version). The Linksys routers get dhcp from IPCop and do not themselves
serve dhcp.

I am able to surf to an occasional web site using a laptop connected to
the lan port of the Linksys but only one site - then I cannot connect
any more.
Post by Carl E Meece III
Post by Carl E Meece III
Check IPcop DHCP Server and
The IPCop dhcp server is on.
Post by Carl E Meece III
Post by Carl E Meece III
make sure the "IP Address/Netmask" for Blue Interface is the same as the
LAN IP Address/Netmask on the Linksys.
I'm not sure what to do here.
My Linksys has it's web admin server at the default 192.168.1.1.
The gateway address of IPCop Blue is 192.168.1.254.
The gateway address of IPCop Green is 10.22.44.254.

Should I be using Linksys > Setup > Advanced routing?
There are settings for Gateway and Router.
Under Gateway I set:
Destination lan ip 10.22.44.0
Subnet mask: 254.254.254.0
Default gateway 10.22.44.254
Interface lan and wireless
Post by Carl E Meece III
Post by Carl E Meece III
It should just work. If not, try a different router or access point.
If it still doesn't work, swap out the Blue NIC.
~ Carl
I also have Blue setup to use the same gateway and DNS server as green,
try that...
I think that is the present setting as shown above.
Post by Carl E Meece III
~ Carl
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.

Larry Alkoff
Haute SubZero
2009-01-25 21:56:19 UTC
Permalink
Post by Larry Alkoff
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.
Larry Alkoff
I think your best approach might be to start from scratch, assuming
nothing you've done so far was valid. I know that's a hard pill to
swallow some times, but after 30 years of dealing with computers I still
find that's the best way when you get really confused.

The key here is that you don't want the Linksys to route anything, you
only want to use it as a switch. If you happen to add the wireless part
into that then it is by definition an Access Point, which is in simplest
terms just a wireless switch. That means 2 primary things, The LAN side
of the Linksys has to have an IP assigned since you have to be able to
administer it for wireless access, and any routing, dhcp, etc., should
be turned off. For the sake of simplicity I would try this process on
the GREEN network first, just to eliminate the blue quirks. Once you
have it working there, you should be able to change the router's LAN IP
(remember, it will only request a DHCP address from the WAN port) then
move it to BLUE. You'll need to add the appropriate MAC or IP addresses
in IPCop at that point, but once you have it working on GREEN you should
really only have to deal with IPCop changes, not the router itself
(except of course for the single LAN IP change).

Hope this all makes sense. I've done at least half a dozen different
wireless routers this way in various locations and they all work the
same way, so I'm confident the Linksys will too no matter which flavor
it is.
solanth
2009-01-25 23:29:22 UTC
Permalink
Post by Haute SubZero
Post by Larry Alkoff
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.
Larry Alkoff
I find it also a great help to start from scratch.
the wireless AP is transparent ie no part in the routing and its ip address is
only for setup.
to add to Haute's words
also disable wep/wap and dont hide the SSID
Users use
GW is IPCOP (green NIC ip if on green network)
DNS is IPCOP green NIC (unless sep DNS server running)
once this works add the other stages one at a time
rgds Ian
Post by Haute SubZero
I think your best approach might be to start from scratch, assuming
nothing you've done so far was valid. I know that's a hard pill to
swallow some times, but after 30 years of dealing with computers I still
find that's the best way when you get really confused.
The key here is that you don't want the Linksys to route anything, you
only want to use it as a switch. If you happen to add the wireless part
into that then it is by definition an Access Point, which is in simplest
terms just a wireless switch. That means 2 primary things, The LAN side
of the Linksys has to have an IP assigned since you have to be able to
administer it for wireless access, and any routing, dhcp, etc., should
be turned off. For the sake of simplicity I would try this process on
the GREEN network first, just to eliminate the blue quirks. Once you
have it working there, you should be able to change the router's LAN IP
(remember, it will only request a DHCP address from the WAN port) then
move it to BLUE. You'll need to add the appropriate MAC or IP addresses
in IPCop at that point, but once you have it working on GREEN you should
really only have to deal with IPCop changes, not the router itself
(except of course for the single LAN IP change).
Hope this all makes sense. I've done at least half a dozen different
wireless routers this way in various locations and they all work the
same way, so I'm confident the Linksys will too no matter which flavor
it is.
---------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
Larry Alkoff
2009-01-26 02:03:29 UTC
Permalink
Post by solanth
Post by Haute SubZero
Post by Larry Alkoff
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.
Larry Alkoff
I find it also a great help to start from scratch.
the wireless AP is transparent ie no part in the routing and its ip address is
only for setup.
to add to Haute's words
also disable wep/wap and dont hide the SSID
Users use
GW is IPCOP (green NIC ip if on green network)
DNS is IPCOP green NIC (unless sep DNS server running)
once this works add the other stages one at a time
rgds Ian
Post by Haute SubZero
I think your best approach might be to start from scratch, assuming
nothing you've done so far was valid. I know that's a hard pill to
swallow some times, but after 30 years of dealing with computers I still
find that's the best way when you get really confused.
The key here is that you don't want the Linksys to route anything, you
only want to use it as a switch. If you happen to add the wireless part
into that then it is by definition an Access Point, which is in simplest
terms just a wireless switch. That means 2 primary things, The LAN side
of the Linksys has to have an IP assigned since you have to be able to
administer it for wireless access, and any routing, dhcp, etc., should
be turned off. For the sake of simplicity I would try this process on
the GREEN network first, just to eliminate the blue quirks. Once you
have it working there, you should be able to change the router's LAN IP
(remember, it will only request a DHCP address from the WAN port) then
move it to BLUE. You'll need to add the appropriate MAC or IP addresses
in IPCop at that point, but once you have it working on GREEN you should
really only have to deal with IPCop changes, not the router itself
(except of course for the single LAN IP change).
Hope this all makes sense. I've done at least half a dozen different
wireless routers this way in various locations and they all work the
same way, so I'm confident the Linksys will too no matter which flavor
it is.
Dear Haute Subzero and solanth.

Hello to both of you and thanks for your help.
I am trying to place your ideas into action
and am logging every step.

What I have done so far:
System map on Blue:
IPcop Blue if on 192.168.1.254 connected to a switch.
Dell laptop with both wired and wifi.
Cat5 connected to switch
but wifi disconnected with wlassistant.
Linksys wrt54gl NOT connected to switch.

Note: Blue Access page on IPcop has all 3 mac entries for Linksys, plus
2 mac entries for Dell wired port and wifi port.

Result:
Can ping both Blue 192.168.1.254 and Dell 192.168.1.24
Can surf the web with no problems using Firefox.

Next step:
Reset the Linksys by pressing the reset button for 1 minute.
This places Linksys on
Connect Linksys lan port to switch.
Result:
Can no longer surf the web.
Error message is: cannot find server
Can still ping both Blue on .254 and Dell on .24
plus Linksys at 192.168.1.1

Next step:
Use wlassistant to connect the Dell wifi to the Linksys router.
Result:
wlassistant reports sucessful connection.
Can still ping Blue, Dell and Linksys.
Can not surf - get cannot find server msg.

Does this give you any hints on what might be going wrong?
solanth
2009-01-26 03:51:48 UTC
Permalink
Post by Larry Alkoff
Post by solanth
Post by Haute SubZero
Post by Larry Alkoff
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.
Larry Alkoff
I find it also a great help to start from scratch.
the wireless AP is transparent ie no part in the routing and its ip
address is only for setup.
to add to Haute's words
also disable wep/wap and dont hide the SSID
Users use
GW is IPCOP (green NIC ip if on green network)
DNS is IPCOP green NIC (unless sep DNS server running)
once this works add the other stages one at a time
rgds Ian
Post by Haute SubZero
I think your best approach might be to start from scratch, assuming
nothing you've done so far was valid. I know that's a hard pill to
swallow some times, but after 30 years of dealing with computers I still
find that's the best way when you get really confused.
The key here is that you don't want the Linksys to route anything, you
only want to use it as a switch. If you happen to add the wireless part
into that then it is by definition an Access Point, which is in simplest
terms just a wireless switch. That means 2 primary things, The LAN side
of the Linksys has to have an IP assigned since you have to be able to
administer it for wireless access, and any routing, dhcp, etc., should
be turned off. For the sake of simplicity I would try this process on
the GREEN network first, just to eliminate the blue quirks. Once you
have it working there, you should be able to change the router's LAN IP
(remember, it will only request a DHCP address from the WAN port) then
move it to BLUE. You'll need to add the appropriate MAC or IP addresses
in IPCop at that point, but once you have it working on GREEN you should
really only have to deal with IPCop changes, not the router itself
(except of course for the single LAN IP change).
Hope this all makes sense. I've done at least half a dozen different
wireless routers this way in various locations and they all work the
same way, so I'm confident the Linksys will too no matter which flavor
it is.
Dear Haute Subzero and solanth.
Hello to both of you and thanks for your help.
I am trying to place your ideas into action
and am logging every step.
IPcop Blue if on 192.168.1.254 connected to a switch.
Dell laptop with both wired and wifi.
Cat5 connected to switch
but wifi disconnected with wlassistant.
Linksys wrt54gl NOT connected to switch.
Note: Blue Access page on IPcop has all 3 mac entries for Linksys, plus
2 mac entries for Dell wired port and wifi port.
Can ping both Blue 192.168.1.254 and Dell 192.168.1.24
Can surf the web with no problems using Firefox.
Reset the Linksys by pressing the reset button for 1 minute.
This places Linksys on
Connect Linksys lan port to switch.
This may have set the linksys to provide DHCP
therefore would provide GW which will prob be wrong
the linksys has to have DHCP off
set linksys up with a static IP address in the blue range with its GW as ipcop
Blue .
Do not use the linksys as a wireless client GW ,they need to have the IPCOP
blue interface as a their GW
Post by Larry Alkoff
Can no longer surf the web.
Error message is: cannot find server
Can still ping both Blue on .254 and Dell on .24
plus Linksys at 192.168.1.1
Use wlassistant to connect the Dell wifi to the Linksys router.
wlassistant reports sucessful connection.
Can still ping Blue, Dell and Linksys.
Can not surf - get cannot find server msg.
Does this give you any hints on what might be going wrong?
---------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
Brad Morgan
2009-01-26 03:28:49 UTC
Permalink
Next step:
Reset the Linksys by pressing the reset button for 1 minute.
This places Linksys on
Connect Linksys lan port to switch.
Result:
Can no longer surf the web.
Error message is: cannot find server
Can still ping both Blue on .254 and Dell on .24
plus Linksys at 192.168.1.1

The Linksys router CANNOT be used this way in its factory default
configuration. Your results don't surprise me at all.

After resetting the Linksys to its factory defaults, you must connect to it
via a wired LAN port, turn off DHCP, and set an IP address and subnet mask
on the blue network.

The 4 LAN ports (and the wireless) on the Linksys are now a switch so you
don't need another switch, you can connect one of the LAN ports directly to
the Blue NIC. Your Dell laptop should work with a wire connected to one of
the other LAN ports or wirelessly. Make sure you only have one connection
active at a time on the laptop.

You don't say how you configured the laptop network connections. If it was
manually, what did you use for the gateway and DNS IP addresses? It would be
best if the laptop wireless and the laptop wired had two different IP
addresses. You can turn DHCP on Blue on if you want.

I'd suggest that you provide some screenshots of the relevant pages on IPCop
and the configuration of the network connections on the laptop. Perhaps one
of the Linksys Router. Alternatively, I can provide screenshots of a working
configuration.

Regards,

Brad
Rick Kunath
2009-01-26 12:57:39 UTC
Permalink
Post by Brad Morgan
You don't say how you configured the laptop network connections. If it was
manually, what did you use for the gateway and DNS IP addresses? It would be
best if the laptop wireless and the laptop wired had two different IP
addresses. You can turn DHCP on Blue on if you want.
I'd suggest that you provide some screenshots of the relevant pages on IPCop
and the configuration of the network connections on the laptop. Perhaps one
of the Linksys Router. Alternatively, I can provide screenshots of a working
configuration.
Seems to me trying to use a cascaded router on Blue is just so much
extra work. And undesirable anyway.

Get a wireless AP device that can be set to transparent bridge mode, set
it that way, give the wireless access point a static IP on Blue and be
done with it. You don't need (or want) a router on Blue.

That's what IP Cop is for.

Then sit back and enjoy while IP Cop does it's thing. The Blue interface
on IP Cop can handle everything else.

I've been using an Orinoco device in transparent bridge mode for years
with no issues. A router/wireless AP is not the ideal device to connect
to Blue.

Rick Kunath
Brad Morgan
2009-01-26 15:28:19 UTC
Permalink
Post by Rick Kunath
Seems to me trying to use a cascaded router on Blue is just so much
extra work. And undesirable anyway.
Get a wireless AP device that can be set to transparent bridge mode, set
it that way, give the wireless access point a static IP on Blue and be
done with it. You don't need (or want) a router on Blue.
Rick, you are correct, we don't want a router. The instructions being given
are to configure the Linksys Router as an access point (i.e. NOT using it as
a Router).

A wireless access point is already a "transparent bridge", so we don't need
to purchase anything else. One of the reasons for buying a Linksys Router
instead of a Linksys Access Point is that the router is about 1/2 the price
of the access point.

I've done the "router as an access point" configuration at least 10 times
for various clients and my home network using Linksys and other brands of
wireless routers.

Regards,

Brad
Rick Kunath
2009-01-26 16:10:44 UTC
Permalink
Post by Brad Morgan
A wireless access point is already a "transparent bridge",
Not necessarily.
Post by Brad Morgan
so we don't need
to purchase anything else. One of the reasons for buying a Linksys Router
instead of a Linksys Access Point is that the router is about 1/2 the price
of the access point.
So are all NAT and routing functions of the device disabled (or can they
be)?

Is the device doing pure security and the rest pass-through? No DHCP, No
NAT, No gateway? Just Rf to Ethernet conversion with wireless encryption?

Rick Kunath
David Sims
2009-01-26 16:48:08 UTC
Permalink
Hi Rick,

A linksys wireless router such as the WRT54G is multiple devices in one,
and has the 'attribute' of being cheaper than lots of standalone
devices at retail in the US.... First, it is an ethernet switch with 4
10/100 wired ports, second it is a WiFi B/G access point with the radio
bridged to the Ethernet switch and third it is a PNAT firewall/router....

So...

You can use these functions individually or in various combinations....
but you have to be a bit careful with addressing... and which ports you
are plugging things into or you get unintended results and/or a lack
of intended fuction.... I have personally used WRT45Gs as a bare AP with
success.... but now that Cisco has remodeled their product line, the
WRT54Gs are hard to find....

I also agree that it is easier to just use an access point though... A
very good multifunction access point, the EdiMax EW-7206APG is available
from Newegg for $31:

http://www.newegg.com/Product/Product.aspx?Item=N82E16817201523

This product can be used as a bridged AP or as a client or as a repeater
and has a detachable antenna (i.e., you can use a seperate high-gain
antenna for long-distance applications) but only a single ethernet
port....

I am currently using a pair of these with directional antennas to bridge
an ethernet over a few miles.... and they are commonly used in Australia
to provide wide-area internet services....

Dave
***************************************************************************
Post by Rick Kunath
Post by Brad Morgan
A wireless access point is already a "transparent bridge",
Not necessarily.
Post by Brad Morgan
so we don't need
to purchase anything else. One of the reasons for buying a Linksys Router
instead of a Linksys Access Point is that the router is about 1/2 the price
of the access point.
So are all NAT and routing functions of the device disabled (or can they
be)?
Is the device doing pure security and the rest pass-through? No DHCP, No
NAT, No gateway? Just Rf to Ethernet conversion with wireless encryption?
Rick Kunath
------------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
Brad Morgan
2009-01-26 17:22:54 UTC
Permalink
Post by Rick Kunath
Post by Brad Morgan
A wireless access point is already a "transparent bridge",
Not necessarily.
I'd like to understand the differences. Can you explain them?
Post by Rick Kunath
So are all NAT and routing functions of the device disabled (or can they
be)?
The Linksys Router has a WAN port, 4 LAN ports (a switch), and wireless. To
configure as an access point, we disable DHCP on the LAN ports, configure
the wireless security, and don't plug anything into the WAN port. Since
there's nothing in the WAN port, the NAT and routing functions are ignored
instead of disabled.
Post by Rick Kunath
Is the device doing pure security and the rest pass-through? No DHCP, No
NAT, No gateway? Just Rf to Ethernet conversion with wireless encryption?
In the above configuration, yes.

Regards,

Brad
Larry Alkoff
2009-01-26 18:07:13 UTC
Permalink
Post by Larry Alkoff
Reset the Linksys by pressing the reset button for 1 minute.
This places Linksys on
Connect Linksys lan port to switch.
Can no longer surf the web.
Error message is: cannot find server
Can still ping both Blue on .254 and Dell on .24
plus Linksys at 192.168.1.1
The Linksys router CANNOT be used this way in its factory default
configuration. Your results don't surprise me at all.
After resetting the Linksys to its factory defaults, you must connect to it
via a wired LAN port, turn off DHCP, and set an IP address and subnet mask
on the blue network.
The 4 LAN ports (and the wireless) on the Linksys are now a switch so you
don't need another switch, you can connect one of the LAN ports directly to
the Blue NIC. Your Dell laptop should work with a wire connected to one of
the other LAN ports or wirelessly. Make sure you only have one connection
active at a time on the laptop.
You don't say how you configured the laptop network connections. If it was
manually, what did you use for the gateway and DNS IP addresses? It would be
best if the laptop wireless and the laptop wired had two different IP
addresses. You can turn DHCP on Blue on if you want.
I'd suggest that you provide some screenshots of the relevant pages on IPCop
and the configuration of the network connections on the laptop. Perhaps one
of the Linksys Router. Alternatively, I can provide screenshots of a working
configuration.
Regards,
Brad
Hi Brad.


I'm going to try what you said on Blue.
I finally understand from you and solanth why the WAN port and setup
should be ignored.

If you would please provide some screenshots of a working configuration
that would be greatly appreciated.

I never really learned how to make screenshots and want to focus on
getting the router running.

Larry
David Meed
2009-01-27 02:02:08 UTC
Permalink
Post by Larry Alkoff
Reset the Linksys by pressing the reset button for 1 minute.
This places Linksys on
Connect Linksys lan port to switch.
Can no longer surf the web.
Error message is: cannot find server
Can still ping both Blue on .254 and Dell on .24
plus Linksys at 192.168.1.1
The Linksys router CANNOT be used this way in its factory default
configuration. Your results don't surprise me at all.
After resetting the Linksys to its factory defaults, you must connect to it
via a wired LAN port, turn off DHCP, and set an IP address and subnet mask
on the blue network.
All you have to do is (30 second) reset the Linksys, connect it to a
dhcp laptop on the LAN ports, wait until the laptop is assigned an IP,
then browse to 192.168.1.1 (the router default address). On the first
setup page about 2/3 of the way down is a radio button for DHCP
enable/disable. Select disable. All the rest of dhcp settings should
gray out. Save the changes at the bottom and reboot the router (power
down for 20 seconds). Don't do the 30 seconds reset button thing
again because that will turn dhcp on again.

Now a cable connected from another LAN port to the IPCop box should
allow you to browse and surf once the laptop releases the DHCP it was
assigned by the linksys and renewed on the IPCop DHCP. (THat may be
tripping you up - if the laptop retains the linksys DHCP settings it
will still be trying to us 192.168.1.1 as a gateway instead of
192.168.254.254 as assigned by IPCop. If you can't command a
release/renew for dhcp, try unplugging the laptop LAN cable for a
minute and then plugging it in again.


-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Larry Alkoff
2009-01-27 09:06:40 UTC
Permalink
Post by David Meed
Post by Larry Alkoff
Reset the Linksys by pressing the reset button for 1 minute.
This places Linksys on
Connect Linksys lan port to switch.
Can no longer surf the web.
Error message is: cannot find server
Can still ping both Blue on .254 and Dell on .24
plus Linksys at 192.168.1.1
The Linksys router CANNOT be used this way in its factory default
configuration. Your results don't surprise me at all.
After resetting the Linksys to its factory defaults, you must connect to it
via a wired LAN port, turn off DHCP, and set an IP address and subnet mask
on the blue network.
All you have to do is (30 second) reset the Linksys, connect it to a
dhcp laptop on the LAN ports, wait until the laptop is assigned an IP,
then browse to 192.168.1.1 (the router default address). On the first
setup page about 2/3 of the way down is a radio button for DHCP
enable/disable. Select disable. All the rest of dhcp settings should
gray out. Save the changes at the bottom and reboot the router (power
down for 20 seconds). Don't do the 30 seconds reset button thing
again because that will turn dhcp on again.
Now a cable connected from another LAN port to the IPCop box should
allow you to browse and surf once the laptop releases the DHCP it was
assigned by the linksys and renewed on the IPCop DHCP. (THat may be
tripping you up - if the laptop retains the linksys DHCP settings it
will still be trying to us 192.168.1.1 as a gateway instead of
192.168.254.254 as assigned by IPCop. If you can't command a
release/renew for dhcp, try unplugging the laptop LAN cable for a
minute and then plugging it in again.
-----
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Thank you very much David.
This has helped me a lot.
It seems to be working good now although I'm not sure what actually
happened!

First I did your first paragraph:
Reset Linksys 30 secs.
Connect Dell set for dhcp to a wired port (wifi interface disabled)
ifconfig down then ifconfig up
browse to 192.168.1.1 to get web interface.
Disable dhcp on Linksys and save.
Cycle power on Linksys.

Second paragraph:
Connect cable to Blue port on IPCop.
ifconfig up on laptop to set Blue dhcp.
Now I can both surf to the Linksys web interface and the web.

My third paragraph:
Disable wired interface on Dell and disconnect cable.
Enable wifi interface on Dell.
Use iwconfig to connect.
Now I can connect to Linksys by wifi including Linksys web interface
and surf the web !!!

This was just so so easy. I guess others were telling me the same basic
thing but all I know is have been beating my head against the wall for
10 days.

Apparently I was missing the part about resetting the Linksys by cycling
the power to adjust the dhcp's from the Linksys to Blue.

Now a question. Will it be possible or advisable to keep the Dell wifi
set on Blue but also enable the wired interface back to Green so I can
go back and forth?

And a second question. I'm going down to Costa Rica for a week Sunday
and need to be able to use my Skype for a phone connection. The Skype
looks just like a wired telephone except it plugs into a wired lan port.
Of course, most of the hotels down there use wifi only.

So my question is - can I somehow bridge the connection from my Dell
wifi to the wired port so I can connect the Skype phone to the wired
port but still connect to the hotel system by wifi. This question is a
little far afield but you seem to have such a good handle on these
networking issues that you might know.

Again I'm very grateful for your help and your sticking with helping me.
It was just so darn easy - it's embarrassing!

Larry
David Meed
2009-01-27 12:54:35 UTC
Permalink
Post by Larry Alkoff
And a second question. I'm going down to Costa Rica for a week Sunday
and need to be able to use my Skype for a phone connection. The Skype
looks just like a wired telephone except it plugs into a wired lan port.
Of course, most of the hotels down there use wifi only.
So my question is - can I somehow bridge the connection from my Dell
wifi to the wired port so I can connect the Skype phone to the wired
port but still connect to the hotel system by wifi. This question is a
Don't know Skype phone at all. But some basic networking issues you
will have to work out.

First question: Does the phone autosense the lan connection, or will
you have to use a hub/switch or crossover cable to connect it to the
laptop.

Second question: Does the phone do dhcp only or will it allow you to
set a static IP. If it has a option for static IP setup, you might be
able to do that (set a fixed address for the laptop, a fixed address
for the phone on the same network/subnet and point the phone gateway
at the laptop.) If it is dhcp you'd have to find a dhcp server and
set that up on the laptop for the wired interface.

I haven't tried bridge connections myself, so you will just have to
try it and see what happens...

You should be able to set it up to work right there on your own home
network to test it out before you go. Another gotcha on the road may
be bandwidth or traffic type restrictions at the motel that don't
allow skype to work, but it's certainly worth a try.


-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Administrator
2009-01-27 13:46:15 UTC
Permalink
| >And a second question. I'm going down to Costa Rica for a
| week Sunday
| >and need to be able to use my Skype for a phone connection.
| The Skype
| >looks just like a wired telephone except it plugs into a
| wired lan port.
| >Of course, most of the hotels down there use wifi only.
| >
| >So my question is - can I somehow bridge the connection from my Dell
| >wifi to the wired port so I can connect the Skype phone to the wired
| >port but still connect to the hotel system by wifi. This
| question is a

Wouldn't it just be simpler to get a PC headphone set and use skype through
the laptop?

David
Larry Alkoff
2009-01-27 16:26:23 UTC
Permalink
Post by Administrator
| >And a second question. I'm going down to Costa Rica for a
| week Sunday
| >and need to be able to use my Skype for a phone connection.
| The Skype
| >looks just like a wired telephone except it plugs into a
| wired lan port.
| >Of course, most of the hotels down there use wifi only.
| >
| >So my question is - can I somehow bridge the connection from my Dell
| >wifi to the wired port so I can connect the Skype phone to the wired
| >port but still connect to the hotel system by wifi. This
| question is a
Wouldn't it just be simpler to get a PC headphone set and use skype through
the laptop?
David
That's my backup plan. I've used the headphones with hotel wifi
on this same Dell Linux laptop before.

However, the Skype phone is really neato. Looks and works just a POTS
phone.

Larry

David Meed
2009-01-27 12:41:41 UTC
Permalink
Post by Larry Alkoff
It seems to be working good now although I'm not sure what actually
happened!
Apparently I was missing the part about resetting the Linksys by cycling
the power to adjust the dhcp's from the Linksys to Blue.
I'm glad it worked out. Sometimes I have beat my head against the
wall for days until some tiny little switch fixed it and it all
worked. In retrospect it was usually the simplest gotcha that tripped
me up. I guess that is part of the techie life - maximum frustration
followed by great relief and satisfaction, and that faint hope is what
keeps us trying one more test in the frustrating times.
Post by Larry Alkoff
Now a question. Will it be possible or advisable to keep the Dell wifi
set on Blue but also enable the wired interface back to Green so I can
go back and forth?
IMHO you should be able to use either as long as you don't use both at
the same time. And I don't know why, it just seems like a bad idea to
have something other than IPCop across both green (secure) and blue
(less secure) at the same time. IPCop wouldn't know which interface
to send the packets out to. Someone who knows IPCop better than I
will be able to tell you the real reason.



Punt the second question to another thread...

-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Carl Meece
2009-01-26 08:19:07 UTC
Permalink
Post by Larry Alkoff
Post by Carl E Meece III
Post by Carl E Meece III
make sure the "IP Address/Netmask" for Blue Interface is the same as the
LAN IP Address/Netmask on the Linksys.
I'm not sure what to do here.
My Linksys has it's web admin server at the default 192.168.1.1.
The gateway address of IPCop Blue is 192.168.1.254.
The gateway address of IPCop Green is 10.22.44.254.
For clarification, by "gateway address" do you mean the IP Address of the
Blue Interface on IPcop?

Also, you SHOULD be able to ping the IP Address of the Blue Interface on
IPcop from any PC on green. You SHOULD NOT be able to ping the IP Address
of any of the computers on the Blue Interface from any PC on green.


----- Original Message -----
From: "Larry Alkoff" <***@mindspring.com>
To: "Carl E Meece III" <***@bellsouth.net>
Cc: <ipcop-***@lists.sourceforge.net>
Sent: Sunday, January 25, 2009 1:59 PM
Subject: Re: [IPCop-user] How to setup Linksys router?
Post by Larry Alkoff
Carl I have not had much luck setting up the Linksys
and would like to try your method. That is, I would like to seup my
Linksys and configuration the same as yours. My comments inline.
Post by Carl E Meece III
Post by Carl E Meece III
Post by Larry Alkoff
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL router
for wifi and have problems connecting.
On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.
At IPCop I have added a Blue access route to 192.168.1.1 but cannot
ping that address from Green I can ping the IPCop gateway at
192.168.1.254.
I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.
How can I get the Linksys router working?
Larry
------------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
I'm assuming you've tried more than one Cat5 cable. Bad cables do happen.
Yes I have tried several cables.
Post by Carl E Meece III
Post by Carl E Meece III
I also have a Linksys router on Blue. I have Blue connected to a LAN
port so all routing is handled by IPcop.
I have a Linksys wrt54gl connected from the Linksys lan port to the Blue
nic on IPCop. I have also tried a Linksys wrt54g (not the l=linux
version). The Linksys routers get dhcp from IPCop and do not themselves
serve dhcp.
I am able to surf to an occasional web site using a laptop connected to
the lan port of the Linksys but only one site - then I cannot connect any
more.
Post by Carl E Meece III
Post by Carl E Meece III
Check IPcop DHCP Server and
The IPCop dhcp server is on.
Post by Carl E Meece III
Post by Carl E Meece III
make sure the "IP Address/Netmask" for Blue Interface is the same as the
LAN IP Address/Netmask on the Linksys.
I'm not sure what to do here.
My Linksys has it's web admin server at the default 192.168.1.1.
The gateway address of IPCop Blue is 192.168.1.254.
The gateway address of IPCop Green is 10.22.44.254.
Should I be using Linksys > Setup > Advanced routing?
There are settings for Gateway and Router.
Destination lan ip 10.22.44.0
Subnet mask: 254.254.254.0
Default gateway 10.22.44.254
Interface lan and wireless
Post by Carl E Meece III
Post by Carl E Meece III
It should just work. If not, try a different router or access point.
If it still doesn't work, swap out the Blue NIC.
~ Carl
I also have Blue setup to use the same gateway and DNS server as green,
try that...
I think that is the present setting as shown above.
Post by Carl E Meece III
~ Carl
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.
Larry Alkoff
solanth
2009-01-26 09:05:22 UTC
Permalink
Post by Carl Meece
Post by Larry Alkoff
Post by Carl E Meece III
Post by Carl E Meece III
make sure the "IP Address/Netmask" for Blue Interface is the same as
the LAN IP Address/Netmask on the Linksys.
I'm not sure what to do here.
My Linksys has it's web admin server at the default 192.168.1.1.
The gateway address of IPCop Blue is 192.168.1.254.
The gateway address of IPCop Green is 10.22.44.254.
For clarification, by "gateway address" do you mean the IP Address of the
Blue Interface on IPcop?
Also, you SHOULD be able to ping the IP Address of the Blue Interface on
IPcop from any PC on green. You SHOULD NOT be able to ping the IP Address
of any of the computers on the Blue Interface from any PC on green.
not correct green can ping any blue or orange
(just checked my own network to confirm)
rgds Ian
Post by Carl Meece
----- Original Message -----
Sent: Sunday, January 25, 2009 1:59 PM
Subject: Re: [IPCop-user] How to setup Linksys router?
Post by Larry Alkoff
Carl I have not had much luck setting up the Linksys
and would like to try your method. That is, I would like to seup my
Linksys and configuration the same as yours. My comments inline.
Post by Carl E Meece III
Post by Carl E Meece III
Post by Larry Alkoff
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL
router for wifi and have problems connecting.
On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.
At IPCop I have added a Blue access route to 192.168.1.1 but cannot
ping that address from Green I can ping the IPCop gateway at
192.168.1.254.
I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.
How can I get the Linksys router working?
Larry
----------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
I'm assuming you've tried more than one Cat5 cable. Bad cables do happen.
Yes I have tried several cables.
Post by Carl E Meece III
Post by Carl E Meece III
I also have a Linksys router on Blue. I have Blue connected to a LAN
port so all routing is handled by IPcop.
I have a Linksys wrt54gl connected from the Linksys lan port to the Blue
nic on IPCop. I have also tried a Linksys wrt54g (not the l=linux
version). The Linksys routers get dhcp from IPCop and do not themselves
serve dhcp.
I am able to surf to an occasional web site using a laptop connected to
the lan port of the Linksys but only one site - then I cannot connect any
more.
Post by Carl E Meece III
Post by Carl E Meece III
Check IPcop DHCP Server and
The IPCop dhcp server is on.
Post by Carl E Meece III
Post by Carl E Meece III
make sure the "IP Address/Netmask" for Blue Interface is the same as
the LAN IP Address/Netmask on the Linksys.
I'm not sure what to do here.
My Linksys has it's web admin server at the default 192.168.1.1.
The gateway address of IPCop Blue is 192.168.1.254.
The gateway address of IPCop Green is 10.22.44.254.
Should I be using Linksys > Setup > Advanced routing?
There are settings for Gateway and Router.
Destination lan ip 10.22.44.0
Subnet mask: 254.254.254.0
Default gateway 10.22.44.254
Interface lan and wireless
Post by Carl E Meece III
Post by Carl E Meece III
It should just work. If not, try a different router or access point.
If it still doesn't work, swap out the Blue NIC.
~ Carl
I also have Blue setup to use the same gateway and DNS server as green,
try that...
I think that is the present setting as shown above.
Post by Carl E Meece III
~ Carl
I am starting my second week of frustration trying to get this to work
so would greatly appreciate any help.
Larry Alkoff
---------------------------------------------------------------------------
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
IPCop-user mailing list
https://lists.sourceforge.net/lists/listinfo/ipcop-user
Jeffrey S. Russell
2009-01-26 12:58:00 UTC
Permalink
Post by Larry Alkoff
Post by Carl E Meece III
make sure the "IP Address/Netmask" for Blue Interface is the same as the
LAN IP Address/Netmask on the Linksys.
I'm not sure what to do here.
My Linksys has it's web admin server at the default 192.168.1.1.
The gateway address of IPCop Blue is 192.168.1.254.
The gateway address of IPCop Green is 10.22.44.254.
For clarification, by "gateway address" do you mean the IP Address of
the
Blue Interface on IPcop?

Also, you SHOULD be able to ping the IP Address of the Blue Interface on

IPcop from any PC on green. You SHOULD NOT be able to ping the IP
Address
of any of the computers on the Blue Interface from any PC on green.

I think Carl meant that you SHOULD NOT be able to ping the IP address of
any of the computers on the green interface from any pc in the blue
network.

:)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (ProxSMTP 1.6)
AntiSpam: SpamAssassin 3.2.3
AntiVirus: ClamAV 0.93.3/8903 - Mon Jan 26 05:43:08 2009
by Markus Madlener @ http://www.copfilter.org
David Meed
2009-01-18 19:28:49 UTC
Permalink
Post by Larry Alkoff
At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green I can ping the IPCop gateway at 192.168.1.254.
We also have routers set up with ipcop blue interface to router lan
interface (not the WAN). We are using the GL routers flashed with
ddwrt v23.??

I may be all wet and would appreciate others who really know what is
going on chiming in, but this is my guess:

I think that the router has no access back to green unless you
specifically allow it - you have to enter the router address in the
blue access page - either by IP or MAC.

In other words the ping from green is going to blue, then out the blue
wire to the router. The reply from the router is returning to the
blue interface and being blocked from going further by ipcop not
allowing access from blue because the router is not on the blue access
page. (I presume that the router does respond to pings from another
computer on blue.) One other important thing is to disable the
router's internal dhcp so it doesn't conflict with IPCop's dhcp.



By the way - we are using our routers as access points only and didn't
bother to put the routers in blue access. Our blue is 172.17.x.x/
255.255.0.0 and the default linksys firmware that we had wouldn't
allow that subnet (only 255.255.255.0).

So the router is still at 192.168.1.1 (default) but the lan ports are
broadcasting all the 172.17.x.x traffic transparently over the
wireless. If we ever have to administrate the router we just manually
assign an 192.168.1.2 ip to a machine on blue.




-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Larry Alkoff
2009-01-18 20:35:47 UTC
Permalink
Post by David Meed
Post by Larry Alkoff
At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green I can ping the IPCop gateway at 192.168.1.254.
We also have routers set up with ipcop blue interface to router lan
interface (not the WAN). We are using the GL routers flashed with
ddwrt v23.??
I may be all wet and would appreciate others who really know what is
I think that the router has no access back to green unless you
specifically allow it - you have to enter the router address in the
blue access page - either by IP or MAC.
In other words the ping from green is going to blue, then out the blue
wire to the router. The reply from the router is returning to the
blue interface and being blocked from going further by ipcop not
allowing access from blue because the router is not on the blue access
page. (I presume that the router does respond to pings from another
computer on blue.) One other important thing is to disable the
router's internal dhcp so it doesn't conflict with IPCop's dhcp.
I appreciate your help but I _already_ have a Blue access page line
granting access from the entire Blue network 192.168.1.254 to Green
and a separate access from the Linksys at 192.168.1.1 to Green.
IPCop doesn't seem to like the duplicate addresses.

I can still ping .254 but not Linksys at 1.1.

So my question is what else do I have to do to complete the ping?
Post by David Meed
By the way - we are using our routers as access points only and didn't
bother to put the routers in blue access. Our blue is 172.17.x.x/
255.255.0.0 and the default linksys firmware that we had wouldn't
allow that subnet (only 255.255.255.0).
So the router is still at 192.168.1.1 (default) but the lan ports are
broadcasting all the 172.17.x.x traffic transparently over the
wireless. If we ever have to administrate the router we just manually
assign an 192.168.1.2 ip to a machine on blue.
I don't really understand what you mean by this David.
If the router is at the default 192.168.1.1 then how are you able to
broadcast and see wifi traffic on a different subnet?
Do you mean the Linksys nats it to the 172.17 network?

Larry
David Meed
2009-01-18 21:29:21 UTC
Permalink
Post by Larry Alkoff
Post by David Meed
So the router is still at 192.168.1.1 (default) but the lan ports are
broadcasting all the 172.17.x.x traffic transparently over the
wireless. If we ever have to administrate the router we just manually
assign an 192.168.1.2 ip to a machine on blue.
I don't really understand what you mean by this David.
If the router is at the default 192.168.1.1 then how are you able to
broadcast and see wifi traffic on a different subnet?
Do you mean the Linksys nats it to the 172.17 network?
No - the LAN ports on the linksys are just a switch. It doesn't care
what network the traffic is on - it routes all traffic from port to
port on the switch (and the wireless is just another port on that
switch.) The only time the router cares what network traffic is on is
if I am actually talking to the http server on the router, or when it
is routing traffic from the WAN port to the internal LAN/switch.


-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Larry Alkoff
2009-01-18 21:58:31 UTC
Permalink
Post by David Meed
Post by Larry Alkoff
Post by David Meed
So the router is still at 192.168.1.1 (default) but the lan ports are
broadcasting all the 172.17.x.x traffic transparently over the
wireless. If we ever have to administrate the router we just manually
assign an 192.168.1.2 ip to a machine on blue.
I don't really understand what you mean by this David.
If the router is at the default 192.168.1.1 then how are you able to
broadcast and see wifi traffic on a different subnet?
Do you mean the Linksys nats it to the 172.17 network?
No - the LAN ports on the linksys are just a switch. It doesn't care
what network the traffic is on - it routes all traffic from port to
port on the switch (and the wireless is just another port on that
switch.) The only time the router cares what network traffic is on is
if I am actually talking to the http server on the router, or when it
is routing traffic from the WAN port to the internal LAN/switch.
Your Green network is 192.168.1/24
and your wifi stuff is all on 172.17.x.x ??

Larry
Larry Alkoff
2009-01-18 20:12:51 UTC
Permalink
Post by Larry Alkoff
I have an IPCop version 1.4.15 Red-Green box that works perfectly.
Recently I added a 3rd nic for Blue to connect a Linksys WRT54GL router
for wifi and have problems connecting.
On IPCop,
the Green network is on 10.x.x.x with gateway at 10.x.x.254,
Blue is at 192.168.1.x with gateway at 192.168.1.254
and the Linksys router on Blue was reset to the default of 192.168.1.1.
At IPCop I have added a Blue access route to 192.168.1.1 but cannot ping
that address from Green but I can ping the IPCop Blue gateway at 192.168.1.254.
I've tried plugging in the cat5 cable from IPCop Blue to both the WAN
and LAN ports on the Linksys.
How can I get the Linksys router working?
Larry
This is turning out to be harder than I thought even though my knowledge
of tcp/ip is fairly good but not expert.

My understanding of IPCop is that Green can always contact Blue but Blue
cannot contact Green unless pinholes are established.

Would that affect pings?

I would like to know what has to be done at the IPCop machine to allow
access from Green to Blue and Blue to Green. Once that works I can
start stripping the access until the wifi part is tightened up.

I've been over the Setup and Admin manuals but am not sure what is required.

I'd really appreciate some help on this.

Larry
David Meed
2009-01-18 20:33:22 UTC
Permalink
Post by Larry Alkoff
I would like to know what has to be done at the IPCop machine to allow
access from Green to Blue and Blue to Green. Once that works I can
start stripping the access until the wifi part is tightened up.
Perhaps it might help if you explain a little more about what you want
to do with the linksys router on Blue?

In our system, blue wireless users only have access to the internet, -
they don't access green unless on a machine by machine basis - that is
what the pinholes are for. As I understand it, blue is not intended
to access green on a wholesale basis.

On my home system, for wholesale access to green from wireless clients
I just installed the wireless router on green using WPA secured
wireless network. Not totally secure, but a lot simpler. If there is
a better way to do it I'm all ears. I'd be especially interested in
an analysis of the relative security of wpa wireless on green vs. wpa
wireless on blue through IPCop to green with pinholes for the machines
on blue. Does it make that much difference?


-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Larry Alkoff
2009-01-18 20:40:19 UTC
Permalink
Post by David Meed
Post by Larry Alkoff
I would like to know what has to be done at the IPCop machine to allow
access from Green to Blue and Blue to Green. Once that works I can
start stripping the access until the wifi part is tightened up.
Perhaps it might help if you explain a little more about what you want
to do with the linksys router on Blue?
In our system, blue wireless users only have access to the internet, -
they don't access green unless on a machine by machine basis - that is
what the pinholes are for. As I understand it, blue is not intended
to access green on a wholesale basis.
This is also exactly how I'd like to end up.
No access from Blue to Green unless specifically permitted.
But I would like to have Green to Blue access and I _thought_ that's
what IPCop allowed by default. Since I have added a route on the Green
machine to 192.168.1.254 that should be allowing me at least ping
Linksys from Blue - yes?

When you say "in our system" is that the same as your home system
or is "in our system" something like your office?
Post by David Meed
On my home system, for wholesale access to green from wireless clients
I just installed the wireless router on green using WPA secured
wireless network. Not totally secure, but a lot simpler. If there is
a better way to do it I'm all ears. I'd be especially interested in
an analysis of the relative security of wpa wireless on green vs. wpa
wireless on blue through IPCop to green with pinholes for the machines
on blue. Does it make that much difference?
David Meed
2009-01-18 21:24:31 UTC
Permalink
Post by Larry Alkoff
I'd really appreciate some help on this.
Some very basic tests that I would try. The responses to these might
help others who could pinpoint your problem. You've probably already
tried this...

1) Set up the router all by itself - nothing connected.
2) Connect a test PC to the router w/cat 5 on one of the LAN ports.
You may have to manually assign an ip in the router subnet. If you
don't have to manually assign the IP, you have DHCP running on the
router and that needs to be turned off!
3) can you ping router and get a reply?

This proves the router replies to pings and the cat 5 cable is
working.

4) Leave the PC set up and connect router with another cat 5 to IPCop
box from another of the LAN ports. (We won't use the WAN port of the
router at all.) at this point the router is just an expensive switch.
5) can you still ping the router? - no reason this shouldn't still
work.
6) Can you ping the IPCop box? This proves Blue NIC is working and IP
Cop is listening on blue. You may have to set up the IP addresses
and/or the mac addresses of the router and/or the test PC on the IPCop
box. - Actually you don't need the router in there for this to work -
the router should be acting as a transparent switch for the traffic
from the PC to the IPCop box, but you will need the router in there
for later.
7) can you ping the internet/browse and surf from the PC (still
connected to the router to the IPCop box on blue) - This proves that
IPCop is routing blue interface to red.
8) Can you ping Green gateway from the test PC?

9) Now plug test pc into green network (switch back to DHCP instead of
manual IP setting) and see if you can ping the router from green.

Here is where my knowledge gets a little sketchy. I think that if
green opens a connection to blue (ping), ipcop should allow the
response back to green without a pinhole needed, as long as the MAC
address of the router is in the blue access window on IPCop. It would
be like pinging someone on the internet from green - the reply comes
back, but they can't talk to green unless green initiates the
conversation.

Which brings up a question:
Does IPCop blue access require the MAC address for blue connections or
will it work for just an IP address no matter what the MAC is? I
haven't checked or studied this--we just used mac addresses for all
our blue users.

I'm interested in how this works out myself, because I have a number
of blue access points that I would love to be able to reach from
green. Right now I just reach up into the network closet and plug my
pc into blue when I have to talk to them. But it seems that the ones
where I have the MAC addresses in the blue access page I can reach
from green. - never spent the time to work it all out.


-----
David Meed <***@meed.ca>
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Larry Alkoff
2009-01-18 21:52:15 UTC
Permalink
Post by David Meed
Post by Larry Alkoff
I'd really appreciate some help on this.
Some very basic tests that I would try. The responses to these might
help others who could pinpoint your problem. You've probably already
tried this...
1) Set up the router all by itself - nothing connected.
2) Connect a test PC to the router w/cat 5 on one of the LAN ports.
You may have to manually assign an ip in the router subnet. If you
don't have to manually assign the IP, you have DHCP running on the
router and that needs to be turned off!
3) can you ping router and get a reply?
This proves the router replies to pings and the cat 5 cable is
working.
Yes, from another computer on the Blue network I can ping the Linksys
router and get a reply.
Post by David Meed
4) Leave the PC set up and connect router with another cat 5 to IPCop
box from another of the LAN ports. (We won't use the WAN port of the
router at all.) at this point the router is just an expensive switch.
5) can you still ping the router? - no reason this shouldn't still
work.
Yes I can ping still ping the router.
Post by David Meed
6) Can you ping the IPCop box? This proves Blue NIC is working and IP
Cop is listening on blue. You may have to set up the IP addresses
and/or the mac addresses of the router and/or the test PC on the IPCop
box. - Actually you don't need the router in there for this to work -
the router should be acting as a transparent switch for the traffic
from the PC to the IPCop box, but you will need the router in there
for later.
Yes I can ping the IPCop box.
Post by David Meed
7) can you ping the internet/browse and surf from the PC (still
connected to the router to the IPCop box on blue) - This proves that
IPCop is routing blue interface to red.
No I cannot ping or surf from the PC.
Post by David Meed
8) Can you ping Green gateway from the test PC?
No I cannot ping the Green gateway from the Blue pc.
Post by David Meed
9) Now plug test pc into green network (switch back to DHCP instead of
manual IP setting) and see if you can ping the router from green.
I didn't mess with the settings on the test Blue pc but have other
computers (most linux or windows) and all can ping IPCop.
Post by David Meed
Here is where my knowledge gets a little sketchy. I think that if
green opens a connection to blue (ping), ipcop should allow the
response back to green without a pinhole needed, as long as the MAC
address of the router is in the blue access window on IPCop. It would
be like pinging someone on the internet from green - the reply comes
back, but they can't talk to green unless green initiates the
conversation.
I only had the fixed IP address of Linksys in the Blue access window of
IPCop but I added the MAC address. It still cannot be pinged from the
Green network.
Post by David Meed
Does IPCop blue access require the MAC address for blue connections or
will it work for just an IP address no matter what the MAC is? I
haven't checked or studied this--we just used mac addresses for all
our blue users.
The Admin manual says that Green always has full access to the Blue network.
Post by David Meed
I'm interested in how this works out myself, because I have a number
of blue access points that I would love to be able to reach from
green. Right now I just reach up into the network closet and plug my
pc into blue when I have to talk to them. But it seems that the ones
where I have the MAC addresses in the blue access page I can reach
from green. - never spent the time to work it all out.
-----
http://www3.nbnet.nb.ca/dmeed (Sony LANC, DMX-512, Panasonic Control M)
www.nbbi.ca
Andrew Borland
2009-01-19 22:20:08 UTC
Permalink
You may already have checked this, but have you told the Linksys Router
to use 192.168.1.254 as its Gateway? Because, if not, when you ping it
from green it has no way of knowing how to get back.

My own Linksys wouldn't let me configure a Gateway unless I first
configured addresses, etc. on its WAN port, even though that port was
unconnected. The cable to IPCop went into one of the LAN ports.

As I recall, I did not need to put anything in the Blue access page in
respect of the router. Presumably because the router itself never
initiated connection.

PS: This isn't something daft like using, or not using, a crossover
cable between the Linksys and the IPCop?

Regards, Andrew Borland (UK)
Larry Alkoff
2009-01-20 00:55:26 UTC
Permalink
Post by Andrew Borland
You may already have checked this, but have you told the Linksys Router
to use 192.168.1.254 as its Gateway? Because, if not, when you ping it
from green it has no way of knowing how to get back.
My own Linksys wouldn't let me configure a Gateway unless I first
configured addresses, etc. on its WAN port, even though that port was
unconnected. The cable to IPCop went into one of the LAN ports.
As I recall, I did not need to put anything in the Blue access page in
respect of the router. Presumably because the router itself never
initiated connection.
PS: This isn't something daft like using, or not using, a crossover
cable between the Linksys and the IPCop?
Regards, Andrew Borland (UK)
Hello Andrew and thanks for jumping in to help.

I don't see any other place in the Linksys web page to put in the IPCop
address. Where would it go?

The only place that even called for a gateway address was the tab Setup
Post by Andrew Borland
Basic Setup > Internet Connection Type when set for static IP but I
could not get the static choice to accept my settings.

So I have set it for dhcp.

If that is the place it goes, lets discuss what settings I need to put in.

Larry
Andrew Borland
2009-01-20 23:07:48 UTC
Permalink
OK, I'm going from fairly distant memory here. For the record, I'm
using a slightly different version of router, namely a WRK54G.

All my IPCop interior I/Fs are 192.168.n.8 (don't ask about the 8 -
it's historical). Specifically, Blue is 192.168.1.8

I configured the WAN (Internet) interface of the Linksys to a static
address of 10.0.0.1 (255.255.255.0) simply to get it well out of harms
way. Once that was done, it was possible to set the Default Gateway
address to 192.168.1.8 [probably not a combination the manufacturer
ever anticipated but it works for me].

On the LAN side, the Linksys has a network address of 192.168.1.1
(255.255.255.0) which is the address I put into Firefox when I want to
talk to it. I can also ping this from green.

I also disabled the Linksys Local DHCP server as that job belongs to
IPCop. IPCop is set to issue addresses above 192.168.1.190

So far as I can recall, that was all there was to it. It took me a
while to discover that you had to have a static WAN IP in order to be
able to set the Default Gateway but once I'd solved that it all just
seemed to work.

As I noted before. I do not have the Linksys MAC address in the list
of "Devices on Blue" nor do I have any fancy "routes" set up (I
wouldn't know how). I do, however, list the MACs of the wireless
clients. Cable to IPCop goes into a LAN port on the Linksys.

And that, m'lud, concludes my evidence.

Regards, Andrew Borland (UK)
Larry Alkoff
2009-01-20 01:07:29 UTC
Permalink
Post by Andrew Borland
You may already have checked this, but have you told the Linksys Router
to use 192.168.1.254 as its Gateway? Because, if not, when you ping it
from green it has no way of knowing how to get back.
My own Linksys wouldn't let me configure a Gateway unless I first
configured addresses, etc. on its WAN port, even though that port was
unconnected. The cable to IPCop went into one of the LAN ports.
As I recall, I did not need to put anything in the Blue access page in
respect of the router. Presumably because the router itself never
initiated connection.
PS: This isn't something daft like using, or not using, a crossover
cable between the Linksys and the IPCop?
Regards, Andrew Borland (UK)
Update.

I just saw in Firewall > Blue Access that I may have put in the wrong
MAC for the link to 192.168.1.254 in IPCop.

So I copied the eth2 MAC address from Status > Network Status.
Rebooted Linksys but still not pinging from Green or from the Blue
laptop to either the Internet or a fixed IP on Green.

Something simple is missing.

Larry
David Sims
2009-01-20 02:13:31 UTC
Permalink
Post by Larry Alkoff
Post by Andrew Borland
You may already have checked this, but have you told the Linksys Router
to use 192.168.1.254 as its Gateway? Because, if not, when you ping it
from green it has no way of knowing how to get back.
My own Linksys wouldn't let me configure a Gateway unless I first
configured addresses, etc. on its WAN port, even though that port was
unconnected. The cable to IPCop went into one of the LAN ports.
As I recall, I did not need to put anything in the Blue access page in
respect of the router. Presumably because the router itself never
initiated connection.
PS: This isn't something daft like using, or not using, a crossover
cable between the Linksys and the IPCop?
Regards, Andrew Borland (UK)
Update.
I just saw in Firewall > Blue Access that I may have put in the wrong
MAC for the link to 192.168.1.254 in IPCop.
So I copied the eth2 MAC address from Status > Network Status.
Rebooted Linksys but still not pinging from Green or from the Blue
laptop to either the Internet or a fixed IP on Green.
Something simple is missing.
Larry
Hi,

Using the same cable that is connecting the Linksys LAN port to the
IPCop, unplug the IPCop end and plug it into a laptop... Set the laptop
to a static address on the same netmask as the Linksys LAN...
Larry Alkoff
2009-01-20 02:46:08 UTC
Permalink
Post by David Sims
Post by Larry Alkoff
Post by Andrew Borland
You may already have checked this, but have you told the Linksys Router
to use 192.168.1.254 as its Gateway? Because, if not, when you ping it
from green it has no way of knowing how to get back.
My own Linksys wouldn't let me configure a Gateway unless I first
configured addresses, etc. on its WAN port, even though that port was
unconnected. The cable to IPCop went into one of the LAN ports.
As I recall, I did not need to put anything in the Blue access page in
respect of the router. Presumably because the router itself never
initiated connection.
PS: This isn't something daft like using, or not using, a crossover
cable between the Linksys and the IPCop?
Regards, Andrew Borland (UK)
Update.
I just saw in Firewall > Blue Access that I may have put in the wrong
MAC for the link to 192.168.1.254 in IPCop.
So I copied the eth2 MAC address from Status > Network Status.
Rebooted Linksys but still not pinging from Green or from the Blue
laptop to either the Internet or a fixed IP on Green.
Something simple is missing.
Larry
Hi,
Using the same cable that is connecting the Linksys LAN port to the
IPCop, unplug the IPCop end and plug it into a laptop... Set the laptop
to a static address on the same netmask as the Linksys LAN...
Eric Oberlander
2009-01-20 19:45:34 UTC
Permalink
Post by David Meed
Post by David Meed
6) Can you ping the IPCop box? This proves Blue NIC is working
and IP
Post by David Meed
Cop is listening on blue. You may have to set up the IP addresses
and/or the mac addresses of the router and/or the test PC on the
IPCop
Post by David Meed
box. - Actually you don't need the router in there for this to
work -
Post by David Meed
the router should be acting as a transparent switch for the traffic
from the PC to the IPCop box, but you will need the router in there
for later.
Yes I can ping the IPCop box.
Post by David Meed
7) can you ping the internet/browse and surf from the PC (still
connected to the router to the IPCop box on blue) - This proves that
IPCop is routing blue interface to red.
No I cannot ping or surf from the PC.
Did you add the PC on Blue as a Device on IPCop's Blue Access page?
The IP Address will do. Make sure to check the enabled box.

Eric
Larry Alkoff
2009-01-20 22:52:23 UTC
Permalink
Post by Eric Oberlander
Post by David Meed
Post by David Meed
6) Can you ping the IPCop box? This proves Blue NIC is working
and IP
Post by David Meed
Cop is listening on blue. You may have to set up the IP addresses
and/or the mac addresses of the router and/or the test PC on the
IPCop
Post by David Meed
box. - Actually you don't need the router in there for this to
work -
Post by David Meed
the router should be acting as a transparent switch for the traffic
from the PC to the IPCop box, but you will need the router in there
for later.
Yes I can ping the IPCop box.
Post by David Meed
7) can you ping the internet/browse and surf from the PC (still
connected to the router to the IPCop box on blue) - This proves that
IPCop is routing blue interface to red.
No I cannot ping or surf from the PC.
Did you add the PC on Blue as a Device on IPCop's Blue Access page?
The IP Address will do. Make sure to check the enabled box.
Eric
Yes I put both MAC addresses on the Dell laptop (received from ifconfig
-a) in the Blue Access page.

Larry
Eric Oberlander
2009-01-21 08:53:33 UTC
Permalink
Post by Larry Alkoff
Post by Eric Oberlander
Post by Larry Alkoff
Yes I can ping the IPCop box.
Post by David Meed
7) can you ping the internet/browse and surf from the PC (still
connected to the router to the IPCop box on blue) - This proves that
IPCop is routing blue interface to red.
No I cannot ping or surf from the PC.
Did you add the PC on Blue as a Device on IPCop's Blue Access page?
The IP Address will do. Make sure to check the enabled box.
Eric
Yes I put both MAC addresses on the Dell laptop (received from
ifconfig -a) in the Blue Access page.
Is the Dell Laptop getting DNS, IP Address, Default Gateway etc. from
IPCop via DHCP on Blue, or are you inputting them manually?

If manually, what values are you you using? Primary DNS should be
same IP address as Blue Interface/Gateway on IPCop.

Eric
Larry Alkoff
2009-01-21 21:19:28 UTC
Permalink
Post by Eric Oberlander
Post by Larry Alkoff
Post by Eric Oberlander
Post by Larry Alkoff
Yes I can ping the IPCop box.
Post by David Meed
7) can you ping the internet/browse and surf from the PC (still
connected to the router to the IPCop box on blue) - This proves that
IPCop is routing blue interface to red.
No I cannot ping or surf from the PC.
Did you add the PC on Blue as a Device on IPCop's Blue Access page?
The IP Address will do. Make sure to check the enabled box.
Eric
Yes I put both MAC addresses on the Dell laptop (received from
ifconfig -a) in the Blue Access page.
Is the Dell Laptop getting DNS, IP Address, Default Gateway etc. from
IPCop via DHCP on Blue, or are you inputting them manually?
If manually, what values are you you using? Primary DNS should be
same IP address as Blue Interface/Gateway on IPCop.
Eric
The laptop has two interfaces.

eth0 is wired, and the values for dns, ip address, gateway are put in
manually.

eth1 is wifi and gets it's values dhcp from IPCop. I can see the lease
on the ipcop Blue Access page. dhcp is turned off on the Linksys.

The values for dns and gateway are the same on both interfaces. Of
course, the ip address is different.

Larry
Larry Alkoff
2009-01-24 04:41:43 UTC
Permalink
Hello David and Brandon
I report sucess!
I have started afresh with the Linux version of the router Linksys
wrt54gl with a 60 second refresh first.
My connection method is
Blue IPCop -> switch -> Linksys and Dell laptop
but Dell laptop is not connected by wire.
The Linksys pulled a dhcp from IPCop of 92.168.1.150.
Firefox loaded a web page! Hooray!
Apparently the old Linksys wrt54g (not L) has some problem.
Guess where it's going ;-)
Larry
Larry Alkoff
2009-01-24 05:09:34 UTC
Permalink
Hello David and Brandon
I report sucess!
I have started afresh with the Linux version of the router Linksys
wrt54gl with a 60 second refresh first.
My connection method is
Blue IPCop -> switch -> Linksys and Dell laptop
but Dell laptop is not connected by wire.
The Linksys pulled a dhcp from IPCop of 92.168.1.150.
Firefox loaded a web page! Hooray!
Apparently the old Linksys wrt54g (not L) has some problem.
Guess where it's going ;-)
Larry
Well I was a little premature in reporting success.

It seems that, using wifi only, I was able to pull in a single web page
but then could not pull in another. Tried 5 pages I use all the time.

The router has pulled a dhcp from IPCop of 192.168.1.150 which is the
start of the dhcp range.

However, whenever I try to surf to a page, Firefox reports 'done' but no
page appears.

I'm done in tonight. Will play more tomorrow.

Larry
Continue reading on narkive:
Loading...