Integration corner

Abstract

These lines are thought to provide a clear and efficent integration among different eBox modules. Therefore, it gives an efficent and orthogonal way to work. Here some topics will be listed in order to leave ideas of possible eBox modules integrations.

Configured DNS and Gateways overwritten by DHCP

Configured DNS and Gateways addresses are overwritten by the last DHCP address. We must fix this behaviour (see #498)

Network Object

Currently, in TCP/IP stack a machine is likely to have the following attributes:

Attributes	eBox Module
Physical Address (MAC)	DHCP
Logical Address (IP)	DHCP - DNS - Objects
Human Readable Address (Name)	DNS
Application Level -> Grouping	DNS - Objects

A cute integration of all of this could be great.

Automatical object creation

The addresses of the eBox machine could be used to create one (or more) objects. For instance, when a remote IP printer is configured, it could be automatically create a network-object with the printer as a member.

DNS service and eBox's nameserver

If eBox is providing DNS service, it should add itself to the name server list. (this requires #498)

Mail Virtual Domains and DNS

DNS provide MX records to allow MTA sends mails to the proper destination through its DNS usage. It could be great to allow at the creation of a DNS domain, set a mail virtual domain just setting a tick there.

HTTP proxy and users

As printers, file sharing and mail allows, support users and groups integration at HTTP proxy to provide rules per user. It brings different problems such as objects integration and rule application. (this is in the roadmap for 0.13)