astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] sqlite cdr

[Darrick H. <dha...@dj...>]

walter trucci wrote:
> You are great!
I don't think I'd go quite that far...more notes below.
>
> 2007/3/5, Darrick Hartman <dha...@dj... 
> <mailto:dha...@dj...>>:
>
>     Darrick Hartman wrote:
>     > walter trucci wrote:
>
>     > Thanks.  These are helpful.  Looks like sqlite is linking
>     against stuff
>     > improperly.  I haven't used it, only started building it at the
>     request
>     > of others.
>     >
>
>     I found the problem and will take care of it tomorrow.  I almost have
>     the cdr_sqlite stuff right too.
>
>
After some further digging, it appears that asterisk-1.2x will only 
support sqlite2 (not sqlite3--which compiles so nicely.  sqlite2 
requires a patch to do cross-compiling).  sqlite3 may or may not be 
supported by asterisk-1.4.  (The mantis bug tracker wasn't exactly clear 
on this.)  For my purposes in the 0.4 branch, sqlite2 is the way we have 
to go since we'll be staying with asterisk-1.2 in that branch.

I'm redoing the sqlite package in 0.4 branch and will have that and the 
cdr stuff ready to go tomorrow.  Assuming it builds cleanly (building 
right now), I just need to clean up the hacks I put in the asterisk.mk 
file. 

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] System Lockdown/securement [Was: Re: LDAP authentication]

[Bryce C. <br...@rh...>]

Thanks Kris! I'm honoured.
There's one further issue of absolute securement that I can't quite 
figure out yet though which is the matter of physical access. If they 
simply mount the CF card, then they can replace the original cron job 
with an insecure one, or worse yet simply remove it all and then they've 
got total control.
Then again, LDAP and Radius are both susceptible to this "brute force" 
:-P attack. However I am definitely interested in solving this. Perhaps 
using a strictly ROM FS? Unpacking an FS out of NVRAM? I'm kind of 
leaning towards the latter as it's still upgradeable, perhaps using a 
signed flashing utility, but as I understand SquashFS, it would seem to 
be the even simpler route. Does anyone have experience with this? It 
seems like a pure read-only FS (i.e. a la CD) would be ideal for 
Astlinux, and a local CF medium would provide for very fast boot times.

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Kristian Kielhofner wrote:
> On 3/5/07, Lenir Santiago <fla...@ya...> wrote:
>   
>> we have about 20 boxes in client offices which we manage for them, and what
>> we want to do is prevent root access via ssh (for security) and use a
>> maintenance account (or one for each of our techs) to login to the box if we
>> need to and if we ever need to change a password (or all passwords) we can
>> do it at the ldap server. Also if its easier, radius would also work for us.
>>
>>
>>     
>
> Hmmm...
>
>   That is interesting.
>
>   The real problem is going to be that uClibc and all of the other
> base components of AstLinux don't support NSS or PAM.  Those things
> are usually not required (or wanted) in embedded systems.
>
>   I like Bryce's SSH key idea.
>
>   

Re: [Astlinux-users] sqlite cdr

[walter t. <sta...@gm...>]

You are great!

2007/3/5, Darrick Hartman <dha...@dj...>:
>
> Darrick Hartman wrote:
> > walter trucci wrote:
> >
> >> This are the errors
> >>
> >> pbx ~ # sqlite3
> >> /usr/bin/sqlite3: line 46:
> >> /home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No
> >> such file or directory
> >> /usr/bin/sqlite3: line 50:
> >> /home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No
> >> such file or directory
> >> /usr/bin/sqlite3: line 87: cd:
> >> /home/dhartman/astlinux/branches/0.4/build_i586/sqlite-3.3.13: No such
> >> file or directory
> >> /usr/bin/sqlite3: line 87:
> >>
> /home/dhartman/astlinux/branches/0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc:
> >> No such file or directory
> >>
> >>
> > Thanks.  These are helpful.  Looks like sqlite is linking against stuff
> > improperly.  I haven't used it, only started building it at the request
> > of others.
> >
>
> I found the problem and will take care of it tomorrow.  I almost have
> the cdr_sqlite stuff right too.
>
> Darrick
>
> --
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] LDAP authentication

[Kristian K. <kri...@gm...>]

On 3/5/07, Lenir Santiago <fla...@ya...> wrote:
> we have about 20 boxes in client offices which we manage for them, and what
> we want to do is prevent root access via ssh (for security) and use a
> maintenance account (or one for each of our techs) to login to the box if we
> need to and if we ever need to change a password (or all passwords) we can
> do it at the ldap server. Also if its easier, radius would also work for us.
>
>

Hmmm...

  That is interesting.

  The real problem is going to be that uClibc and all of the other
base components of AstLinux don't support NSS or PAM.  Those things
are usually not required (or wanted) in embedded systems.

  I like Bryce's SSH key idea.

-- 
Kristian Kielhofner

[Astlinux-users] How should I change SetCIDName(${CALLERIDNAME} to Set(CALLERID(name)=name)?

[nedi <ne...@gm...>]

Hi all
I have SC-375 GSM Gatewa and problems with Caller ID forwarding  from 
Asterisk to Mobile
can be  my caller id are wrong  in Astlinux asterisk ???
i have it so :

[incomingsipgate.de]
exten =>12366,1,SetCIDName(${CALLERIDNAME})
exten =>12366,2,Dial(local/10@10)

How should I change SetCIDName(${CALLERIDNAME}  to  Set(CALLERID(name)=name) 
???

Regards

nedi

Re: [Astlinux-users] libpq error WAS: trunk compile error stuff

[Darrick H. <dha...@dj...>]

ast...@el... wrote:
> ast...@el... said:
>   
>> Also, the PostgreSQL version being used, 8.1.4 , doesn't seem to be
>> available at the download sites anymore. Closest match is 8.1.7 which
>> seems to compile alright.
>>     
>
> Okay, seems like I am a liar. Not only must the version number be bumped
> up, a change needs to be made to the asterisk package asterisk.mk
>   
I'm working on this.  There are several issues with the current 
PostgreSQL and sqlite code.  I tried to commit something earlier, but 
the svn site was not resolving correctly.  I'll have something up 
tomorrow.  That patch is not sufficient to build the necessary modules.  
app_sql_postgres might build, but the cdr module won't.  I really don't 
think either will with that current patch.

I'll post a note to the list after this is corrected.

Darrick

>
> the original line for libpq support is the following;
>
> $(ASTERISK_DIR)/.configured: $(ASTERISK_DIR)/.source
> ifeq ($(strip $(BR2_PACKAGE_ASTERISK_LIBPQ_CUSTOM)),y)
>       cp package/asterisk/custom/*.c $(ASTERISK_DIR)/apps/
>       toolchain/patch-kernel.sh package/asterisk/custom/\*.patch
>
>
> which should be changed to;
>
> $(ASTERISK_DIR)/.configured: $(ASTERISK_DIR)/.source
> ifeq ($(strip $(BR2_PACKAGE_ASTERISK_LIBPQ_CUSTOM)),y)
>        toolchain/patch-kernel.sh $(ASTERISK_DIR) package/asterisk/custom/ 
> asterisk\custom\*.patch
>
>
>
> Seems it was choking on the copy of *.c (which seems unnecessary anyways
> because there are no c files?), claiming it's a directory, then the search
> for the patch file was going bad due to a filepath issue.
>
> This is applicable to both 0.4 and trunk
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>   


-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] libpq error WAS: trunk compile error stuff

[<ast...@el...>]

ast...@el... said:
> Also, the PostgreSQL version being used, 8.1.4 , doesn't seem to be
> available at the download sites anymore. Closest match is 8.1.7 which
> seems to compile alright.

Okay, seems like I am a liar. Not only must the version number be bumped
up, a change needs to be made to the asterisk package asterisk.mk


the original line for libpq support is the following;

$(ASTERISK_DIR)/.configured: $(ASTERISK_DIR)/.source
ifeq ($(strip $(BR2_PACKAGE_ASTERISK_LIBPQ_CUSTOM)),y)
      cp package/asterisk/custom/*.c $(ASTERISK_DIR)/apps/
      toolchain/patch-kernel.sh package/asterisk/custom/\*.patch


which should be changed to;

$(ASTERISK_DIR)/.configured: $(ASTERISK_DIR)/.source
ifeq ($(strip $(BR2_PACKAGE_ASTERISK_LIBPQ_CUSTOM)),y)
       toolchain/patch-kernel.sh $(ASTERISK_DIR) package/asterisk/custom/ 
asterisk\custom\*.patch



Seems it was choking on the copy of *.c (which seems unnecessary anyways
because there are no c files?), claiming it's a directory, then the search
for the patch file was going bad due to a filepath issue.

This is applicable to both 0.4 and trunk

Re: [Astlinux-users] LDAP authentication

[Bryce C. <br...@rh...>]

Lenir,
I would suggest disabling console logins, disabling password 
authentication and root login in SSH, and create a maintenance account 
with a disabled password (or disable passwords altogether in PAM), then 
use SSH keys for authentication. This accomplishes the security aspect. 
As far as changing access restrictions, you could simply have a master 
copy of authorized_keys containing the SSH keys of only those 
technicians that are authorized to connect, and use a nightly cron job 
to update this list on the boxes. Finally, to ensure that the clients 
don't just slip their own authorized_keys in, be sure to use gnupg to 
sign the authorized_keys master file and check it upon every download.

I'm pretty sure this would take care of your requirements immediately as 
well as prevent any sensitive data from crossing public networks (you 
never put radius over the internet only across protected networks in 
secure environments.)

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Lenir Santiago wrote:
> we have about 20 boxes in client offices which we manage for them, and 
> what we want to do is prevent root access via ssh (for security) and 
> use a maintenance account (or one for each of our techs) to login to 
> the box if we need to and if we ever need to change a password (or all 
> passwords) we can do it at the ldap server. Also if its easier, radius 
> would also work for us.
>
> */Bryce Chidester <br...@rh...>/* wrote:
>
>     Lenir,
>     pam_ldap and nss_ldap are for using LDAP as a way to authenticate
>     and resolve system user/group data from an LDAP source, however
>     astlinux only has one user as it should, root, which should never
>     be authenticated over LDAP. Is this what you're trying to do? Or
>     what exactly are you trying to authenticate?
>
>     Regards,
>     Bryce Chidester
>     Rhino Equipment Corp.
>     br...@rh... Tel: +1 (480) 940-1826 x6351 Fax: +1 (480) 961-1826 FWD: 633686 x6351 IP: asterisk.rhinoequipment.com x6351  THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers. 
>
>
>
>     Lenir Santiago wrote:
>>     Is there any way to get pam_ldap authentication or nss_ldap or
>>     both working on Astlinux?
>>     ------------------------------------------------------------------------
>>     Be a PS3 game guru.
>>     Get your game face on with the latest PS3 news and previews at
>>     Yahoo! Games.
>>     <http://us.rd.yahoo.com/evt=49936/*http://videogames.yahoo.com>
>>     ------------------------------------------------------------------------
>>      ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>     ------------------------------------------------------------------------
>>      _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users  Donations to support AstLinux are graciously accepted via PayPal
>>      to pa...@kr....
>     -------------------------------------------------------------------------
>     Take Surveys. Earn Cash. Influence the Future of IT
>     Join SourceForge.net's Techsay panel and you'll get the chance to
>     share your
>     opinions on IT & business topics through brief surveys-and earn cash
>     http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
>     Astlinux-users mailing list
>     Ast...@li...
>     https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
>     Donations to support AstLinux are graciously accepted via PayPal
>     to pa...@kr....
>
>
> ------------------------------------------------------------------------
> Be a PS3 game guru.
> Get your game face on with the latest PS3 news and previews at Yahoo! 
> Games. <http://us.rd.yahoo.com/evt=49936/*http://videogames.yahoo.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] sqlite cdr

[Darrick H. <dha...@dj...>]

Darrick Hartman wrote:
> walter trucci wrote:
>   
>> This are the errors
>>  
>> pbx ~ # sqlite3
>> /usr/bin/sqlite3: line 46: 
>> /home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No 
>> such file or directory
>> /usr/bin/sqlite3: line 50: 
>> /home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No 
>> such file or directory
>> /usr/bin/sqlite3: line 87: cd: 
>> /home/dhartman/astlinux/branches/0.4/build_i586/sqlite-3.3.13: No such 
>> file or directory
>> /usr/bin/sqlite3: line 87: 
>> /home/dhartman/astlinux/branches/0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc: 
>> No such file or directory
>>
>>     
> Thanks.  These are helpful.  Looks like sqlite is linking against stuff 
> improperly.  I haven't used it, only started building it at the request 
> of others.
>   

I found the problem and will take care of it tomorrow.  I almost have 
the cdr_sqlite stuff right too.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] LDAP authentication

[Lenir S. <fla...@ya...>]

we have about 20 boxes in client offices which we manage for them, and what we want to do is prevent root access via ssh (for security) and use a maintenance account (or one for each of our techs) to login to the box if we need to and if we ever need to change a password (or all passwords) we can do it at the ldap server. Also if its easier, radius would also work for us.

Bryce Chidester <br...@rh...> wrote:        Lenir,
 pam_ldap and nss_ldap are for using LDAP as a way to authenticate and resolve system user/group data from an LDAP source, however astlinux only has one user as it should, root, which should never be authenticated over LDAP. Is this what you're trying to do? Or what exactly are you trying to authenticate?
 
Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh... Tel: +1 (480) 940-1826 x6351 Fax: +1 (480) 961-1826 FWD: 633686 x6351 IP: asterisk.rhinoequipment.com x6351  THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers. 
 
 
 Lenir Santiago wrote: Is there any way to get pam_ldap authentication or nss_ldap or both working on Astlinux?
    
   
---------------------------------
Be a PS3 game guru.
 Get your game face on with the latest PS3 news and previews at Yahoo! Games.   

---------------------------------
 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
   

---------------------------------
 _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users  Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
  -------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

 
---------------------------------
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Lonnie A. <li...@lo...>]

Kristian,

I will be quiet now, I looked at your "astfw" code... too much to get =20=

my brain around on this Monday.

In my thinking I was 'assuming' that asterisk was sitting behind the =20
same NAT as would any LAN IP's, when a WAN interface is specified =20
(non-PBX only mode).  This is where I got confused.

I have to trust Kristian on this one.

Sorry for all the comments...

Lonnie


On Mar 5, 2007, at 1:55 PM, Kristian Kielhofner wrote:

> On 3/5/07, Lonnie Abelbeck <li...@lo...> wrote:
>> Kristian,
>>
>> I think I understand you, maybe I am wrong? <smile>
>>
>> But, I will try one more time.
>>
>> I'm no iptables guru, but this might be what I am suggesting:
>> iptables -t nat -A PREROUTING -i sis1 -p udp =96dport 5060 -j DNAT =
=96to
>> 192.168.1.10:5060
>>
>> This puts an inbound, external udp/5060 rule in the NAT table
>> pointing to your asterisk box.  If a different SIP device now tries
>> to register out, it will not be given the external/public of 5060
>> since it is reserved by the NAT rule above.  correct?
>>
>> Of course, if you want to receive inbound SIP to asterisk, you would
>> also have to add something like:
>> iptables -A FORWARD --destination 192.168.1.10 -p udp --dport 5060 -j
>> ACCEPT
>>
>> Is this clear?
>>
>> Lonnie
>>
>
> Lonnie,
>
>   I started on FreeBSD/OpenBSD and I understand ipfw/pf rules quite
> well.  I appreciate the   translation to iptables for the other
> readers :).
>
>   We are talking about two different things.  You want to put an
> Asterisk box behind another Linux/iptables router (that isn't running
> Asterisk) and translate traffic on the Linux/iptables box.
>
>   I want to put a SIP device behind a Linux/iptables router that is
> running Asterisk.
>
>   This causes a problem.
>
>   The iptables MASQUERADE & SNAT (not DNAT) iptables code (by default)
> will assign port 5060 on the external interface as the port to be used
> for PAT with the SIP device BEHIND the Linux router.  This will make
> port 5060 on the Linux/iptables/Asterisk box to be inaccessible via
> SIP because incoming traffic to the external interface on port 5060
> will be translated and routed to the SIP device behind nat because of
> the iptables MASQ state.
>
>   Using --to-ports forces the MASQ/SNAT code to only use ports in the
> defined range - not the port used by the device inside the NAT.
>
>   Is this making sense to anyone else?  If so, can you explain it
> better than I can :)?
>
> --=20
> Kristian Kielhofner
>
> ----------------------------------------------------------------------=20=

> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to =20=

> pa...@kr....
>

Re: [Astlinux-users] sqlite cdr

[Darrick H. <dha...@dj...>]

walter trucci wrote:
> This are the errors
>  
> pbx ~ # sqlite3
> /usr/bin/sqlite3: line 46: 
> /home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No 
> such file or directory
> /usr/bin/sqlite3: line 50: 
> /home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No 
> such file or directory
> /usr/bin/sqlite3: line 87: cd: 
> /home/dhartman/astlinux/branches/0.4/build_i586/sqlite-3.3.13: No such 
> file or directory
> /usr/bin/sqlite3: line 87: 
> /home/dhartman/astlinux/branches/0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc: 
> No such file or directory
>
Thanks.  These are helpful.  Looks like sqlite is linking against stuff 
improperly.  I haven't used it, only started building it at the request 
of others.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] sqlite cdr

[walter t. <sta...@gm...>]

This are the errors

pbx ~ # sqlite3
/usr/bin/sqlite3: line 46:
/home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No such
file or directory
/usr/bin/sqlite3: line 50:
/home/dhartman/astlinux/branches/0.4/toolchain_build_i586/bin/sed: No such
file or directory
/usr/bin/sqlite3: line 87: cd:
/home/dhartman/astlinux/branches/0.4/build_i586/sqlite-3.3.13: No such file
or directory
/usr/bin/sqlite3: line 87:
/home/dhartman/astlinux/branches/0.4/build_i586/staging_dir/bin/i586-linux-uclibc-gcc:
No such file or directory



2007/3/5, Darrick Hartman <dha...@dj...>:
>
> walter trucci wrote:
> > Thanks a lot. I see that maybe there is some errors on sqlite
> > compiling, when I run sqlite3 there are some errors.
> Please provide the errors so I can correct them.  sqlite was added as a
> request, but the developers currently don't use it.  It appears to
> compile cleanly.
>
> Darrick
>
> --
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] LDAP authentication

[Bryce C. <br...@rh...>]

Lenir,
pam_ldap and nss_ldap are for using LDAP as a way to authenticate and 
resolve system user/group data from an LDAP source, however astlinux 
only has one user as it should, root, which should never be 
authenticated over LDAP. Is this what you're trying to do? Or what 
exactly are you trying to authenticate?

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Lenir Santiago wrote:
> Is there any way to get pam_ldap authentication or nss_ldap or both 
> working on Astlinux?
>
> ------------------------------------------------------------------------
> Be a PS3 game guru.
> Get your game face on with the latest PS3 news and previews at Yahoo! 
> Games. <http://us.rd.yahoo.com/evt=49936/*http://videogames.yahoo.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] LDAP authentication

[Lenir S. <fla...@ya...>]

Is there any way to get pam_ldap authentication or nss_ldap or both working on Astlinux?

 
---------------------------------
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Bryce C. <br...@rh...>]

I'm not an iptables guru and I have no idea who would do what. However, 
if iptables could somehow dynamically create port forwards (I didn't 
know it could), the issue is still that the 2nd SIP device thinks it's 
on 5060 so when it says From: <1234@IPADDR: 5060>, it tells the remote 
service to call back to 5060.
I'm sure Kris can further expand on this, however I'm fairly certain 
that this is all just the common case you cannot both forward a port and 
host it locally on a router.

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Lonnie Abelbeck wrote:
> Bryce,
>
>> When the SIP device connects to its outside host, its' identified as 
>> being at 123.45.67.8:5060 (source address), however 123.45.67.8 is 
>> the IP of the Astlinux router and port 5060 is the port Asterisk is 
>> already listening on.
>
> Isn't iptables smart enough to realize that the udp/external 5060 nat 
> table is in use,  and automatically assign a different external port 
> of the 2'nd SIP device?
>
> Lonnie
>
> On Mar 5, 2007, at 2:27 PM, Bryce Chidester wrote:
>
>> It makes sense to me, but nonetheless here's my 
>> translation/simplification.
>>
>> If a router is running Asterisk, with SIP enabled, then port 5060 
>> (and whatever RTP range is defined) are claimed by Asterisk. 
>> Generally, this does not present a problem, except until you have to 
>> try and NAT another SIP device behind it. In order for the SIP device 
>> to communicate to the outside (technically, for the outside to talk 
>> to it), there must be a port forward in place on the router. This is 
>> where the conflict occurs.
>> When the SIP device connects to its outside host, its' identified as 
>> being at 123.45.67.8:5060 (source address), however 123.45.67.8 is 
>> the IP of the Astlinux router and port 5060 is the port Asterisk is 
>> already listening on. When the remote service tries to call the SIP 
>> device, it actually connects to Asterisk and the call won't go through.
>> As for the "fix" with MASQPORTS, you're only forwarding the RTP data 
>> so audio will go through without a hitch, however this does not solve 
>> the conflicting claims for port 5060.
>> Simplest fix is to set your SIP phone, or Asterisk, to use a 
>> different port for SIP than 5060 (I think 5082 is another common choice).
>> Regards,
>> Bryce Chidester
>> Rhino Equipment Corp.
>> br...@rh...
>> Tel: +1 (480) 940-1826 x6351
>> Fax: +1 (480) 961-1826
>> FWD: 633686 x6351
>> IP: asterisk.rhinoequipment.com x6351
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.
>>     
>>
>>
>> Kristian Kielhofner wrote:
>>> On 3/5/07, Lonnie Abelbeck <li...@lo...> wrote:
>>>   
>>>> Kristian,
>>>>
>>>> I think I understand you, maybe I am wrong? 
>>>>
>>>> But, I will try one more time.
>>>>
>>>> I'm no iptables guru, but this might be what I am suggesting:
>>>> iptables -t nat -A PREROUTING -i sis1 -p udp –dport 5060 -j DNAT –to
>>>> 192.168.1.10:5060
>>>>
>>>> This puts an inbound, external udp/5060 rule in the NAT table
>>>> pointing to your asterisk box.  If a different SIP device now tries
>>>> to register out, it will not be given the external/public of 5060
>>>> since it is reserved by the NAT rule above.  correct?
>>>>
>>>> Of course, if you want to receive inbound SIP to asterisk, you would
>>>> also have to add something like:
>>>> iptables -A FORWARD --destination 192.168.1.10 -p udp --dport 5060 -j
>>>> ACCEPT
>>>>
>>>> Is this clear?
>>>>
>>>> Lonnie
>>>>
>>>>     
>>> Lonnie,
>>>
>>>   I started on FreeBSD/OpenBSD and I understand ipfw/pf rules quite
>>> well.  I appreciate the   translation to iptables for the other
>>> readers :).
>>>
>>>   We are talking about two different things.  You want to put an
>>> Asterisk box behind another Linux/iptables router (that isn't running
>>> Asterisk) and translate traffic on the Linux/iptables box.
>>>
>>>   I want to put a SIP device behind a Linux/iptables router that is
>>> running Asterisk.
>>>
>>>   This causes a problem.
>>>
>>>   The iptables MASQUERADE & SNAT (not DNAT) iptables code (by default)
>>> will assign port 5060 on the external interface as the port to be used
>>> for PAT with the SIP device BEHIND the Linux router.  This will make
>>> port 5060 on the Linux/iptables/Asterisk box to be inaccessible via
>>> SIP because incoming traffic to the external interface on port 5060
>>> will be translated and routed to the SIP device behind nat because of
>>> the iptables MASQ state.
>>>
>>>   Using --to-ports forces the MASQ/SNAT code to only use ports in the
>>> defined range - not the port used by the device inside the NAT.
>>>
>>>   Is this making sense to anyone else?  If so, can you explain it
>>> better than I can :)?
>>>
>>>   
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to 
>> share your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________ 
>> <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________>
>> Astlinux-users mailing list
>> Ast...@li... 
>> <mailto:Ast...@li...>
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to 
>> pa...@kr... <mailto:pa...@kr...>.
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Lonnie A. <li...@lo...>]

Bryce,

> When the SIP device connects to its outside host, its' identified =20
> as being at 123.45.67.8:5060 (source address), however 123.45.67.8 =20
> is the IP of the Astlinux router and port 5060 is the port Asterisk =20=

> is already listening on.

Isn't iptables smart enough to realize that the udp/external 5060 nat =20=

table is in use,  and automatically assign a different external port =20
of the 2'nd SIP device?

Lonnie

On Mar 5, 2007, at 2:27 PM, Bryce Chidester wrote:

> It makes sense to me, but nonetheless here's my translation/=20
> simplification.
>
> If a router is running Asterisk, with SIP enabled, then port 5060 =20
> (and whatever RTP range is defined) are claimed by Asterisk. =20
> Generally, this does not present a problem, except until you have =20
> to try and NAT another SIP device behind it. In order for the SIP =20
> device to communicate to the outside (technically, for the outside =20
> to talk to it), there must be a port forward in place on the =20
> router. This is where the conflict occurs.
> When the SIP device connects to its outside host, its' identified =20
> as being at 123.45.67.8:5060 (source address), however 123.45.67.8 =20
> is the IP of the Astlinux router and port 5060 is the port Asterisk =20=

> is already listening on. When the remote service tries to call the =20
> SIP device, it actually connects to Asterisk and the call won't go =20
> through.
> As for the "fix" with MASQPORTS, you're only forwarding the RTP =20
> data so audio will go through without a hitch, however this does =20
> not solve the conflicting claims for port 5060.
> Simplest fix is to set your SIP phone, or Asterisk, to use a =20
> different port for SIP than 5060 (I think 5082 is another common =20
> choice).
> Regards,
> Bryce Chidester
> Rhino Equipment Corp.
> br...@rh...
> Tel: +1 (480) 940-1826 x6351
> Fax: +1 (480) 961-1826
> FWD: 633686 x6351
> IP: asterisk.rhinoequipment.com x6351
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  =20
> PROPRIETARY MATERIAL and is thus for use only by the intended  =20
> recipient. If you received this in error, please contact the =20
> sender  and delete the email and its attachments from all computers.
>
>
> Kristian Kielhofner wrote:
>> On 3/5/07, Lonnie Abelbeck <li...@lo...> wrote:
>>
>>> Kristian,
>>>
>>> I think I understand you, maybe I am wrong?
>>>
>>> But, I will try one more time.
>>>
>>> I'm no iptables guru, but this might be what I am suggesting:
>>> iptables -t nat -A PREROUTING -i sis1 -p udp =96dport 5060 -j DNAT =
=96to
>>> 192.168.1.10:5060
>>>
>>> This puts an inbound, external udp/5060 rule in the NAT table
>>> pointing to your asterisk box.  If a different SIP device now tries
>>> to register out, it will not be given the external/public of 5060
>>> since it is reserved by the NAT rule above.  correct?
>>>
>>> Of course, if you want to receive inbound SIP to asterisk, you would
>>> also have to add something like:
>>> iptables -A FORWARD --destination 192.168.1.10 -p udp --dport =20
>>> 5060 -j
>>> ACCEPT
>>>
>>> Is this clear?
>>>
>>> Lonnie
>>>
>>>
>> Lonnie,
>>
>>   I started on FreeBSD/OpenBSD and I understand ipfw/pf rules quite
>> well.  I appreciate the   translation to iptables for the other
>> readers :).
>>
>>   We are talking about two different things.  You want to put an
>> Asterisk box behind another Linux/iptables router (that isn't running
>> Asterisk) and translate traffic on the Linux/iptables box.
>>
>>   I want to put a SIP device behind a Linux/iptables router that is
>> running Asterisk.
>>
>>   This causes a problem.
>>
>>   The iptables MASQUERADE & SNAT (not DNAT) iptables code (by =20
>> default)
>> will assign port 5060 on the external interface as the port to be =20
>> used
>> for PAT with the SIP device BEHIND the Linux router.  This will make
>> port 5060 on the Linux/iptables/Asterisk box to be inaccessible via
>> SIP because incoming traffic to the external interface on port 5060
>> will be translated and routed to the SIP device behind nat because of
>> the iptables MASQ state.
>>
>>   Using --to-ports forces the MASQ/SNAT code to only use ports in the
>> defined range - not the port used by the device inside the NAT.
>>
>>   Is this making sense to anyone else?  If so, can you explain it
>> better than I can :)?
>>
>>
> ----------------------------------------------------------------------=20=

> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV____________________________=
____=20
> _______________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to =20=

> pa...@kr....

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Bryce C. <br...@rh...>]

It makes sense to me, but nonetheless here's my translation/simplification.

If a router is running Asterisk, with SIP enabled, then port 5060 (and 
whatever RTP range is defined) are claimed by Asterisk. Generally, this 
does not present a problem, except until you have to try and NAT another 
SIP device behind it. In order for the SIP device to communicate to the 
outside (technically, for the outside to talk to it), there must be a 
port forward in place on the router. This is where the conflict occurs.
When the SIP device connects to its outside host, its' identified as 
being at 123.45.67.8:5060 (source address), however 123.45.67.8 is the 
IP of the Astlinux router and port 5060 is the port Asterisk is already 
listening on. When the remote service tries to call the SIP device, it 
actually connects to Asterisk and the call won't go through.
As for the "fix" with MASQPORTS, you're only forwarding the RTP data so 
audio will go through without a hitch, however this does not solve the 
conflicting claims for port 5060.
Simplest fix is to set your SIP phone, or Asterisk, to use a different 
port for SIP than 5060 (I think 5082 is another common choice).

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Kristian Kielhofner wrote:
> On 3/5/07, Lonnie Abelbeck <li...@lo...> wrote:
>   
>> Kristian,
>>
>> I think I understand you, maybe I am wrong? <smile>
>>
>> But, I will try one more time.
>>
>> I'm no iptables guru, but this might be what I am suggesting:
>> iptables -t nat -A PREROUTING -i sis1 -p udp –dport 5060 -j DNAT –to
>> 192.168.1.10:5060
>>
>> This puts an inbound, external udp/5060 rule in the NAT table
>> pointing to your asterisk box.  If a different SIP device now tries
>> to register out, it will not be given the external/public of 5060
>> since it is reserved by the NAT rule above.  correct?
>>
>> Of course, if you want to receive inbound SIP to asterisk, you would
>> also have to add something like:
>> iptables -A FORWARD --destination 192.168.1.10 -p udp --dport 5060 -j
>> ACCEPT
>>
>> Is this clear?
>>
>> Lonnie
>>
>>     
>
> Lonnie,
>
>   I started on FreeBSD/OpenBSD and I understand ipfw/pf rules quite
> well.  I appreciate the   translation to iptables for the other
> readers :).
>
>   We are talking about two different things.  You want to put an
> Asterisk box behind another Linux/iptables router (that isn't running
> Asterisk) and translate traffic on the Linux/iptables box.
>
>   I want to put a SIP device behind a Linux/iptables router that is
> running Asterisk.
>
>   This causes a problem.
>
>   The iptables MASQUERADE & SNAT (not DNAT) iptables code (by default)
> will assign port 5060 on the external interface as the port to be used
> for PAT with the SIP device BEHIND the Linux router.  This will make
> port 5060 on the Linux/iptables/Asterisk box to be inaccessible via
> SIP because incoming traffic to the external interface on port 5060
> will be translated and routed to the SIP device behind nat because of
> the iptables MASQ state.
>
>   Using --to-ports forces the MASQ/SNAT code to only use ports in the
> defined range - not the port used by the device inside the NAT.
>
>   Is this making sense to anyone else?  If so, can you explain it
> better than I can :)?
>
>   

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Kristian K. <kri...@gm...>]

On 3/5/07, Lonnie Abelbeck <li...@lo...> wrote:
> Kristian,
>
> I think I understand you, maybe I am wrong? <smile>
>
> But, I will try one more time.
>
> I'm no iptables guru, but this might be what I am suggesting:
> iptables -t nat -A PREROUTING -i sis1 -p udp =96dport 5060 -j DNAT =96to
> 192.168.1.10:5060
>
> This puts an inbound, external udp/5060 rule in the NAT table
> pointing to your asterisk box.  If a different SIP device now tries
> to register out, it will not be given the external/public of 5060
> since it is reserved by the NAT rule above.  correct?
>
> Of course, if you want to receive inbound SIP to asterisk, you would
> also have to add something like:
> iptables -A FORWARD --destination 192.168.1.10 -p udp --dport 5060 -j
> ACCEPT
>
> Is this clear?
>
> Lonnie
>

Lonnie,

  I started on FreeBSD/OpenBSD and I understand ipfw/pf rules quite
well.  I appreciate the   translation to iptables for the other
readers :).

  We are talking about two different things.  You want to put an
Asterisk box behind another Linux/iptables router (that isn't running
Asterisk) and translate traffic on the Linux/iptables box.

  I want to put a SIP device behind a Linux/iptables router that is
running Asterisk.

  This causes a problem.

  The iptables MASQUERADE & SNAT (not DNAT) iptables code (by default)
will assign port 5060 on the external interface as the port to be used
for PAT with the SIP device BEHIND the Linux router.  This will make
port 5060 on the Linux/iptables/Asterisk box to be inaccessible via
SIP because incoming traffic to the external interface on port 5060
will be translated and routed to the SIP device behind nat because of
the iptables MASQ state.

  Using --to-ports forces the MASQ/SNAT code to only use ports in the
defined range - not the port used by the device inside the NAT.

  Is this making sense to anyone else?  If so, can you explain it
better than I can :)?

--=20
Kristian Kielhofner

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Lonnie A. <li...@lo...>]

Kristian,

I think I understand you, maybe I am wrong? <smile>

But, I will try one more time.

I'm no iptables guru, but this might be what I am suggesting:
iptables -t nat -A PREROUTING -i sis1 -p udp =96dport 5060 -j DNAT =96to =
=20
192.168.1.10:5060

This puts an inbound, external udp/5060 rule in the NAT table =20
pointing to your asterisk box.  If a different SIP device now tries =20
to register out, it will not be given the external/public of 5060 =20
since it is reserved by the NAT rule above.  correct?

Of course, if you want to receive inbound SIP to asterisk, you would =20
also have to add something like:
iptables -A FORWARD --destination 192.168.1.10 -p udp --dport 5060 -j =20=

ACCEPT

Is this clear?

Lonnie

On Mar 5, 2007, at 10:01 AM, Kristian Kielhofner wrote:

> On 3/2/07, Lonnie Abelbeck <li...@lo...> wrote:
>>
>> On Mar 2, 2007, at 3:12 PM, Kristian Kielhofner wrote:
>>
>>>   In this scenario, the NAT code in the Linux kernel will attempt to
>>> use port 5060 on the external interface of the AstLinux machine.  It
>>> does this for three reasons:
>>>
>>> 1)  5060 is above 1023
>>> 2)  It defaults to using the same port that is used on the internal
>>> side (if possible)
>>> 3)  It doesn't know that there is something listening on that port
>>> locally.
>>
>> Kristian,
>>
>> I don't understand your #3.
>> If you want your asterisk box to 'listen' on 5060, you have to port
>> forward 5060 to your asterisk box (192.168.1.10)
>>
>> using "ipnat" on FreeBSD
>> rdr sis1 0/0 port 5060 -> 192.168.1.10 port 5060 udp
>>
>> This would make port 5060 on the WAN interface unavailable, when a
>> SIP phone registered out the WAN, correct?
>>
>> I instincts say your suggested changes are unnecessary,
>>
>> but then again, I use m0n0wall. <smile>
>>
>> Lonnie
>>
>
> Lonnie,
>
>   I think it is possible that you are misunderstanding me.
>
>   Basically, if you use AstLinux in router mode and register a
> DIFFERENT SIP device behind it (nothing to do with Asterisk at all),
> you will block access to port 5060 because the Linux kernel will (by
> default) PAT using the same external port number as the device.
>
>   Not only is m0n0 FreeBSD based (I don't know what the PAT specifics
> are there), it doesn't run Asterisk so it doesn't have this problem.
>
> --=20
> Kristian Kielhofner
>
> ----------------------------------------------------------------------=20=

> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to =20=

> pa...@kr....
>

Re: [Astlinux-users] trunk compile error stuff

[Kristian K. <kri...@gm...>]

On 3/4/07, ast...@el... <ast...@el...> wrote:
>
> Actually, this has been a recurring problem for me before today. That's
> why I mentioned it.
>

asterisk,

  This is why I operate files.astlinux.org.  I managed to grab a copy
of both asterisk and zaptel.  I am syncing my local files with
files.astlinux.org and it should be available there shortly.


-- 
Kristian Kielhofner

Re: [Astlinux-users] trunk compile error - flite

[Kristian K. <kri...@gm...>]

On 3/4/07, ast...@el... <ast...@el...> wrote:
> Seems like flite is unhappy. This is being compiled with the ALSA stuff.
>
>
> /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
> -Os -pipe  -Wall    -o ../bin/flite_time flite_time_main.o
> -L../build/i386-linux-gnu/lib -lflite_cmu_time_awb -lflite_usenglish
> -lflite_cmulex -L../build/i386-linux-gnu/lib -lflite -lm
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_open':
> audio.c:(.text+0x2b): undefined reference to `audio_open_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_write':
> audio.c:(.text+0x3ab): undefined reference to `audio_write_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_close':
> audio.c:(.text+0x88): undefined reference to `audio_close_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_drain':
> audio.c:(.text+0x3db): undefined reference to `audio_drain_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_flush':
> audio.c:(.text+0x3e4): undefined reference to `audio_flush_oss'
> collect2: ld returned 1 exit status
> make[2]: *** [../bin/flite] Error 1
> make[2]: *** Waiting for unfinished jobs....
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_open':
> audio.c:(.text+0x2b): undefined reference to `audio_open_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_write':
> audio.c:(.text+0x3ab): undefined reference to `audio_write_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_close':
> audio.c:(.text+0x88): undefined reference to `audio_close_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_drain':
> audio.c:(.text+0x3db): undefined reference to `audio_drain_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_flush':
> audio.c:(.text+0x3e4): undefined reference to `audio_flush_oss'
> collect2: ld returned 1 exit status
> make[2]: *** [../bin/flite_time] Error 1
> make[1]: *** [build/i386-linux-gnu/obj//.make_build_dirs] Error 2
> make[1]: Leaving directory
> `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/flite-1.3-release'
> make: ***
> [/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/flite-1.3-release/bin/flite]
> Error 2
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>

asterisk,

  flite did work at one time.  I know because I used it!

  Somewhere along the lines it got broken...

  If a package is not built by default it is not routinely tested.
Ideally we would have a proper testing mechanism in place to
automatically build, test, and report on various packages.
Unfortunately at this time there just aren't enough resources to do
this.

    Plus, even if it did compile properly, you are attempting to use
it in an unsupported configuration (enabled with ALSA, which is
totally unsupported itself).

  What we should probably do is enable a configuration mechanism
similar to the Linux kernel - make a menu option for
EXPERIMENTAL/UNSUPPORTED code and only enable those packages when it
is selected.  I'll talk to Darrick about this.

  As far as the actual error here, my guess is that alsa is seeing
some OSS/ALSA like headers when compiling and attempting to link to
them during linking.  Unfortunately, the various .a/.so's for either
lib are not there...
-- 
Kristian Kielhofner

[Astlinux-users] Asterisk 1.4.1 plans?

[Sebastian A. <sp...@sy...>]

With the release on Saturday of Asterisk 1.4.1 (showing some maturity now
for this branch), as there any plans to switch to using the 1.4 branch of
Asterisk in trunk (future 0.5 branch)?

Has anyone used Asterisk 1.4.x with AstLinux yet (either 0.4 branch or
trunk)? Did you have any issues with it?

Kind regards,

Sebastian 

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[Kristian K. <kri...@gm...>]

On 3/2/07, Lonnie Abelbeck <li...@lo...> wrote:
>
> On Mar 2, 2007, at 3:12 PM, Kristian Kielhofner wrote:
>
> >   In this scenario, the NAT code in the Linux kernel will attempt to
> > use port 5060 on the external interface of the AstLinux machine.  It
> > does this for three reasons:
> >
> > 1)  5060 is above 1023
> > 2)  It defaults to using the same port that is used on the internal
> > side (if possible)
> > 3)  It doesn't know that there is something listening on that port
> > locally.
>
> Kristian,
>
> I don't understand your #3.
> If you want your asterisk box to 'listen' on 5060, you have to port
> forward 5060 to your asterisk box (192.168.1.10)
>
> using "ipnat" on FreeBSD
> rdr sis1 0/0 port 5060 -> 192.168.1.10 port 5060 udp
>
> This would make port 5060 on the WAN interface unavailable, when a
> SIP phone registered out the WAN, correct?
>
> I instincts say your suggested changes are unnecessary,
>
> but then again, I use m0n0wall. <smile>
>
> Lonnie
>

Lonnie,

  I think it is possible that you are misunderstanding me.

  Basically, if you use AstLinux in router mode and register a
DIFFERENT SIP device behind it (nothing to do with Asterisk at all),
you will block access to port 5060 because the Linux kernel will (by
default) PAT using the same external port number as the device.

  Not only is m0n0 FreeBSD based (I don't know what the PAT specifics
are there), it doesn't run Asterisk so it doesn't have this problem.

-- 
Kristian Kielhofner

Re: [Astlinux-users] sqlite cdr

[Darrick H. <dha...@dj...>]

walter trucci wrote:
> Thanks a lot. I see that maybe there is some errors on sqlite 
> compiling, when I run sqlite3 there are some errors.
Please provide the errors so I can correct them.  sqlite was added as a 
request, but the developers currently don't use it.  It appears to 
compile cleanly.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com