Thanks for all the suggestions from the group. There were several requests for a more clear description of the setup. Here it is: Verizon FIOS DSL <=> Actiontek router (192.168.1.1) <=> LinkSys router (192.168.1.20 <=> 192.168.2.1) Linux box (with samba printer): 192.168.1.14 windows box (needing to print): 192.168.2.200 The fix: 1. Enable printing from 192.168.2.x in the samba setup. (I'm not sure that helped, because the LinkSys router was set up as a gateway, thus the print request showed up from 192.168.1.20.) 2. Set up a route to the 192.168.2.x network on my linux box. 3. Lots of mucking around with the LinkSys. I also opened it up to all outside access. I also set "dynamic routing". 4. Whacked at the windows box quite a bit. It finally (magically?) started working. Unresolved questions: 1. What did I do to make it work? 2. Why do I need to keep the LinkSys set with the "gateway" rather than the "router" setting? If I set "router", then I can access between the 2 networks nicely, but the 192.168.2.x will not route to the internet. Maybe I needed a static route? It would be nice to understand what was the key. I'd also like to understand how to set the LinkSys as a router rather than a gateway, but at least it works and my wife is no longer reminding me how much linux messes things up. :-) Thanks, Bill
Is there any particular reason you are using a 2 router setup? (other than the provided wireless router has poor range?) You could just plug one of the switch ports on the linksys into a switch port on the actiontek and use the linksys as a wap. 2. In gateway setting, all traffic passing from your linksys to the actiontek router is being nat'd through 192.168.1.20. In router mode, all traffic is passing through with its native 192.168.2.0/24 addresses. I think you will have to set up a static route on the actiontek to get the 192.168.2.0/24 to be nat'd out. What does the routing table on the actiontek look like right now? Justin On 8/22/06, Bill Mills-Curran <bill@mills-curran.net> wrote:
Thanks for all the suggestions from the group.
There were several requests for a more clear description of the setup. Here it is:
Verizon FIOS DSL <=> Actiontek router (192.168.1.1) <=> LinkSys router (192.168.1.20 <=> 192.168.2.1)
Linux box (with samba printer): 192.168.1.14
windows box (needing to print): 192.168.2.200
The fix: 1. Enable printing from 192.168.2.x in the samba setup. (I'm not sure that helped, because the LinkSys router was set up as a gateway, thus the print request showed up from 192.168.1.20.)
2. Set up a route to the 192.168.2.x network on my linux box.
3. Lots of mucking around with the LinkSys. I also opened it up to all outside access. I also set "dynamic routing".
4. Whacked at the windows box quite a bit. It finally (magically?) started working.
Unresolved questions:
1. What did I do to make it work?
2. Why do I need to keep the LinkSys set with the "gateway" rather than the "router" setting? If I set "router", then I can access between the 2 networks nicely, but the 192.168.2.x will not route to the internet. Maybe I needed a static route?
It would be nice to understand what was the key. I'd also like to understand how to set the LinkSys as a router rather than a gateway, but at least it works and my wife is no longer reminding me how much linux messes things up. :-)
Thanks, Bill _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
participants (2)
-
Bill Mills-Curran -
Justin Odom