|
Ticket ID: SIXXS #568683 Ticket Status: Resolved PoP: simbx01 - Amis (Maribor)
simbx01 connectivity problem
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Monday, 27 August 2007 22:47:40
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Hello, I'm Pawel Tobis (PTW1-SIXXS). I have a static tunnel connected to simbx01 PoP.
I've noticed that there is nor IPv6 neither IPv4 connectivity between my endpoint and the PoP. Here is the IPv4 traceroute:
$ traceroute -In -q1 simbx01.sixxs.net
traceroute to simbx01.sixxs.net (212.18.63.73), 30 hops max, 38 byte packets
1 217.96.29.25 1.680 ms
2 80.50.201.253 1.946 ms
3 195.117.0.29 1.991 ms
4 62.156.138.250 23.907 ms
5 62.156.138.249 24.161 ms
6 62.154.15.94 33.832 ms
7 217.6.50.186 38.204 ms
8 195.3.118.93 38.082 ms
9 195.3.70.70 39.460 ms
10 *
11 *
12 *
I'm creating this ticket so quick, because a week ago a similar situation occured and your system gave me a penalty for the inactivity of my tunnel (even though it was not my fault).
I hope this will let you improve your services.
Regards
Pawel Tobis
simbx01 connectivity problem
![[si]](/s/countries/si.gif) Shadow Hawkins on Tuesday, 28 August 2007 11:51:38
simbx01 is currently under a DDoS attack (the IPv4 address of it). Because of this we had to temporary restrict international access to it yesterday night to mitigate the immediate effects of the attack. Fortunately enough the traffic pattern was identifiable and we were able to filter it out without affecting legitimate traffic and right now everything should be working fine.
The previous problems were due to OS instabilities caused by a FreeBSD kernel bug and this issue was solved about two weeks ago.
simbx01 connectivity problem
It is still strange that there are people who believe that DDoSing a PoP actually has any use. The 'annoying person' who they are most likely wanting to get indeed doesn't have connectivity for a while (and more annoyingly the rest of the userbase on that PoP) but after the DDoS is over the connectivity resumes and the person will remain annoying.
As such, if a person is annoying, please simply contact abuse@sixxs.net with relevant details and we will make sure that the person won't be annoying again.
Usage of IRC is a privilege and that privilege will be taken when the usage of it is annoying to others.
State change: resolved
The state of this ticket has been changed to resolved
PoP no longer pings tunnels, reporting tunnel downtime (resubmit)
Carmen Sandiego on Monday, 30 June 2008 13:57:51
Name: Andrej Ota (AO1377-RIPE)
Tunnel: T8493, T12325
PoP simbx01 is no longer probing (ICMP ECHO) tunnel endpoints. This is causing invalid tunnel downtime reports.
- AICCU is not used
- T8493 setup: PPPoE connection via ADSL, no NATs involved.
- T12325 setup: Packet mode connection via VDSL, no NATs involved.
- T8493 OS: Ubuntu Linux: Linux gw-2 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i586 GNU/Linux
- T12325 OS: Ubuntu Linux: Linux gw-2 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i586 GNU/Linux
- T8493 interface table:
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
br0 1500 0 29460620 0 0 0 31747601 0 0 0 BMRU
eth0 1500 0 77792878 0 0 0 32737857 0 0 0 BMRU
eth1 1500 0 32986338 0 0 0 31082586 0 0 0 BMRU
eth2 1500 0 260974 0 0 0 449149 0 0 0 BMRU
lo 16436 0 50 0 0 0 50 0 0 0 LRU
ppp0 1492 0 16353466 0 0 0 13929516 0 0 0 MOPRU
sixxs 1280 0 5742 0 0 0 682 0 0 0 OPRU
tap0 1500 0 67499 0 0 0 132166 0 0 0 BMPRU
- T8493 routing tables:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
213.250.19.90 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
193.189.180.32 0.0.0.0 255.255.255.248 U 0 0 0 eth2
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.252.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
::1/128 :: Un 0 1 25 lo
2001:15c0:65ff:5c::/128 :: Un 0 2 0 lo
2001:15c0:65ff:5c::1/128 :: U 1024 0 1 sixxs
2001:15c0:65ff:5c::2/128 :: Un 0 1 47 lo
2001:15c0:65ff:5c::/64 :: Un 256 0 0 sixxs
2001:15c0:6628::/128 :: Un 0 2 0 lo
2001:15c0:6628::ffff/128 :: Un 0 1 0 lo
2001:15c0:6628::/64 :: U 256 0 0 eth2
2001:15c0:6628:1::/128 :: Un 0 2 0 lo
2001:15c0:6628:1::ffff/128 :: Un 0 1 3993 lo
2001:15c0:6628:1::/64 :: U 256 0 0 br0
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::c14d:383c/128 :: Un 0 1 0 lo
fe80::20c:29ff:febd:77c6/128 :: Un 0 1 265 lo
fe80::20c:29ff:febd:77c6/128 :: Un 0 1 0 lo
fe80::20c:29ff:febd:77d0/128 :: Un 0 1 0 lo
fe80::20c:29ff:febd:77da/128 :: Un 0 1 26377 lo
fe80::2ff:18ff:fea7:9e2d/128 :: Un 0 1 0 lo
fe80::/64 :: U 256 0 0 eth1
fe80::/64 :: U 256 0 0 eth2
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 br0
fe80::/64 :: Un 256 0 0 sixxs
fe80::/64 :: U 256 0 0 tap0
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 eth2
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 br0
ff00::/8 :: U 256 0 0 sixxs
ff00::/8 :: U 256 0 0 tap0
::/0 2001:15c0:65ff:5c::1 UG 1024 0 689 sixxs
::/0 :: !n -1 1 1 lo
- T8493 firewall table:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
- T12325 interface table:
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
ath0 2290 0 1109 0 0 0 11045 0 3 0 BMRU
eth0 1500 0 5588767 0 0 0 3930608 1 0 0 BMRU
eth1 1500 0 0 0 0 0 0 0 0 0 BMU
eth2 1500 0 3924569 0 0 0 5474844 0 0 0 BMRU
lo 16436 0 1342 0 0 0 1342 0 0 0 LRU
sixxs 1280 0 39720 0 0 0 5937 0 0 0 OPRU
wifi0 1500 0 162807 0 0 0 47571 25499 0 0 BMRU
- T12325 routing tables:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
84.255.195.88 0.0.0.0 255.255.255.252 U 0 0 0 eth0
84.255.248.112 0.0.0.0 255.255.255.240 U 0 0 0 eth1
192.168.200.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0
192.168.253.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
0.0.0.0 84.255.195.89 0.0.0.0 UG 0 0 0 eth0
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
::1/128 :: Un 0 1 260 lo
2001:15c0:65ff:10a::/128 :: Un 0 2 0 lo
2001:15c0:65ff:10a::1/128 :: U 1024 0 1 sixxs
2001:15c0:65ff:10a::2/128 :: Un 0 1 5933 lo
2001:15c0:65ff:10a::/64 :: Un 256 0 0 sixxs
2001:15c0:666c::/64 :: U 256 0 0 eth1
2001:15c0:666c:1::/128 :: Un 0 2 0 lo
2001:15c0:666c:1::ffff/128 :: Un 0 1 9 lo
2001:15c0:666c:1::/64 :: U 256 0 0 eth2
2001:15c0:666c:200::/128 :: Un 0 2 0 lo
2001:15c0:666c:200::ffff/128 :: Un 0 1 0 lo
2001:15c0:666c:200::/64 :: U 256 0 0 ath0
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::/128 :: Un 0 2 0 lo
fe80::54ff:c35a/128 :: Un 0 1 0 lo
fe80::54ff:f870/128 :: Un 0 1 0 lo
fe80::c0a8:fd01/128 :: Un 0 1 0 lo
fe80::20b:6bff:fe2c:dcc6/128 :: Un 0 1 1 lo
fe80::20d:b9ff:fe14:134c/128 :: Un 0 1 0 lo
fe80::20d:b9ff:fe14:134e/128 :: Un 0 1 8 lo
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 eth2
fe80::/64 :: U 256 0 0 eth1
fe80::/64 :: Un 256 0 0 sixxs
fe80::/64 :: U 256 0 0 ath0
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 eth2
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 sixxs
ff00::/8 :: U 256 0 0 ath0
::/0 2001:15c0:65ff:10a::1 UG 1024 0 38 sixxs
::/0 :: !n -1 1 1 lo
- T12325 firewall table:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
- IPv4 traceroute for T8493:
traceroute to simbx01.sixxs.net (212.18.63.73), 30 hops max, 40 byte packets
1 BSN-access.dsl.siol.net (213.250.19.90) 28.972 ms 29.151 ms 30.357 ms
2 ljubljanica1-0-0-0.siol.net (89.143.3.13) 30.296 ms 32.031 ms 32.233 ms
3 asterix-1-0-0.siol.net (89.143.1.21) 34.206 ms 34.169 ms 35.861 ms
4 custos-1-1-0.siol.net (89.143.1.6) 39.597 ms 39.786 ms 39.749 ms
5 six.amis.net (193.2.141.40) 40.455 ms 42.665 ms 42.878 ms
6 ljubljana9-po-1.amis.net (212.18.35.121) 42.356 ms 28.233 ms 23.094 ms
7 maribor3-te-1-1.amis.net (212.18.35.233) 192.503 ms 192.721 ms 192.684 ms
8 simbx01.sixxs.net (212.18.63.73) 29.382 ms 31.349 ms 31.300 ms
- IPv6 traceroute for T8493:
traceroute to simbx01.sixxs.net (2001:15c0:ffff:7::2), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 simbx01.sixxs.net (2001:15c0:ffff:7::2) 39.339 ms 40.663 ms 42.848 ms
traceroute to 2001:15c0:65ff:5c::1 (2001:15c0:65ff:5c::1), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 gw-93.mbx-01.si.sixxs.net (2001:15c0:65ff:5c::1) 39.883 ms 42.705 ms 42.642 ms
- IPv4 traceroute for T12325:
1 84-255-195-89.link.t-2.net (84.255.195.89) 22.660 ms 29.986 ms 30.539 ms
2 * * *
3 six.amis.net (193.2.141.40) 33.731 ms 39.287 ms 40.656 ms
4 ljubljana9-po-1.amis.net (212.18.35.121) 39.925 ms 41.305 ms 49.135 ms
5 maribor3-te-1-1.amis.net (212.18.35.233) 49.748 ms 50.376 ms 51.098 ms
6 simbx01.sixxs.net (212.18.63.73) 51.771 ms 24.466 ms 33.805 ms
- IPv6 traceroute for T12325:
traceroute to simbx01.sixxs.net (2001:15c0:ffff:7::2), 30 hops max, 40 byte packets
1 simbx01.sixxs.net (2001:15c0:ffff:7::2) 96.307 ms 21.233 ms 21.920 ms
traceroute to 2001:15c0:65ff:10a::1 (2001:15c0:65ff:10a::1), 30 hops max, 40 byte packets
1 gw-267.mbx-01.si.sixxs.net (2001:15c0:65ff:10a::1) 62.599 ms 21.175 ms 20.916 ms
- HBT not used
- tcpdump for ICMP ECHO packets captured nothing
- simbx01 is marked as up, with no similar unresolved issues.
I am aware that this is good will based service and I respect that. I try to be as concise in my reports as possible, to save you from reading stuff that is not anomalous. For this reason alone I decided to skip reporting about all the stuff that is actualy working just fine and instead report just one what is unexpected and anomalous.
Because there are no probes, tunnels don't get counted as active. Because they don't get counted as active, I get invalid reports about "tunnel downtime". If this won't be rectified in due time, tunnels will get disabled by default.
And the last question is, who will be maintaining simbx01 in future?
Sincerely,
Andrej Ota.
AO1377-RIPE
PoP no longer pings tunnels, reporting tunnel downtime (resubmit)
Carmen Sandiego on Tuesday, 01 July 2008 07:51:29
The problem is still evident. Wireshark capture between 2008-06-30 19:00 UTC and 2008-07-01 05:00 UTC detected no ICMP ECHO probes coming from PoP. Tunnel status pages for both tunnels still show undefined latency times as if tunnels aren't reachable.
There was also confirmation from Marek Stopka in ticket #755847, which was marked as invalid (supposed lack of due diligence?), and I know of at least one more tunnel owner in simbx01 that has an identical problem. This amounts to at least 4 tunnels that I know of, which have identical issues.
I know this is a best effort service and I understand that everybody is doing this on their own time and for free. I don't expect issues to be resolved within hours or days. But I still think I should point out the following:
- my report doesn't belong under this ticket, as it has absolutely no relation to the DDoS problem (IPv4 and IPv6 connectivity is there and working just fine)
- ticket is still marked as invalid which is clearly wrong, based on the available data.
Sincerely,
Andrej Ota
AO1377-RIPE
PoP no longer pings tunnels, reporting tunnel downtime (resubmit)
![[at]](/s/countries/at.gif) Shadow Hawkins on Saturday, 05 July 2008 03:26:22
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
I have the same problem with my tunnel. It is being reported as down, what's clearly impossible, as I am writing this by using the tunnel...
I already sent a long mail regarding this, and I also wrote in the forum.
But now the thread is gone.
I think I will try to switch POP if possible...
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 28 August 2007 13:44:37
Posting is only allowed when you are