Re: [LAU] Traverso 0.49.2

On Fri, Aug 13, 2010 at 7:42 PM, david <gnome@email-addr-hidden> wrote:

> Bengt Gördén wrote:
>
>> torsdag 12 augusti 2010 22:39:39 skrev Jeremy:
>>
>>> On Thu, Aug 12, 2010 at 2:43 PM, drew Roberts <zotz@email-addr-hidden> wrote:
>>>
>>>> On Thursday 12 August 2010 02:00:22 Remon Sijrier wrote:
>>>>
>>>>> Your website seems to be down for me.
>>>>>>
>>>>> Works for me, can anyone else confirm this problem?
>>>>>
>>>> Just checked. Up for me.
>>>>
>>>> Remon
>>>>>
>>>> drew
>>>> _______________________________________________
>>>>
>>> This is very strange. I've tried several days in a row and the website
>>> is
>>>
>>> still inaccessible to me. Every other website I've visited works fine.
>>> This is across multiple computers.
>>>
>>> $ wget http://traverso-daw.org
>>> --2010-08-12 20:37:48-- http://traverso-daw.org/
>>> Resolving traverso-daw.org... 85.10.194.156
>>> Connecting to traverso-daw.org|85.10.194.156|:80... failed: No route to
>>> host.
>>>
>>
>> "No route to host" means that your computer/router doesn't know how to
>> reach the destination. Normally a desktop uses "default gateway" and that
>> points upstream. This could be set to wrong address.
>>
>> Try this to see what the routing table looks like:
>> ip route
>>
>> or this for older boxes
>> route -n
>> netstat -rn
>>
>> It should reveal your routing table.
>>
>> If you're missing the default gw you can add it like this
>>
>> ip route add default via <ip-number to gateway>
>>
>> or
>> route add default gw <ip-number to gateway>
>>
>>
>> There are actually several ways to inject routes to not be able to reach a
>> destination. This for example.
>> ip route add prohibit <ip-number>
>>
>> iptables might also be a source of problem.
>>
>> Feel free to contact me offline if you think this is OT.
>>
>
> Or your ISP's upstream provider might be having a spat with the ISP that
> provides pipes to the Traverso site.
>
> I think that generally if your routing is messed up, it would effect more
> than just one particular site.
>

Yeah, that's why it's so strange, because *no other website* I try to visit
has these problems. I know that I'm at least connecting to my router and
then my modem. I know verizon does some wierd shit, like redirecting
missed dns lookups to their search page...

> --
> David
> gnome@email-addr-hidden
> authenticity, honesty, community
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@email-addr-hidden
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Sat Aug 14 12:15:02 2010