You are not logged in.
Hi,
I have some experience in configuring certain networked services, but I lack the basic knowledge/experience to start from a fresh install. In the past I have always relied on others to start me out, but I would like to learn to do this myself. I want to install and configure 1 centralized box with two ethernet interfaces, so I guess this would be a correct processing-order:
1. Install the base system
2. (Install and configure a robust) logging system (syslog-ng?)
3. dhcp and DNS (dhcpd, bind9)
4. firewall (iptables)
5. time (openntpd)
6. authentication (pam + kerberos)
7. user directory (openldap)
8. networked file system (NFS, samba)
9. mail (fetchmail, dovecot, postfix)
10. webserver (apache, php5)
11. database (postgresql)
12. calendar (davical)
13. telephony (asterisk)
14. backups (bacula)
15. VPN (openvpn)
Now I have a spare low-end box standing around, so I could just jump in and gather the much needed experience. The problem with this set-up is that wherever I go (both at the office and at home), there is already a network set up, and none of them can tolerate any downtime, so I would like very much to not bork those systems/networks.
Can I do this in a sandbox, like running an OS inside a VM? At home I have a Cisco smart switch installed that can handle multiple VLANs - maybe this is the solution (or not)...
Also, there must be loads of books covering this setup - can anyone recommend one?
Offline
Not sure why you need a sandbox for regular UNIX services. Maybe you're wanting a ssh port forwarding trick or something?
Maybe you mean a chroot jail.
Last edited by nomorewindows (2012-07-08 02:18:25)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
No, I simply mean that having two DHCP-servers inside the same network means trouble, no? So I would not be able to test my server out, unless I have a possibility to sandbox my server (and a client).
THX.
Offline
No, I simply mean that having two DHCP-servers inside the same network means trouble, no? So I would not be able to test my server out, unless I have a possibility to sandbox my server (and a client).
THX.
Buy a cheap switch (<$10) or a crossover cable to connect a client with your server.
Or skip the DHCP server, set a static IP (you will do that anyways) and test it. Then add the dhcp server when everthing else works.
Last edited by progandy (2012-07-09 10:46:33)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Buy a cheap switch (<$10) or a crossover cable to connect a client with your server.
Possible, but then I have no connection to the internet.
Or skip the DHCP server, set a static IP (you will do that anyways) and test it. Then add the dhcp server when everthing else works.
This is an acceptable solution. I would've however hoped there's something I'm doing wrong so I could learn a new chapter of linux networking ;-)
THX!
Offline