Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

i have VPN setup which is like this:

########### internet  ############## internet  ############   LAN   ############
# macbook # --------> # VPN server #----------># PC A     # -------># PC B     #
#10.8.0.6 #           # 10.8.0.1   #           # 10.8.0.7 #         # 192.168..#
###########           ##############           ############         ############

and now i want to access the PC B in the local LAN of PC A ( A is in VPN net ) with my macbook, I can access PC A with my macbook, so VPN works, i just need some way to route the traffic from the macbook over PC A ( i guess ) to reach PC B in the LAN of PC A, i cant add PC B to the vpn net because i dont have (physical) access to it. ( i hope this is not too confusing ) how can i do this? VPN Server and PC A are running Debian,

any advice is greatly appreciated :), and sorry for my bad english

share|improve this question

closed as too localized by Michael Mrozek Jul 21 '12 at 16:35

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

    
Please don't cross-post. –  Mat Jul 21 '12 at 14:08
    
Still open on SU; closing here –  Michael Mrozek Jul 21 '12 at 16:35
add comment

1 Answer 1

If it were Linux, the command you'd use would be:

ip route add 192.168.0.0/16 via 10.8.0.7

This requires that ip_forwarding is enabled on PC A (assuming it's a Linux box, I'm sure there's a similar concept in other OSes). I'm not sure if the "ip" command is available on Mac.

share|improve this answer
1  
It would also require that the devices in 192.168 know how to reach 10.8.0.0/24, e.g they should have a route via 10.8.0.7 otherwise nat is required –  Ulrich Dangel Jul 21 '12 at 15:38
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.