On Tue, Aug 6, 2013 at 1:18 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote:
Ok i been fooling around with this, and suspect I am missing something dumb... I have the following SOHO network configuration -
Internet | Router A 169.254.1.1 | |-----169.254.1.200 Router B 192.168.20.1 --------- 192.168.20.100 Machine A | 169.254.1.100 (eth0) OpenSuSE Gateway Machine with SuSEFirewall 192.168.10.1 (eth1) | | 192.168.10.20 Machine B
So how do I set up the SuSEFirewall and the network routing tables on the OpenSuSE Gateway to allow Machine B to see Machine A? I did set up a route in the Routing Table in YaST2 for the network interfaces as follows -
Destination 192.168.20.0 Genmask 255.255.255.0 Gateway 169.254.1.200 Device eth0
The gateway address for Machine A is set to 192.168.20.1 The gateway address for Machine B is set to 192.168.10.1 The gateway address for the OpenSuSE Gateway Machine is set to 169.254.1.1
So far I have been unable to get Machine B to even ping Machine A. Is the SuSEFirewall interfering and if so what do I have to do to make it behave? I tried a few things with it also, but so far no joy.
Gotta be something dumb I am missing, appreciate and thanks in advance for a bit of help..
Marc...
You need to rephrase your question: You have 2 separate default non-routable networks setup with a suse gateway router between them and you're asking how to have the suse gateway router route the default non-routable traffic between them. I don't know how to override the default lack of routing of 169.254.x.x and 192.168.x.x addresses in the suse gateway router, but I'd be shocked if you can't be done easily. Hopefully someone else knows how to override the default behavior and route those IPs. fyi: This is not a "dumb" question. You have setup a more complex network, but companies do similar things all the time. If a company is lucky enough to have their own class A, class B, class C's, Then they can do it all with routable IPs. The reality today is most companies don't have that luxury, so the do use multiple non-routable networks so they can do things such as have a 10.x.x.x for the main network and a 192.168.x.x for a wireless guest network, etc. To accommodate that routers have override options to allow those IP ranges to be routed. I just have never been the one responsible for setting that up, so I don't know any details of how to do the override. Greg Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org