Ron Byer Jr. wrote:
> 32 bit.
>
> I will do the " cp astlinux.config to .config then do make oldconfig", on
> the next iteration, later tonight or tomorrow morning.
>
> H. I did do that last when I pulled down 214x. But I didn't do it when I
> started the 2155 build.
Something almost has t
Darrick Hartman [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2008 5:13 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
32 or 64 bit?
Can you cp astlinux.config to .config then do make oldconfig?
On Mon, 8 Dec 2008 14:52:24 -0600, Ron Byer Jr. w
utions, Inc.
> +1.732.786.8830 x120
>
>
> -Original Message-
> From: Darrick Hartman [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 08, 2008 3:00 PM
> To: AstLinux Users Mailing List
> Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
>
> Philip,
thout some questions, I'm sure).
rb
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Darrick Hartman [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2008 3:00 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixu
nmental (i.e. my box), but
>> that's still the leading suspect, to be sure.
>>
>>
>> Ron Byer Jr.
>> NetWeave Integrated Solutions, Inc.
>> +1.732.786.8830 x120
>>
>>
>> -Original Message-
>> From: Darrick Hartman [m
tal (i.e. my box), but
> that's still the leading suspect, to be sure.
>
>
> Ron Byer Jr.
> NetWeave Integrated Solutions, Inc.
> +1.732.786.8830 x120
>
>
> -Original Message-
> From: Darrick Hartman [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 07,
leading suspect, to be sure.
>
>
> Ron Byer Jr.
> NetWeave Integrated Solutions, Inc.
> +1.732.786.8830 x120
>
>
> -Original Message-
> From: Darrick Hartman [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 07, 2008 7:47 PM
> To: AstLinux Users Mailing
at's still the leading suspect, to be sure.
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Darrick Hartman [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 07, 2008 7:47 PM
To: AstLinux Users Mailing List
Subject: Re: [Ast
Philip Prindeville wrote:
> Joy?
>
> Or no joy?
>
>
> Ron Byer Jr. wrote:
>> Sorry. I don't know how that came out to be 2041. Twice, no less. Intended
>> to say 2136. I think the latest was 2140 when I pulled it, and I scrambled
>> that to 2041.
Ron,
Please update to the lastest 0.6 svn and
, Inc.
+1.732.786.8830 x120
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 3:05 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Why 2041?
Ron Byer Jr. wrote:
#1)
I'm building 2041, which
nc.
> +1.732.786.8830 x120
>
>
> -Original Message-
> From: Philip Prindeville [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 05, 2008 3:05 PM
> To: AstLinux Users Mailing List
> Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
>
> Why 2041?
>
>
>
ville [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 3:05 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Why 2041?
Ron Byer Jr. wrote:
> #1)
> I'm building 2041, which will take a while.
>
> #2)
> Regarding modprobe -l mis-
> Sent: Thursday, December 04, 2008 6:55 PM
> To: AstLinux Users Mailing List
> Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
>
> We'll talk about 2131 off-line... :-)
>
> Pick up #2133. This might fix your issue.
>
> -Philip
>
>
> Darrick Hartman
k-workaround at
present that will keep me quiet and off the list .
rb
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 6:55 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
We'll talk
> close(4)= 0
>>>
>>> setsockopt(17, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
>>>
>>> bind(17, {sa_family=AF_INET6, sin6_port=htons(123), inet_pton(AF_INET6,
>>> "::", &s
>>>
ailing List
>> Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
>>
>>
>>
>> I don't have access to my net5501 AstLinux box from here. I will get
>>
>> around to reconfiguring my VPN sometime, I promise. :)
>>
>>
>>
>> So t
f_conntrack_sane.ko
description:SANE connection tracking helper
author: Michal Schmidt <[EMAIL PROTECTED]>
license:GPL
srcversion: AE4A999ADC6D20AC4B75C43
depends:nf_conntrack
vermagic: 2.6.25.14-69.fc8 SMP mod_unload 686 4KSTACKS
parm: ports
--Original Message-
From: Darrick Hartman [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 5:00 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Ron,
I've confirmed two things. If ipv6 is NOT enabled, ntpd runs fine.
(restart did not wor
= 0
>
> close(4) = 0
>
> getpid()= 1631
>
> write(3, "<27>Mar 3 14:36:42 ntpd[1631]: "..., 120) = 120
>
> rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
>
> _exit(1)
On 12/4/08, Philip Prindeville <[EMAIL PROTECTED]> wrote:
>
>
> Not so. See my earlier posting. IPv6 is big in Asia and France. It's
> soon to be big in Latin America:
>
> http://www.lacnic.net/en/eventos/ipv6
>
OT but why not.
There are currently just over 2,000 IPv6 routes announced in the
tached
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Tod Fitch [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 3:47 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
I d
Kristian Kielhofner wrote:
> On 12/4/08, Darrick Hartman <[EMAIL PROTECTED]> wrote:
> ..snip..
>
>> My preference is to remove ipv6 from the 0.6 branch if this cannot be
>> resolved quickly. ipv6 is not wide spread at this point. The 0.6.3
>> release will happen after Asterisk 1.4.23 is rel
, Inc.
+1.732.786.8830 x120
-Original Message-
From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 2:11 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
On Dec 4, 2008, at 12:38 PM, Ron Byer Jr. wrote:
Lonnie, et al:
Do you hav
ipv6
>> fi
>> modprobe -l ipv6
>>
>>
>> It appears that ipv6 is pre-loaded prior to this, and manages to avoid
>> unloading it. the modprobe -l ipv6 before and after both report that is it
>> loaded.
>>
>> rb
>>
>>
>>
&g
g ipv6..."
> modprobe -r ipv6
> fi
> modprobe -l ipv6
>
>
> It appears that ipv6 is pre-loaded prior to this, and manages to avoid
> unloading it. the modprobe -l ipv6 before and after both report that is it
> loaded.
>
> rb
>
>
>
>
&g
No change. Still fails on the ipv6 bind.
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 2:11 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users
On 12/4/08, Darrick Hartman <[EMAIL PROTECTED]> wrote:
..snip..
>
> My preference is to remove ipv6 from the 0.6 branch if this cannot be
> resolved quickly. ipv6 is not wide spread at this point. The 0.6.3
> release will happen after Asterisk 1.4.23 is released (mostly because it
> addresses
On 12/4/08, Lonnie Abelbeck <[EMAIL PROTECTED]> wrote:
> If I remember correctly, Kristian was playing with IPv6 and added it.
>
> http://astlinux.svn.sourceforge.net/viewvc/astlinux?view=rev&revision=1829
>
> I agree with Darrick, this should be removed from the 0.6 branch.
>
>
> Lonnie
>
Yes,
On Dec 4, 2008, at 12:38 PM, Ron Byer Jr. wrote:
> Lonnie, et al:
>
> Do you have the NTP startup issue ? I'm stumped by why this doesn't
> have
> more pervasive impact. I'm always ready to find out that it's a
> cockpit
> error on my part.
No problem here, but I run my own NTP server with
t;
>>modprobe ipv6
>>else
>> echo "removing ipv6..."
>>modprobe -r ipv6
>> fi
>> modprobe -l ipv6
>>
>>
>> It appears that ipv6 is pre-loaded prior to this, and manages to
>> avoid
>&
; It appears that ipv6 is pre-loaded prior to this, and manages to avoid
> unloading it. the modprobe -l ipv6 before and after both report that is it
> loaded.
>
> rb
>
>
>
>
> -----Original Message-
> From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED]
>
d
unloading it. the modprobe -l ipv6 before and after both report that is it
loaded.
rb
-Original Message-
From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 12:11 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
On Dec 4, 2008, at 9:11 AM, Ron Byer Jr. wrote:
> Philip,
>
> Thanks for the suggestion. I did the modprobe ipv6 and it had little/
> no
> effect. Still failing on the bind (AF_INET6) call.
>
> I guess there are two mysteries here, though I would be happy to
> solve only
> one of them :: why i
Sent: Wednesday, December 03, 2008 9:32 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Ron Byer Jr. wrote:
>
> Additional info:
>
> ##Master NTP server(s). This is the NTP server that AstLinux will sync
> against
>
> ##upon bootup. It i
Ron Byer Jr. wrote:
>
> Additional info:
>
> ##Master NTP server(s). This is the NTP server that AstLinux will sync
> against
>
> ##upon bootup. It is also the server that the running ntpd process
> will use
>
> ##to maintain that time sync.
>
> NTPSERVS="us.pool.ntp.org"
>
> #NTPSERVS="europe.po
Additional info:
##Master NTP server(s). This is the NTP server that AstLinux will sync
against
##upon bootup. It is also the server that the running ntpd process will use
##to maintain that time sync.
NTPSERVS="us.pool.ntp.org"
#NTPSERVS="europe.pool.ntp.org"
>From rc.conf.
And us
I updated to 0.6.2 a week or so ago (on my net5501), and just discovered
today that my date is all screwed up. I had been running 0.6-2082 prior to
that, so I went back to that version, with no apparent changes. So, I've
been less than observant for some time now. In my defense, I have a box for
Tod Fitch wrote:
> On Nov 29, 2008, at 8:33 AM, Philip Prindeville wrote:
>
>> Which firewall are you using, and is UDP port 123 open? If you're using
>> Arno's firewall, then set OPEN_UDP="123" in
>> /etc/arno-iptables-firewall/firewall.conf ...
>>
>> Also, did you try setting your hardware cloc
>
>Which firewall are you using, and is UDP port 123 open? If you're using
>Arno's firewall, then set OPEN_UDP="123" in
>/etc/arno-iptables-firewall/firewall.conf ...
>
>Also, did you try setting your hardware clock to the correct time? You
>can set the time manually with "date", and then run "hw
On Nov 29, 2008, at 8:33 AM, Philip Prindeville wrote:
Which firewall are you using, and is UDP port 123 open? If you're
using
Arno's firewall, then set OPEN_UDP="123" in
/etc/arno-iptables-firewall/firewall.conf ...
Also, did you try setting your hardware clock to the correct time?
You
c
Tod Fitch wrote:
> On Nov 28, 2008, at 11:10 AM, Michael Keuter wrote:
>>>
>>> For AstLinux v0.6.2, I was attempting to setup my box as a
>>> firewall/router. Ran into troubles (worry about that later) then
>>> reconfigured as best I could back to having only an EXT_IF with
>>> static IP to resume
On Nov 28, 2008, at 10:19 AM, Philip Prindeville wrote:
Tod Fitch wrote:
For AstLinux v0.6.2, I was attempting to setup my box as a
firewall/router. Ran into troubles (worry about that later) then
reconfigured as best I could back to having only an EXT_IF with
static
IP to resume use as only
On Nov 28, 2008, at 11:10 AM, Michael Keuter wrote:
For AstLinux v0.6.2, I was attempting to setup my box as a
firewall/router. Ran into troubles (worry about that later) then
reconfigured as best I could back to having only an EXT_IF with
static IP to resume use as only a Asterisk server.
But
I don't see ntpdate or the other tools I am used to working with in
the path, so am a little bit slow on this. Any ideas?
Thanks!
Hi Tod,
just for info, are you using the geni386-image?
Because I also had this ntp problems in the past (starting with a
runnix based Astlinux) but only on geni38
>Content-Type: multipart/signed; boundary=Apple-Mail-1-476342321; micalg=sha1;
> protocol="application/pkcs7-signature"
>
>For AstLinux v0.6.2, I was attempting to setup my box as a
>firewall/router. Ran into troubles (worry about that later) then
>reconfigured as best I could back to havin
Tod Fitch wrote:
> For AstLinux v0.6.2, I was attempting to setup my box as a
> firewall/router. Ran into troubles (worry about that later) then
> reconfigured as best I could back to having only an EXT_IF with static
> IP to resume use as only a Asterisk server.
>
> But now the NTP setting does
For AstLinux v0.6.2, I was attempting to setup my box as a firewall/
router. Ran into troubles (worry about that later) then reconfigured
as best I could back to having only an EXT_IF with static IP to resume
use as only a Asterisk server.
But now the NTP setting does not appear to work. I h
47 matches
Mail list logo
