Topics

1

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 -"Jeffsdomain.us" I want the domain at the house to be "Home.Jeffsdomain.us" and mail from "*@Jeffsdomain.us" and all sub domains to be forwarded to my home mail server "Mail.Home.Jeffsdomain.us"  web pages at "WWW.Home.Jeffsdomain.us" and ViOP calls to be delivered to my ViOP server at "ViOP.Home.Jeffsdomain.us". 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 'Home.Jeffsdomain.us" 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.
-jeff
   

2

Installation and Upgrades / missing web pages on links from Dashboard.

« on: July 18, 2009, 04:17:58 am »

Guys,
I clicked on System in the dashboard and this is what I got.

Page not found(show help) (hide help)
we're sorry
The page cannot be found
If you typed the URL manually, please check it
Maybe a change in eBox's configuration or software made no longer available the requested page
If you need more help, you may want visit eBox's homepage for documentation and mailing lists

I also get it when clicking on the Network, & Logs, and when I clicked on the Software Management I get a really Nasty bug report that I filed earlier.
-jeff

3

Installation and Upgrades / A really nasty bug has occurred

« on: July 18, 2009, 04:08:59 am »

Guys, I don't remember how I got this but get it I did.

A really nasty bug has occurred
Exception
One composite element is given and slashes are given. The valid format requires no slashes
Trace
One composite element is given and slashes are given. The valid format requires no slashes at /usr/share/perl5/EBox/Model/CompositeManager.pm line 118
EBox::Model::CompositeManager::composite('EBox::Model::CompositeManager=HASH(0xab8e950)', '/events/') called at /usr/share/perl5/EBox/CGI/Run.pm line 201
EBox::CGI::Run::lookupModel('EBox::CGI::Events::Composite') called at /usr/share/perl5/EBox/CGI/Run.pm line 226
EBox::CGI::Run::_lookupViewController('EBox::CGI::Events::Composite', 'EBox') called at /usr/share/perl5/EBox/CGI/Run.pm line 96
EBox::CGI::Run::run('EBox::CGI::Run', 'Events/Composite/', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xb544d04)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb55e104)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb55e104)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xb544d04)') called at -e line 0
eval {...} called at -e line 0

4

Installation and Upgrades / Good configuration HOWTO, not eBox

« on: June 09, 2009, 04:47:34 am »

Guys,  This was a very interesting HOWTO, not about eBox but replicates a lot of the functionality.  Good explanations and discussion about the configuration of these tools.  May be of help when digging deep.

http://ubuntuforums.org/showthread.php?t=640760&highlight=eBox
-jeff

5

Installation and Upgrades / Help on Forum Profile - uploading picture.

« on: May 18, 2009, 05:21:27 pm »

Guys,
     I have been trying to upload my picture to my profile and can't seem to get it to upload.  I have tried loading it from my pictures folder (vista) and it failed.  I thought that it may be because their were spaces in the path. so I moved it to the c: directory on my vista box.  Still did not work.  I tried to load it from my Facebook profile using http and it still did not work.  So I am wondering what I am doing wrong.  It may be due to the size 1,255 KB is the reported size on my Vista workstation.

Please help.
-jeff

6

Installation and Upgrades / Dashboard display error

« on: May 17, 2009, 09:44:31 pm »

Guys on the dashboard, version 1.0-1
the first interface information is not visible, could it be printed in wrong color? it's the one in the green, the others show up.  none of the green area's have any information in them....

Clicking on the "Configure Widgets" puts a message in the browser bottom left status area of "Error on page."

Also on the dashboard, the interfaces should be displayed in order of their number, eth0 at the top and ethx at the bottom.  on mine it is eth1...eth4, eth0. 

I love the look and feel of this. Great work!
-jeff

7

Installation and Upgrades / General question about email and egroupware

« on: May 06, 2009, 03:48:50 am »

Ok, I am not looking to start a flame war but I am interested in why eBox uses egroupware and Postfix, instead of a package like citadel?  Was it a features issue, a purity issue, integration issue, or just simply timing? or something else?
-jeff

8

Installation and Upgrades / What versions of the products behind the modules are you useing?

« on: April 28, 2009, 05:04:32 am »

Guys,
    are you using ICS Bind 9.4 or 9.6 or something else in 1.0 and 1.1
what about all of the other software that your integrating.  I know that you try to keep the kernal the same as the 8.04 LTS version of Ubuntu, but what about the others?  would be really cool to see that on the features page.
-jeff

9

Installation and Upgrades / Help with DNS requirements to get email and other services running on my domain.

« on: April 17, 2009, 06:41:38 pm »

Hello all and thanks for your help,

     I have my domain - "mydomain.us",  I want my eBox server to be my Gateway system at home and for the home to have the domain "home.mydomain.us", with ebox being the only exposed IP and serving as the DNS relay for internal systems.  I want the ebox server will have the FDN of "ebox.home.mydomain.us".  My major problem is that the "home.mydomain.us" does not exist in the public DNS space.

My external IP is Provided via DHCP and has changed several times this last month.... go figure, so I'll be needing a Dynamic DNS program to update the records at the public DNS servers, as well as the reverse lookup record for my server.

What do I have to have the domain registrar enter into the public IP space?
     I think that I'll need 4 records entered, SOA for "home.mydomain.us", PTR and A record for "ebox.home.mydomain.us" and a MX record to have all mail for "mydomain.us" sent to "ebox.home.mydomain.us".

Is this sufficient?  Help and advice requested....
HOWTO's really appreciated.
-jeff

10

Installation and Upgrades / Web Site - needs to be upgraded now with screen shots from 1.0....

« on: April 13, 2009, 12:50:33 am »

Hey all,  The Dashboard is so cool why don't you have screen shots of it up on the web site?
-jeff

11

Installation and Upgrades / Looking for good documentation / tutorials

« on: April 11, 2009, 10:28:55 pm »

Guys,
    I am trying to gather a list of good HOWTO's / Documentation / Tutorials.  This is turning out to be much harder than I thought it would be. 

subjects of most interest right now:
Virtual domains as used in ebox what are they and how do they work?
getting from owning a domain to using it for you home servers?
understanding Manson files and how they work
understanding Perl, HTML and what ever else is needed to start programming ebox modules.
-jeff

I have just ordered a bunch of O'Reilly books on Perl and Lynix
10 years after getting my MS in computer science I am going to start programing again for fun.....

12

Installation and Upgrades / New Installation, Udev problems.

« on: April 09, 2009, 09:47:42 am »

Hello,
   Well I'm trying to install ebox from the ebox 1.0 install ISO.  Got the OS and ebox modules installed from CD.  Rebooted, and because I have 5 NIC's I checked the /etc/udev/rules.d/70-persistent-net.rules file.  I did not like what I saw and using nano I changed the file, rebooted and ran into troubles galore.  I then reinstalled the screen and keyboard and again using nano fixed the files and rebooted.  I'm exactly back where I started.  So how do I do that now?

(I am generating a log as I go that I plan to become a good through HOWTO, and I'll include that below between the lines.)  it is very very rough right now so please excuse.
_________________________________________________________________________
OK this is where I am going to document the installation of eBox 1.0 in my home network.

Why? The current gateway device does not offer enough flexibility and configuration options to keep my IT savy kids off of the non-school sites during the day.  They keep getting viruses on their systems.

what I have:

A domain registered with eNom Central called MYmailDOMAIN.US, that I'll use for email delivery.

Comcast Cable Modem:
   Domain      hsd1.pa.comcast.net
   IP Address   68.32.x.y 
   Subnet Mask   255.255.255.128 
   Gateway      68.32.x.w 
   DNS       168.87.75.194 
   DNS       268.87.64.146 
   DNS       368.87.72.130


Linksys WRT54G-TM running DD-WRT v24 as my gateway server
   Wan Domain   hsdi.pa.comcast.net
   WAN IP Address   68.32.x.y
   WAN Subnet Mask   255.255.255.128 
   WAN Gateway   68.32.x.w

   Lan Domain   Home.MyMailDomain.US
   LAN Subnet Mask   255.255.255.0
   LAN IP Address   192.168.1.1
   LAN Gateway   192.168.1.1
   LAN DNS      192.168.1.1

 
   
Linksys WRT54G V2 Running DD-WRT V24
Many switches and bridges.
Headless Dell box to run eBox on,
My Main workstation is a Windows VISTA system.
14+ computers

Current Network Configuration:
CABLEMODEM=====>{Linksys WRT54G-TM Running DD-WRT V24}==========={Home Lan}
                {IP DHCP 68.32.x.y from Cable Company}           {IP's DHCPed from DD-WRT}
 


What I want:

Desired network configuration:

CABLEMODEM=====>{NIC0 ->eBox with 5 NICS}=+=nic1===>192.168.1/24 -> DMZ, Servers, and other stuff
                                          |
                                          +=nic2===>192.168.2/23 -> Home & School LAN, 2 Wireless AP's running DD-WRT V24 in ap MODE 
                                          |
                                          +=nic3===>192.168.3/24 -> DEV LAN
                                          |
                                          +=nic3===>192.168.3/24 -> TEST LAN

I want to have the eBox provide all gateway services for my internal networks.

I would like the following services running on eBox: DHCP, Firewall, Web Proxie, NTP Server, eMail, eGroupware


OK with Ubunto there is a process that is used during the install that writes the hardware configuration files.  UDEV.  for Network devices Ubuntu writes out a file that records the hardware networking configuration.

Code: [Select]

poundjd@ebox:/etc/udev/rules.d$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x8086:0x1064 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:20:0c:56:2b", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b6", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b7", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
poundjd@ebox:/etc/udev/rules.d$

On my system I want the motherboards NIC to be the external or WAN ethernet interface  SO I use nano to change the file to

Code: [Select]

poundjd@ebox:/etc/udev/rules.d$ nano 70-persistent-net.rules
This did not work because poundjd is not root, and does not have write permissions to this directory.
so->

Code: [Select]

poundjd@ebox:/etc/udev/rules.d$ sudo nano 70-persistent-net.rules
[sudo] password for poundjd:
after saving both a backup and this file with changes

Code: [Select]

poundjd@ebox:/etc/udev/rules.d$ ls
05-options.rules            40-permissions.rules         60-persistent-storage-tape.rules  70-persistent-net.rules.backup     85-hwclock.rules    README
05-udev-early.rules         45-fuse.rules                60-symlinks.rules                 75-cd-aliases-generator.rules      85-ifupdown.rules
20-names.rules              55-hpmud.rules               61-persistent-storage-edd.rules   75-persistent-net-generator.rules  85-pcmcia.rules
30-cdrom_id.rules           60-persistent-input.rules    70-persistent-cd.rules            80-programs.rules                  90-modprobe.rules
40-basic-permissions.rules  60-persistent-storage.rules  70-persistent-net.rules           85-hdparm.rules                    95-udev-late.rules
poundjd@ebox:/etc/udev/rules.d$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
#
# Edit history:
# 2009 04 09 JDP Modified file to move eth0 to motherboard NIC, and sundance NIC to eth1-4.
#

# PCI device 0x8086:0x1064 (e100)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:20:0c:56:2b", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b6", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b7", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x1186:0x1002 (sundance)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:05:5d:5e:89:b4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
poundjd@ebox:/etc/udev/rules.d$

now to shutdown, as you can see below I still make lots of mistakes

Code: [Select]

poundjd@ebox:/etc/udev/rules.d$ shutdown
shutdown: time expected
Try `shutdown --help' for more information.
poundjd@ebox:/etc/udev/rules.d$ sudo shutdown
shutdown: time expected
Try `shutdown --help' for more information.
poundjd@ebox:/etc/udev/rules.d$ shutdown --help
Usage: shutdown [OPTION]... TIME [MESSAGE]
Bring the system down.

Options:
  -r                          reboot after shutdown
  -h                          halt or power off after shutdown
  -H                          halt after shutdown (implies -h)
  -P                          power off after shutdown (implies -h)
  -c                          cancel a running shutdown
  -k                          only send warnings, don't shutdown
  -q, --quiet                 reduce output to errors only
  -v, --verbose               increase output to include informational messages
      --help                  display this help and exit
      --version               output version information and exit

TIME may have different formats, the most common is simply the word 'now' which will bring the system down immediately.  Other valid formats are +m, where m is the number of
minutes to wait until shutting down and hh:mm which specifies the time on the 24hr clock.

Logged in users are warned by a message sent to their terminal, you may include an optional MESSAGE included with this.  Messages can be sent without actually bringing the
system down by using the -k option.

If TIME is given, the command will remain in the foreground until the shutdown occurs.  It can be cancelled by Control-C, or by another user using the -c option.

The system is brought down into maintenance (single-user) mode by default, you can change this with either the -r or -h option which specify a reboot or system halt
respectively.  The -h option can be further modified with -H or -P to specify whether to halt the system, or to power it off afterwards.  The default is left up to the
shutdown scripts.

Report bugs to <upstart-devel@lists.ubuntu.com>
poundjd@ebox:/etc/udev/rules.d$ shutdown -r
shutdown: time expected
Try `shutdown --help' for more information.
poundjd@ebox:/etc/udev/rules.d$ shutdown -r 0
shutdown: Need to be root
poundjd@ebox:/etc/udev/rules.d$ sudo shutdown -r 0

Broadcast message from poundjd@ebox
        (/dev/pts/0) at 1:46 ...

The system is going down for reboot NOW!
poundjd@ebox:/etc/udev/rules.d$



_________________________________________________________________________
As you can imagine I had problems after that reboot.  The network was dead.  After re-installing a screen and keyboard I was able to login and change the file back.


Now to my question.....  How do I change the OS so that eth0 is on the motherboard - the e100 PCI device, and the Sundance NIC interfaces are configured so that b4-b7 is eth1-eth4?



Any and all help is really appreciated.  Especially links to good documentation.
-jeff

13

Installation and Upgrades / Help, ISO image not passing check

« on: April 06, 2009, 04:37:25 am »

Hello,
I have downloaded the ISO image for 1.0 three times and burned it to a cd.  Each time when I try to have the system check the CD the check sum for ./isolinux/boot.cat fails.  Is there a way to verify the ISO image on DISK on my VISTA system before I burn another CD?  I have burned many images before with no problem.
-jeff

14

Installation and Upgrades / help, my ethernet connections keep changeing

« on: January 08, 2009, 04:24:30 am »

Hi all,  I have a system with a mother board Ethernet nic and I installed a 4 port nic as well.  When I load ubuntu and ebox the eln0-4 have no consistent order.  on one boot they will be one way on the next they will be some other way.  I am really confused.  I thought that the MB NIC would be eth0 and the 4 nics on the card would be 1-4, but no.  Is there some way that I can force some consistent pattern on them?  so that they are the same every reboot?
- really driving me nuts.

15

Installation and Upgrades / Ebox with 5 NIC's haveing problems

« on: January 07, 2009, 07:06:55 am »

OK, I bought a 4 port nic and there is a nic on the mb. 
I have loaded ubuntu + ebox at least 5 times.  I never get a consistent arrangement of eln0 on the mother board nic interface and the 4 nic's on the card being 1-4.  The mb nic just seams to show up where ever it wants to from boot to boot.  Am I missing something really fundamental here?  Please help;

Is there some configuration file that I have to set to make the mb nic show up as eln0?
-jeff