10 Aug
2010
10 Aug
'10
7:59 p.m.
Available for download here: http://traverso-daw.org/download.html
Change log can be viewed here: http://traverso-daw.org/changelogs.html
Feedback and praise please here: http://traverso-daw.org/forum/index.php
Don't forget to: http://traverso-daw.org/Support.html
The T-team
12 Aug
12 Aug
7:10 a.m.
On Tue, Aug 10, 2010 at 5:59 PM, Remon Sijrier <remon(a)traverso-daw.org>wrote;wrote:
Available for download here:
http://traverso-daw.org/download.html
Change log can be viewed here: http://traverso-daw.org/changelogs.html
Feedback and praise please here: http://traverso-daw.org/forum/index.php
Don't forget to: http://traverso-daw.org/Support.html
The T-team
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
Your website seems to be down for me.
Jeremy
10:03 a.m.
Excerpts from Remon Sijrier's message of 2010-08-12 08:00:22 +0200:
Works here too.
--
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
Your website
seems to be down for me.
Works for me, can anyone else confirm this problem?
Remon 
10:40 p.m.
On Thu, Aug 12, 2010 at 2:43 PM, drew Roberts <zotz(a)100jamz.com> wrote:
On Thursday 12 August 2010 02:00:22 Remon Sijrier
wrote:
Just checked. Up for me.
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.
(wgetting any other website works fine).
Jeremy
Your
website seems to be down for me.
Works for me, can anyone else confirm this problem?
Remon
drew
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
13 Aug
13 Aug
12:31 a.m.
On 2010-08-12 22:39, Jeremy wrote:
Strange indeed, works just fine here:
atte@vestbjerg:~/Desktop/delme$ wget http://traverso-daw.org
--2010-08-13 00:30:35-- http://traverso-daw.org/
Resolving traverso-daw.org... 85.10.194.156
Connecting to traverso-daw.org|85.10.194.156|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'
[ <=> ] 9.343 --.-K/s in
0,04s
2010-08-13 00:30:40 (239 KB/s) - `index.html' saved [9343]
--
Atte
http://atte.dk http://modlys.dk
10:09 a.m.
torsdag 12 augusti 2010 22:39:39 skrev Jeremy:
On Thu, Aug 12, 2010 at 2:43 PM, drew Roberts
<zotz(a)100jamz.com> wrote:
"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.
regards,
/bengan
On Thursday 12 August 2010 02:00:22 Remon Sijrier
wrote:
Just checked. Up for me.
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. Your
website seems to be down for me.
Works for me, can anyone else confirm this problem? Remon
drew
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
5:09 p.m.
checked here with wget here as well, also works fine.
I hope the suggestion offered by bengan gives a clue what is going on!
If you still can't access the website, and you want to try out the 0.49.2
release, just send me a note then I can send the tarball by mail to you
(and/or a recent git checkout if you're curious what is being worked on for
the next release)
Remon
7:52 p.m.
On Fri, 13 Aug 2010 03:09:15 -0500, Bengt Gördén <bengan(a)bag.org> wrote:
"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.
It's amazing his email got through at all if his system is that badly
configured :P
--Steve
9:42 p.m.
Bengt Gördén wrote:
torsdag 12 augusti 2010 22:39:39 skrev Jeremy:
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(a)hawaii.rr.com
authenticity, honesty, community
On Thu, Aug 12, 2010 at 2:43 PM, drew Roberts
<zotz(a)100jamz.com> wrote:
"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. On Thursday 12 August 2010 02:00:22 Remon Sijrier
wrote:
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. > Your website seems to be down for me.
Works for me, can anyone else confirm this problem?
Just checked. Up for me.
Remon
drew
_______________________________________________
14 Aug
14 Aug
8:55 a.m.
On Fri, Aug 13, 2010 at 7:42 PM, david <gnome(a)hawaii.rr.com> wrote:
Bengt Gördén wrote:
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...
torsdag 12 augusti 2010 22:39:39 skrev Jeremy:
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.
On Thu, Aug 12, 2010 at 2:43 PM, drew Roberts
<zotz(a)100jamz.com> wrote:
"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.
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.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:07 a.m.
Jeremy wrote:
On Fri, Aug 13, 2010 at 7:42 PM, david 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 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
<http://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...
Roadrunner does that, too.
FWIW, I just tried traceroute to the traverso domain, and got nothing.
But wget works.
Sorry, the mysteries of the internet are manifold!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
5244
days inactive
5248
days old
linux-audio-user@lists.linuxaudio.org
12 comments
8 participants
participants (8)
-
Atte André Jensen -
Bengt Gördén -
david -
drew Roberts -
Jeremy -
Philipp Überbacher -
Remon Sijrier -
S C Rigler