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.
31
Installation and Upgrades / Re: samba login too long
« on: February 10, 2010, 05:32:54 pm »
J. A. Calvo
Samba has no forums, only mailing lists. I checked and I know that samba + windows 7 = problems.
Just wanted to compare my experience /login times/ warnings to the others.
Surprised that nobody is using ebox as a pdc
alvinquah
Not above works for me. After 2+ mins of waiting, client can:
- browse network
- browse for mapped folders (click network->eboxserver)
I did not configure my home folder to be mapped as additional drive though. I am using a shortcut to \\eboxserver\whatever
Samba supports the execution of Windows logon scripts, which are scripts (.BAT or .CMD) that are executed on the client when a user logs on to a Windows domain. Note that these scripts are stored on the Unix side, but are transported across the network to the client side and executed once a user logs on. You cam modify/create the logon script to map your shares similar to below:
Read more at http://forum.ebox-platform.com/index.php?topic=2019.0
Samba has no forums, only mailing lists. I checked and I know that samba + windows 7 = problems.
Just wanted to compare my experience /login times/ warnings to the others.
Surprised that nobody is using ebox as a pdc
alvinquah
Not above works for me. After 2+ mins of waiting, client can:
- browse network
- browse for mapped folders (click network->eboxserver)
I did not configure my home folder to be mapped as additional drive though. I am using a shortcut to \\eboxserver\whatever
Samba supports the execution of Windows logon scripts, which are scripts (.BAT or .CMD) that are executed on the client when a user logs on to a Windows domain. Note that these scripts are stored on the Unix side, but are transported across the network to the client side and executed once a user logs on. You cam modify/create the logon script to map your shares similar to below:
Code: [Select]
# Here we map network drives to shares on the ebox server
echo Mapping Network Drives to Ebox Server
net use h: \\eboxserver\data
net use i: \\eboxserver\networkRead more at http://forum.ebox-platform.com/index.php?topic=2019.0
32
Installation and Upgrades / Re: samba login too long
« on: February 10, 2010, 04:07:38 pm »
nobody is using ebox as a pdc and windows 7 as client?
33
Installation and Upgrades / Re: Asterisk - configuration question
« on: February 10, 2010, 04:01:32 pm »
Thank you.
I understood the last two regarding the CID and devices (not users) advises.
Could you elaborate a little bit on the first one?
Scenario:
ebox + asterisk + external sip provider are configured using provided ebox web gui.
SIP user 1777XXXXXXX@callcentric.com is redirected to the 2125555555 by the provider.
ebox asterisk successfully registered with SIP provoder using WAN IP, username and password.
Two users with two extensions 1001 and 1002 configured using provided ebox web gui.
Two softphones installed and configured on client computers, both registered with ebox asterisk and are able to make outgoing calls by dialing "0" in front of the phone number.
Incoming call to the number 2125555555
SIP provider re-directs the call to the WAN IP registered (ebox ip). Now what? Which extension rings by default and how to configure this? Is it possible to have IVR let you choose the extension? Should I create an extension to the root user of ebox and make it as a default? If I put an extra NIC to into the ebox, and attach an ATA device to it, how to configure and make it as default device to answer the call?
I understood the last two regarding the CID and devices (not users) advises.
Could you elaborate a little bit on the first one?
Scenario:
ebox + asterisk + external sip provider are configured using provided ebox web gui.
SIP user 1777XXXXXXX@callcentric.com is redirected to the 2125555555 by the provider.
ebox asterisk successfully registered with SIP provoder using WAN IP, username and password.
Two users with two extensions 1001 and 1002 configured using provided ebox web gui.
Two softphones installed and configured on client computers, both registered with ebox asterisk and are able to make outgoing calls by dialing "0" in front of the phone number.
Incoming call to the number 2125555555
SIP provider re-directs the call to the WAN IP registered (ebox ip). Now what? Which extension rings by default and how to configure this? Is it possible to have IVR let you choose the extension? Should I create an extension to the root user of ebox and make it as a default? If I put an extra NIC to into the ebox, and attach an ATA device to it, how to configure and make it as default device to answer the call?
34
Installation and Upgrades / Re: OpenVPN Ethernet Bridging
« on: February 10, 2010, 03:36:25 pm »
That's why you use dhcp to serve all values automatically, don't you? 
35
Installation and Upgrades / Re: OpenVPN Ethernet Bridging
« on: February 10, 2010, 03:31:59 pm »Quote
You mean I should manually configure my WINS and DNS server (and possibly Gateway) on the tap adapter in Windows to finalize all this after the push code?
No, openvpn will push them for you. That's why I harcoded this values in the
Code: [Select]
/usr/share/ebox/stubs/openvpn/openvpn.conf.mas in the first place. When open restarted it creates a new Code: [Select]
/etc/openvpn/whatever.conf using values in your input through the web gui and openvpn.conf.mas as a template.Before the mod: the last line of the file would like:
Code: [Select]
push "route 192.168.1.0 255.255.255.0"After the mod:Code: [Select]
push "route 192.168.1.0 255.255.255.0"
push "dhcp-option DNS 192.168.1.1"
push "dhcp-option WINS 192.168.1.1"
push "dhcp-option DOMAIN yourdomain"When your windows/linux client gets an ip from openvpn DHCP, it gets all the values as well (dns, wins, getaway, etc.).
Important: when configuring openvpn do not assign the same subnet to the openvpn dhcp as you advertised network, it will not work. I personally if use 10.X.X.X instead of 192.168.X.X
openvpn
configuration: VPN address 10.0.17.0/24
advertised networks: 192.168.1.0/24
When openvpn connection is established, you can check that all values are pushed correctly (not modified you tap device) by ifconfig /all and route print
Hope this helps
36
Installation and Upgrades / Re: Need help with separating two internal interfaces.
« on: February 10, 2010, 02:42:41 am »
They are already separated by design. No extra configuration required.
37
Installation and Upgrades / Re: Need help with separating two internal interfaces.
« on: February 10, 2010, 12:41:45 am »
Still do not understand what you are trying to achieve. You will be able to connect to ebox no matter what as it's the same computer with 3 NIC interfaces. Having said that, you will not be able to access computers from one subset to the other. Computers on 10.0.1.0/24 will not be able to "see" computers on 192.168.2.0/24 and vise verse.
38
Installation and Upgrades / Re: Asterisk - configuration question
« on: February 10, 2010, 12:09:33 am »
Ok. You are right. With "0" it's dialing out. Thanks.
Except instead of the CID "2125555555" it shows ... the extension of the person who are calling "1001"
What's about incoming calls?
And could I assign an extension to the device (ip) rather then a user (domain user)?
Except instead of the CID "2125555555" it shows ... the extension of the person who are calling "1001"
What's about incoming calls?
And could I assign an extension to the device (ip) rather then a user (domain user)?
39
Installation and Upgrades / Re: Need help with separating two internal interfaces.
« on: February 10, 2010, 12:00:29 am »
You are able to ping and to access 192.168.2.100 simply because you have one computer (ebox) with 3 NICs. You will not be able to ping or access any computer on 192.168.2.0/24 network except ebox itself.
eth0: 192.168.1.100, - External interface for WAN?
192.168.0.0 – 192.168.255.255 is assigned to the private network and it's not routable. You need a DHCP or a static ip from your ISP.
eth0: 192.168.1.100, - External interface for WAN?
192.168.0.0 – 192.168.255.255 is assigned to the private network and it's not routable. You need a DHCP or a static ip from your ISP.
40
Installation and Upgrades / Re: slapd: connection_read(XX): no connection!
« on: February 09, 2010, 09:17:43 pm »Code: [Select]
Feb 9 10:05:10 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:05:10 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:05:10 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:05:10 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:05:10 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:06:17 <ebox_name> slapd[XXXXX]: <= bdb_equality_candidates: (AstAccountHost) not indexed
Feb 9 10:08:18 <ebox_name> slapd[XXXXX]: <= bdb_equality_candidates: (AstAccountHost) not indexed
Feb 9 10:09:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:09:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:01 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:06 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
Feb 9 10:10:06 <ebox_name> slapd[XXXXX]: connection_read(XX): no connection!
41
Installation and Upgrades / Re: samba login too long
« on: February 09, 2010, 09:08:49 pm »
nobody is using ebox as a pdc?
42
Installation and Upgrades / Asterisk - configuration question
« on: February 09, 2010, 09:06:43 pm »
Testing Asterisk module.
On the SIP provider tab I filled all the fields
Provider: CallCentric
Name: CallCentric
Username: 1777XXXXXXX
Password: PASSWORD
Server: callcentric.com
Recipient of incoming calls: 2125555555 <- did number
On tab Users and groups I created extension for my users 1001, 1002
Using soft phone I can call from extension (1001) to (1002) internally - it works.
All outgoing calls fail. Let say I call 2129999999:
By the way, for incoming calls which extension supposed to ring 1001, 1002, default?
Any way I could assign extension to the device (ip) rather then user (domain user)?
Only one DID supported?
I am prepared to edit sip.conf and extensions.conf by hand if required.
On the SIP provider tab I filled all the fields
Provider: CallCentric
Name: CallCentric
Username: 1777XXXXXXX
Password: PASSWORD
Server: callcentric.com
Recipient of incoming calls: 2125555555 <- did number
On tab Users and groups I created extension for my users 1001, 1002
Using soft phone I can call from extension (1001) to (1002) internally - it works.
All outgoing calls fail. Let say I call 2129999999:
Code: [Select]
tail -f /var/log/asterisk/messages
Call from user <user_name> to extension '2129999999' rejected because extension not foundAll incoming calls fail as well.Code: [Select]
tail -f /var/log/asterisk/messages
Call from '1777XXXXXXX' to extension '2125555555' rejected because extension not foundBy the way, for incoming calls which extension supposed to ring 1001, 1002, default?
Any way I could assign extension to the device (ip) rather then user (domain user)?
Only one DID supported?
I am prepared to edit sip.conf and extensions.conf by hand if required.
43
Installation and Upgrades / Re: OpenVPN Ethernet Bridging
« on: February 09, 2010, 03:53:04 pm »
ebox static ip =192.168.1.1
-----------
Lan: 192.168.1.0/24
-----------
openvpn
configuration: VPN address 10.0.17.0/24
advertised networks: 192.168.1.0/24
-----------
After your vpn client gets an ip, openvpn should create a necessary route. You can check it with
You can check it with
-----------
Lan: 192.168.1.0/24
-----------
openvpn
configuration: VPN address 10.0.17.0/24
advertised networks: 192.168.1.0/24
-----------
After your vpn client gets an ip, openvpn should create a necessary route. You can check it with
Code: [Select]
route printCode: [Select]
Network Destination Netmask Gateway Interface Metric
192.168.1.0 255.255.255.0 10.0.17.1 10.0.17.3 31Also dns, wins and gateway all should be 192.168.1.1You can check it with
Code: [Select]
ipconfig /all 44
Installation and Upgrades / Re: Moved to eBox 1.2 and Have Lots of Problems
« on: February 09, 2010, 03:27:26 am »
Same here. Version 1.4
On each module restart ebox logs:
On each module restart ebox logs:
Code: [Select]
Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/HTML/Mason/Component/Subcomponent.pm line 34.
Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/HTML/Mason/Component/Subcomponent.pm line 34.
Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/HTML/Mason/Component/Subcomponent.pm line 34.
45
Installation and Upgrades / Re: OpenVPN Ethernet Bridging
« on: February 09, 2010, 02:08:45 am »
I don't really understand your question: "we can all go off of"
Bridging mode does not work, period.
Routing mode kind of working with following modifications.
Clients must use a WINS server (such as samba) to allow cross-VPN network browsing to work. And still software that depends on broadcasts will not "see" machines on the other side of the VPN.
Before:
After:
As you see I harcoded my ebox ip, which is 192.168.1.1
and you are good to go.
You have mentioned that version 1.4 allows WINS. I did not tried that as yet.
If I did not answer your question, please, be more specific.
Bridging mode does not work, period.
Routing mode kind of working with following modifications.
Clients must use a WINS server (such as samba) to allow cross-VPN network browsing to work. And still software that depends on broadcasts will not "see" machines on the other side of the VPN.
Code: [Select]
nano -w /usr/share/ebox/stubs/openvpn/openvpn.conf.masBefore:
Code: [Select]
<%def advertisedNets>
<%args>
@nets
</%args>
% foreach my $net (@nets) {
% my ($net, $netmask) = @{ $net };
push "route <% $net %> <% $netmask %>"
%}
</%def>After:
Code: [Select]
<%def advertisedNets>
<%args>
@nets
</%args>
% foreach my $net (@nets) {
% my ($net, $netmask) = @{ $net };
push "route <% $net %> <% $netmask %>"
push "dhcp-option DNS 192.168.1.1"
push "dhcp-option WINS 192.168.1.1"
push "dhcp-option DOMAIN mydomain"
%}
</%def>As you see I harcoded my ebox ip, which is 192.168.1.1
Code: [Select]
sudo /etc/init.d/ebox openvpn restartand you are good to go.
You have mentioned that version 1.4 allows WINS. I did not tried that as yet.
If I did not answer your question, please, be more specific.