December 9, 2010 at 1:38 am #42775
| | |
| | | |
PC1 PC2 PC3 Switch
| | |
PC4 PC5 PC6
Server1 Windows: DNS, DHCP (192.168.2.16)
Server2 Windows: FTP (192.168.2.18)
Cisco Router: Gateway (192.168.2.51)
PC 1, 2, 3: Client OS Windows (192.168.2.0/24)
Zeroshell: ETH00 (192.168.2.10), ETH01 (10.10.10.10)
PC 4, 5, 6: Client Mac OSX (10.10.10.0/24)
All 192.168.2.0/24 have gateway 192.168.2.51 and I plan to connect all 10.10.10.0/24 to 192.168.2.0/24 via Zeroshell.
can ping each other, can access Server1 and Server2 as FTP Server from 10.10.10.0/24
I’m new in zeroshell and need help and advise how to set and configure zeroshell?
Thx B4December 9, 2010 at 12:26 pm #51423
if you cannot manage the cisco router , ( add a static route ) , there are two “dirty” ways that you can take :
1st : add on each pc’s of the 192.168.2.0/24 a static route , something like
route add -p 10.10.10.0 mask 255.255.255.0 192.168.2.10 metric 3
( the -p argument makes the route permanent , otherwise you will lose the route at next reboot )
2nd : change , on each pc’s on the 192.168.2.0/24 the default gateway with the ip address of the ZS eth00 interface ( 192.168.2.10 ) , you can do this by upgrading the dhcp setting on your dhcp server .( but be aware , if your ZS machine fails , all your network will be without a default route for the internet )
in both case , on ZS machine create a static default route with next hope address the ip of the cisco router (192.168.2.51) , and disable natDecember 9, 2010 at 3:06 pm #51424
I have a similar setup to yours, except for the cisco router. in my setup i have 1 main router, ZS, and 2 network segments each with a ZS. you should not have to make any changes to your main cisco router, simply put a static route on the ZS to your main network:
DEFAULT GATEWAY|0.0.0.0|Net|0|192.168.0.1| |Up
that is all i needed to do for my setup.
obviously change the gateway I use for yoursDecember 9, 2010 at 7:19 pm #51425
and, as rightly JC writes …
if you want access from the 10.10.10.0/24 network to the 192.168.2.0/24 network and not vice versa, it’s enough enable nat on
ZS’s ETH00 (192.168.2.10) and make a default route with next-hope address 192.168.2.51February 12, 2011 at 7:51 am #51426
Thx all of you.
All your advise working, right know I will decide which one will be use.
Once again Thank You 😆
You must be logged in to reply to this topic.