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.
61
Installation and Upgrades / Web interface shows only the first share
« on: July 27, 2009, 12:26:50 pm »
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.
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.
62
Installation and Upgrades / Re: firewall issue: bug or feature?
« on: July 27, 2009, 12:23:33 pm »
Will the update be available to ebox 1.2, or are you fixing the beta version?
I am still having the issue with jabber.
I am still having the issue with jabber.
63
Installation and Upgrades / Re: firewall issue: bug or feature?
« on: July 27, 2009, 01:55:19 am »
Hi again
I forgot to mention that i allow everything from everywhere. I did this from ebox's web interface and NOT from the command line through iptables' commands.
So there is no issue that i block something by mistake.
I forgot to mention that i allow everything from everywhere. I did this from ebox's web interface and NOT from the command line through iptables' commands.
So there is no issue that i block something by mistake.
64
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.
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.
65
Installation and Upgrades / Re: Jabber setup
« on: July 22, 2009, 05:02:16 pm »
Surprisingly with 1.0 I did make jabber to work with my custom domain. The strange thing is, that, with my fresh install of 1.2 I can't. I read every possible post concerning jabber, but still no luck.
Is it possible for someone, to explain us how can we set up jabber with a custom domain?
To be more specific:
-I always get internal server error in pidgin
-I can resolve the custom domain domain.lan
-my /etc/hosts file looks like this:
127.0.0.1 localhost.localdomain localhost
10.10.11.101 users.domain.lan users
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Is it possible for someone, to explain us how can we set up jabber with a custom domain?
To be more specific:
-I always get internal server error in pidgin
-I can resolve the custom domain domain.lan
-my /etc/hosts file looks like this:
127.0.0.1 localhost.localdomain localhost
10.10.11.101 users.domain.lan users
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts