Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Appesteijn on April 12, 2005, 09:42:18 PM
-
Hi,
I've just installed a 6.5RC1 server with 3 NIC's. 1 external and 2 internal. The two internal ones have 100.0 and 110.0 as their ip-ranges. But when I restart dhcpd it complains that the dhcp information for eth2 (or 110.0) isn't available. Ofcourse this is correct so I edited dhcpd.conf and added 192.168.110.10-15 as a range and restarted dhcpd. But the it complains that eth1 (the external NIC) hasn't got any config available. That is also correct but I don't want to give ip-adresses to the internet :)
So has anybody any idea's about how I should fix this?
I want 1 internal NIC for my clients en 1 internal NIC for my other servers.
-
SME is not designed for this. I would suggest looking at IPCop.
-
IPCop doesn't have all the functionality SME has. So I still want to use SME as my primary server.
I now have give my other servers a fixed ip-adres so the dhcp-daemon isn't needed anymore. But now I have a (i guess) routing problem:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
62.216.x.x 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.110.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 62.216.x.x 0.0.0.0 UG 0 0 0 eth1
So i can ping 192.168.110.10 from my server (100.1 and 110.1). I can ping my server (100.1 and 110.1) from my clients (100.x), but I can't ping my other server (110.1) from my clients (100.x). Anybody with suggestions?
-
SME is not designed for this.
True, but it's also designed to be customisable. OP should not expect multiple NICs to be supported out of the box though.
Easiest way to support multiple networks is to use a router and the "local networks" panel.
-
Why would you need to have 3 NICs? If you need multiple network segments connecting internally to the SME, have routers with the WAN ports connected to the internal NIC on a switch and using DHCP or static and handling their own networks on their internal sides. Traffic from either of them (and all connected machines) will be considered internal network traffic for the SME and then there is no need for an overly complicated setup.
Keeping things as stock as possible usually works best for diaster recovery and later upgrades, etc.
Just my humble opinion.
-
did you work out the problem with dhcp on eth2??
I can see how this would not make sence to some but the use of 2 local networks that can not see each other is a very good thing if you require 2 private networks and only 1 internet feed. I have been stumped on this for a day or 2 now .....any help would be good.
-
No I didn't work out for me. I guess you could try to modify the templates and add eth2 in the config database but I don't know enough of it to make it work.