I've tested some connections I have access to with a pretty interesting
result:
- Two BB accesses within AS8404, one got access to [1], the other one
not!
- One ADSL behind AS21494 works fine.
- Upstream traffic over AS13030 works fine.
To me it seems like a large IP block on Akamai spread over s
ok, didn't think of that, makes sense of course...
so it looks like some sort of problem between init7 and akamai after all
init7 is looking into it at this moment.
regards,
mike
--
Mike Kellenberger [EMAIL PROTECTED]
Escapenet - the Web Company Tel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| so it looks like some sort of problem between init7 and
| akamai after all
DNS lookups for akamaized content (example used: members.spamcop.net)
from a DNS server behind an Init7 DSL line (213.144.132.248/29) returns
80.67.84.74 and 80.67.84.83, bo
On Tue, 2008-01-29 at 01:05 -0800, Christian Jouas wrote:
> 8404 has some Akamai servers inhouse
This is it!
Changed nameserver to AS8404 nameservers, Sites had been available
again. So it seems that Akamai traffic is not allowed to cross AS8404
but has to be loaded from the Akamai servers within
>
> could be some kind of dns issue as well
>
[...]
>
> cleared all caches on our cache-only nameservers; not using
> forwarders; but still always get the same results back
>
That's exactly how the Akamai DNS is supposed to work. You'll always get
different results from different AS's as the A
8404 has some Akamai servers inhouse
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Kamm
Sent: mardi, 29. janvier 2008 09:49
To: [EMAIL PROTECTED]
Subject: Re: AW: [swinog] Large IP Block at Akamai?
I've tested some connections I have access to wi
could be some kind of dns issue as well
nslookup from here:
nslookup i.dell.com
Non-authoritative answer:
Name:a569.g.akamai.net
Addresses: 80.67.84.75, 80.67.84.74
Aliases: i.dell.com, img.dell-cidr.akadns.net
img.dell.com.edgesuite.net
nslookup from ip-plus or any other onli
On Tue, 2008-01-29 at 01:05 -0800, Christian Jouas wrote:
> 8404 has some Akamai servers inhouse
And we are using our own name servers which are not behind 8404 access
network. That could be the reason. Stdby...
- Dan
___
swinog mailing list
swinog@li
Andre Keller wrote:
> Hi swinoggers
>
> I'm searching for a possibility to set the originator in sms_client...
> (somewhere in ucp.c i asume).
>
> I saw in the mailinglist of smsclient, that Per Jessen wrote about
> that in August 2004. Are these patches still around?
Yep, I've still got it som
I will give it a try.
Works perfect also with 2.0.9a
thank you again
Regards André
___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Andre,
it's a very simple patch:
http://jessen.ch/files/smsclient-originator-patch
Just change the "from" to whatever number you need.
/Per Jessen, Herrliberg
Thank you very much. I will give it a try.
Regards André
___
swinog mailing lis
Per Jessen wrote:
> it's a very simple patch:
> http://jessen.ch/files/smsclient-originator-patch
Correction:
http://jessen.ch/patches/smsclient-originator-patch
/Per Jessen, Herrliberg
--
http://www.spamchek.com/ - your spam is our business.
___
Hi swinoggers
I'm searching for a possibility to set the originator in sms_client...
(somewhere in ucp.c i asume).
I saw in the mailinglist of smsclient, that Per Jessen wrote about that
in August 2004. Are these patches still around?
regards André
__
Per Jessen wrote:
> Andre Keller wrote:
>
>> Hi swinoggers
>>
>> I'm searching for a possibility to set the originator in
>> sms_client... (somewhere in ucp.c i asume).
>>
>> I saw in the mailinglist of smsclient, that Per Jessen wrote about
>> that in August 2004. Are these patches still aroun
14 matches
Mail list logo
