[LAU] Traverso 0.49.2

[david]

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 at 100jamz.com> 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.

-- 
David
gnome at hawaii.rr.com
authenticity, honesty, community