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.


Topics - thomas

Pages: [1]
1
I am using ebox 1.2 since the beginning and I have not any problems (now....)
I am looking in the forum, and I haven't find clear (and complete) instructions for the upgrade from 1.2 to 1.4.

I have read the http://trac.ebox-platform.com/wiki/Document/Documentation/Updates , and as I understand I have to manual add (or replace) the reposiroty:
deb http://ppa.launchpad.net/ebox/1.4/ubuntu hardy main
in /etc/apt/sources.lst
do an apt-get update
and an apt-get dist-upgrade

Is this enough?
Will my /usr/share/ebox/stubs/ directory  be replaced?
Will my /usr/share/squid/mime.conf will be replaced?
Will my /etc/ldap.secret be replaced?

Do I have to backup my changes?
Is there anything else, I have to keep in mind?

The above questions (and many more) are related with one of my ebox installations, a box acting as router, proxy, vpn, gateway, dhcp etc


I would like to know if this is a completely safe operation (the upgrade) after all.




2
Installation and Upgrades / rrd problem
« on: October 12, 2009, 02:04:59 pm »
My log (/var/log/syslog) is full of these messages:

Code: [Select]
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/swap/swap-free.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/swap/swap-cached.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/processes/ps_state-running.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/processes/ps_state-sleeping.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/processes/ps_state-zombies.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/processes/ps_state-stopped.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/processes/ps_state-paging.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)
Oct 12 15:00:22 router collectd[9716]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/router/processes/ps_state-blocked.rrd) failed: illegal attempt to update using time 1255348822 when last update time is 1255348822 (minimum one second step)

Does anybody is aware of the problem, or even more of the solution?

3
Installation and Upgrades / Squid caching exemption
« on: September 19, 2009, 05:12:49 pm »
How can I exempt specific networks or specific IPs from caching?
I have a lot of Ip Cameras in a particular subnetwork, which is different from the Internal Lan.
I have enabled the transparent proxy module, and I see now that all the traffic from the cameras (GBytes) is caching.

The gui allows only domains to exempt from cache.
Thx

4
Installation and Upgrades / Two Network Problems
« on: August 27, 2009, 02:14:01 pm »
Hello
My first (and most important) problem is the vpn connections. I have multiple ADSL lines and I forward a specific port on each of them in my internal ebox router 's port of openvpn server.
When I first setup the vpn server, all worked fine. After that I added the second ADSL line and then the problems began. When I added the third line the problems became bigger. I have setup the mutliple gateway procedures (with weights) and make the one gateway the default gateway. I tried a lot of things but I can't have a stable connection with vpn server. I connect after a lot of retries and when I finally connect I loose the connection (vpn connection failed) after a few minutes.
I tried to forward different ports on the external lines to the same port in the internal ebox router, and I tried to forward the same ports with no luck

My topology

Code: [Select]
                                          -------------

10.10.a.101 ---------|                    |           |-----eth1----10.10.x.0/24

                     |                    |           |-----eth2----10.10.y.0/24

10.10.a.102 ---------|------------ eth5---|           |-----eth0----10.10.z.0/24

                     |                    |   ebox    |-----eth3----10.10.m.0/24

10.10.a.103 ---------|                    |           |-----eth4----10.10.n.0/24

                                          -------------

The second problem has to do with the virtual interfaces. In the external interface when I add a second ip, I cannot connect to the second lan. Specificall my primary ip is 10.10.a.1 and I add the 192.168.a.1. I can still reach clients (ADSL modems) in the 10.10.a.0/24 network, but I cannot even ping clients in the 192.168.a.0/24 networks.

Thx in advance

5
Hi again.
I am running ebox 1.2. Every client mounts many share (at least 3). The web interface shows only the first share.
This is not something critical, but this is still an issue.

6
Installation and Upgrades / firewall issue: bug or feature?
« on: July 27, 2009, 01:48:23 am »
Hello.

I have a server with 6 interfaces (6 subnets). The server acts as dhcp server, dns server, http proxy server, mail filter server.... In general it acts as gateway.

With ebox 1.0 i could assign a dns name to this server (e.g. router.domain.lan) to only one interface (e.g. 10.100.10.1) and i could reach him from every subnet (10.100.10.0/24, 10.100.11.0/24, 10.100.12.0/24 etc). With ebox 1.2 I can only reach this dns name from the same subnet (10.100.10.0/24). From every other subnet i must type the ip address of the subnet's interface. So if i am on a computer with ip 10.100.14.75 i must type https://10.100.14.1 to reach the router.domain.lan.

I looked in the logs and I saw that packets are dropped.
So how can i have a unique dns name for that server?

Thanks in advance.

Pages: [1]