Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
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 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |