Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - poundjd

Pages: 1 2 [3] 4 5 ... 13
The last paragraph is really a product (service) that the company behind eBox is selling.  - So while I like the idea, they may not support development in that direction with out a dependency on the service. - they need to make money to stay open and continue the good work.

The main issue (as I see it) how are we going to organize all of this.  Once that is decided then the screens should just about make themselves apparent.

     First thanks for answering. and Yes, that an easy pat answer and quite correct as far as it goes, and is the perfect example of why this is and remains an ISSUE.  Please understand that the answer you gave me is one I have been guilty of giving out many many times myself.  

     For configuring an eBox we have pages and pages of very detailed directions. But for the "Other" stuff we give pat answers like above.  which while correct as far as it goes does very little to educate the user.  DynDNS and the services like them make it possible to have a DNS entry for your system, whither it has a fixed or dynamic IP.  The answer does not address all the other stuff that needs to be accomplished so that you can use the full capabilities of the eBox.

What I am trying to illuminate here is the need for documentation on this aspect of make the system useful to the user, just like proper configuration of the system is needed so are the proper configurations of the services (like DynDNS, or similar services and your ViOP provider) that the eBox uses.

Installation and Upgrades / External to eBox: what to do to make it work
« on: February 09, 2010, 11:43:23 pm »
All, I have been playing with eBox for quite a while and one thing that I have never really gotten a good answer for is what else (read as external to eBox) do I need to do to make it work.

For example,  I have an public domain -"" I want the domain at the house to be "" and mail from "*" and all sub domains to be forwarded to my home mail server ""  web pages at "" and ViOP calls to be delivered to my ViOP server at "". etc...

So what services do I need from a DNS provider?
     I think that I need a SOA record for the sub domain, and an A record to point to the NS of the Sub Domain.  I believe that I'll also need an MX record.  But what else? and why.  Now I believe that if the SOA record and the A record for the NS are in place all other DNS configuration for the '" domain can be handled by the eBox doing DNS.

   What if I need/want backup DNS services for when My server was not on line? What about email cashing if my server was not on line?  etc.....

I can't believe that I am the only one with these questions.

You know I think that maybe we should take one more step back from this and look at it again.
We have a few different types of services
     1) Services that your users directly interface with -> shares, e-mail, VoIP calls,...
     2) Services that your users indirectly interface with -> e-mail and other filters,....
     3) Services that your users may not even know about -> Firewalls, DHCP, DNS, Infrastructure setup,....

     Further each of these services have many configuration options that need to be addresses.  Also many of these functions have different configuration requirements for different aspects of the service, such as when the eBox is a client or when eBox is the server, or sometimes both.  For new administrators that can be quite confusing.

Installation and Upgrades / Re: Custom Samba Shares overwritten
« on: February 09, 2010, 07:06:17 pm »
There is no one CONFIG.FILE.mas.

    Every service has configuration files that must be stored in specific locations to allow that service to run (in this case Samba)  When a service is brought under eBox control and configuration one of the things that is done is that for every configuration file that the service uses a default eBox configuration file for that service is created using the exact same name and directory as the services configuration file but with ".mas" added to the end of it.  This is the file that eBox will open and process when it rewrites the standard configuration file for that service.

So if your service uses the configuration file SERVICE.CONFIGURE stored in the directory SERVICEDIRECTORY then in that same directory there will be a SERVICE.CONFIGURE.mas file.  If you make changes to the SERVICE.CONFIGURE file they will be overwritten every time eBox configures that service.  If you want some special configuration, that the eBox web interface does not allow for then you have to go to the SERVICE.CONFIGURE.mas file and place it there.  This will then be used for every reconfiguration of that service.  The one problem with  this is that these files are overwritten when eBox is upgraded... hence the SERVICE.CONFIGURE.mas.BACKUP FILE.

Hope this helps

News and Announcements / Re: eBox kernel packages available
« on: February 09, 2010, 06:53:16 pm »
My home network supports my wife and 4 very active kids,  3 of them are home schooled and need more help with scheduling and such.  Besides I need some way of keeping my home and work calendars synced up. - work calendar is exchange and locked down tight.... can't do much about setting up automatic sync....  can and do export and input Icalendar files - until that gets shut down.....

Installation and Upgrades / Re: Custom Samba Shares overwritten
« on: February 09, 2010, 06:42:37 pm »
  Updates do overwrite files all the time.

One approach that may work is to ensure that your customizations are done in the CONFIG.FILE.mas and that a copy of it is saved in CONFIG.FILE.MAS.BACKUP-File.Version.  Using this kind of system for all configurations will allow a much easier time of getting back to a working system after an upgrade.

Guys, I have a clarifying question to ask.

What are the limitations on traffic shaping, bonding, load balancing, and other advanced networking services in the two different configurations?

Installation and Upgrades / Re: Error trying to add a printer
« on: February 09, 2010, 06:13:52 pm »
You should enter a bug track report....

Installation and Upgrades / Re: DHCP question
« on: February 09, 2010, 05:26:45 pm »
  I have been playing at setting up a eBox server sence befor 1.0.  I still have not gotten one into production here at the house. ( I lost almost a year due to a surge at work that kept me off of the internet.) I really am still learning about FW rules and such.  I understand the concepts but have not put it to code yet.  Also the FW rules you will want will be driven by what you have running in the DMZ.  I would start with allowing nothing from the DMZ into the home network, and only allowing what is required into the DMZ network from the WAN.  Allowing all from the DMZ to the WAN is one easy solution but then if your DMZ is comprimised you become part of the botnets.... not good.  I'd recommend that you completly identify what traffice you need to support the services that you want to run in your DMZ and then write the FW Rules that implement that and only that....

Installation and Upgrades / Re: DHCP question
« on: February 09, 2010, 04:59:57 pm »
The concept of a DMZ is that of a zone with different protections than the rest of the network.  So it is really a construct of the FW Rules that you apply to that subnet. 

The services that you have in your DMZ will determine what rules you apply to that subnet.  IE if there is no reason for other internal devices to access the DMZ then your rules should prevent that.

Installation and Upgrades / Re: DHCP question
« on: February 09, 2010, 04:56:16 pm »
I also have an eBox with 5 network interfaces (MB interface, and 4NIC card).  I plan on using the MB NIC to be the wan connection, and the first NIC on the 4 NIC card to be the home network, the 2nd NIC to be my DMZ zone for risky services, and the third for HIGHLY Protected servers - NO ACCESS to/from WAN, and the 4th for testing/playing with new stuff, each will have a /24 subnet.  Latter if I get another Internet Access link (WAN2), then I'll use one of the NICs for access to WAN2.  Then I can play with load ballanceing and such.

News and Announcements / Re: eBox kernel packages available
« on: February 09, 2010, 03:58:14 am »
I want to use eBox for a full featured network protection solution.
I want to use eBox for a full featured Communications Server.
I want to use eBox for a full featured File Server/User Manager.
With the way things are partitioned now, I'll most likely setup several eBox servers in my house.  1st would be the File Server/User Manager - LDAP; 2nd would be the Gateway Server / full network protection; third would be web/email/gorupware.
PS.  Sorry for such a long silient spell.  - work got in the way.

Ok, I'm sourt of confussed,  I have a cable connection, my External IP is assigned by the Cable company using DHCP, and I assigne addresses in the House via DHCP to include all the DNS stuff.  My internal DHCP server assignes the the my internal IP of my gatway to all the internal IP's as both the Primary DNS, and Gateway.  It all works fine.  If I was not doing DHCP from the gateway box then that may be an issue.

So you guys with this problem are not useing the eBox as your Network Gateway? or you Not useing it to assigne IP via DHCP?

If that is the case then you have to manually input your DNS and Gateway in to your DHCP Server, or your systems directily.  My cable IP changes about once to twice a year, so if your's is similar then the work is not too bad.  I have over 20 systems in the house and use DHCP so that I don't go crazy....

Installation and Upgrades / Re: A really nasty bug has occurred
« on: July 23, 2009, 01:51:52 am »
Guys, I have IE8 on this vista system.  I'm going to burn a new cd from a newly down loaded ISO and reinstall.
Un less someone has a test that they want me to preform before I do that.  The problems are so basic that I think it may be a bad ISO on the CD (Bad CD or Image or both).

Pages: 1 2 [3] 4 5 ... 13