PDA

View Full Version : Debian packages for showeq 5.0.0.15-4 (Oct 13 struct patch)



tanner
10-14-2004, 10:35 PM
Just put up:
showeq-dev_5.0.0.15-4_i386.deb
showeq-doc_5.0.0.15-4_all.deb
showeq_5.0.0.15-4_i386.deb

Add the following to your /etc/apt/sources.list

deb ftp://ftp.real-time.com/linux/real-time unstable custom
deb-src ftp://ftp.real-time.com/linux/real-time unstable custom

Minimal Installation:
% sudo apt-get update
% sudo apt-get install showeq

Optional Installation:
% sudo apt-get install showeq-maps
% sudo apt-get install showeq-doc

OR

% sudo apt-get install mapfiend-maps
% sudo apt-get install showeq-doc

Changelog:
ftp://ftp.real-time.com/linux/real-time/pool/s/showeq/showeq_5.0.0.15-4_i386.changes

Nothing major here just the Oct13 struct patch.

Hogi
10-15-2004, 07:15 AM
valdyn@master:~$ ping ftp.real-time.com
ping: unknown host ftp.real-time.com

I<3EQ
10-15-2004, 07:37 AM
[user@localhost user]$ nslookup ftp.real-time.com
Server: 192.168.2.1
Address: 192.168.2.1#53

ftp.real-time.com canonical name = gladiator.real-time.com.
Name: gladiator.real-time.com
Address: 208.20.202.31

[user@localhost user]$ ping ftp.real-time.com
PING gladiator.real-time.com (208.20.202.31) 56(84) bytes of data.
64 bytes from gladiator.real-time.com (208.20.202.31): icmp_seq=1 ttl=39 time=59.6 ms
64 bytes from gladiator.real-time.com (208.20.202.31): icmp_seq=2 ttl=39 time=59.7 ms
64 bytes from gladiator.real-time.com (208.20.202.31): icmp_seq=3 ttl=39 time=56.2 ms
64 bytes from gladiator.real-time.com (208.20.202.31): icmp_seq=4 ttl=39 time=58.0 ms

--- gladiator.real-time.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 56.233/58.412/59.723/1.433 ms


Looks like theres something wrong with your DNS.

Hogi
10-15-2004, 11:48 AM
not my dns which is broken, the error is something else and beyond just dns not working, and its not my system.
Any mirror?

thanks in advance..

Hogi

tanner
10-15-2004, 02:31 PM
not my dns which is broken, the error is something else and beyond just dns not working, and its not my system.
Any mirror?

thanks in advance..


No official mirror, hopefully someone will volunteer. I'm also willing to put it somewhere else, if someone will volunteer space for me.

As an aside, showeq was just accepted into the official debian repository, so it should be making the rounds once it makes it through buildd.

If you don't mind, can you send me your source IP address(es)?

This is 1Tb ftp server that sits on multiple links to multiple Tier1 providers here in the US, so I don't know why you can't get here.

I'd like to investigate further.

Hogi
10-16-2004, 04:15 AM
my ip changes once per 24 hours, but can be looked up via "valdyn.mine.nu". Resolving ftp.real-time.com doesn't work.

aldyn@master:~$ ping 208.20.202.31
PING 208.20.202.31 (208.20.202.31) 56(84) bytes of data.
From 207.67.87.38 icmp_seq=2 Packet filtered
From 207.67.87.38 icmp_seq=4 Packet filtered
From 207.67.87.38 icmp_seq=8 Packet filtered


valdyn@master:~$ traceroute 208.20.202.31
traceroute to 208.20.202.31 (208.20.202.31), 30 hops max, 38 byte packets
1 192.168.1.254 (192.168.1.254) 0.627 ms 0.446 ms 0.410 ms
2 217.5.98.96 (217.5.98.96) 60.852 ms 59.929 ms 50.655 ms
3 217.237.152.70 (217.237.152.70) 48.533 ms 50.096 ms 49.995 ms
4 NYC-gw14.USA.net.DTAG.DE (62.156.131.157) 141.871 ms 141.353 ms 140.979 ms
5 tran-02-so-0-1-0-0.nycl.twtelecom.net (66.192.252.249) 139.863 ms 142.034 ms 140.416 ms
6 core-01-ge-0-2-1-0.nycl.twtelecom.net (66.192.240.41) 143.263 ms 141.493 ms 139.723 ms
7 core-01-ge-0-2-1-1.chcg.twtelecom.net (66.192.255.65) 161.838 ms 161.274 ms 162.072 ms
8 66.192.254.15 (66.192.254.15) 177.096 ms 178.501 ms 177.357 ms
9 66-192-253-85.gen.twtelecom.net (66.192.253.85) 177.335 ms 186.183 ms 177.283 ms
10 207-67-87-38.gen.twtelecom.net (207.67.87.38) 178.357 ms !A 178.979 ms !A *

DSL - Router: Billion Bipac 741
My box:


valdyn@master:~$ cat /proc/version
Linux version 2.6.8.1-ck7 (root@master) (gcc-Version 3.3.4 (Debian 1:3.3.4-11)) #1 Mon Sep 13 22:36:16 CEST 2004



I expect this to be a broken router somewhere, but I'm not competent to figure out details.
My kernel naturally includes the fix that was applied to the tcp/ip stack in linux around 2.6.8, which will break connecting to some "broken" routers.
( gentoo server wasn't accessible for gentoo users for a while for that reason )

Hogi