- This topic has 0 replies, 1 voice, and was last updated 20 years ago by
.
-
Posts
-
Hi All,
I’ve tried to find the answer – no luck whatsoever.
I can’t imagine I’m the only one having this type of thing i want to achieve.
Situation
Two subnets, 192.168.116.x and 192.168.33.x. Gateways on x.1
Between the two subnets sits a VPN router. (192.168.116.21 WAN and 192.168.33.1 LAN)
Parallel with this VPN router is an OSX 10.4.8 server. One interface on x.x.116.5 and the other on x.x.33.5.
What I want to create is fileservices etc. on both subnets. Without OS X server interfering with the VPN-router and all other traffic going through it. So, OS X should act as if it were 2 servers on the different subnets. Both – preferrably – with their own set of firewall-rules.
What i _don’t_ want to do is take the VPN-router out of service. So, having OS X taking over the VPN-connection is not really an option. Trying this “*may*” create a new set of challenges I’m not really waiting for.
File services etc. need to be available for people coming in from the Internet and people coming in from the LAN (33.x). Coming in from the Internet and passing through the VPN router for some services appeared to be a challenge. For f.e. VoIP it proved to be a neckbreaking experience. So I don’t want to try that again. No worky.
Leaving the fileservices at 116.5 for the users at 33.x proved to be a bandwidth-challenge for the VPN-router. Not a lucky choice as well.
As of this moment, System Preferences tells me the 116.5 I/F is my connection to the Internet.
33.5 I/F is active. That’s all.
ping -S 192.168.33.5 192.168.33.1 answers with a “no route to host”
Using sysctl -w net.inet.ip.forwarding=0 disables the forwarding. So potential routing loops are killed.
ping -S 192.168.33.5 192.168.33.1 still answers with a “no route to host”.
I am puzzled as to why the 33.5 I/F won’t start. Trying from workstations on the 33.x LAN, only 116.5 is accessible. 33.5 gives a “looking up” message and times out.
It looks like the OS X server does a back-off somehow. For now I have no clue how I can tell the machine to just start serving all there is.
I checked, double-checked, triple-checked the settings. From just any client at 192.168.33.x the only connection that works is to 192.168.116.5 🙁
Now the big Q is: is there a way to get this to work? Or is it a dead-end street?
Any help/suggestion/comment is highly appreciated!/Paul
- You must be logged in to reply to this topic.