27 Jan
2015
27 Jan
'15
6:03 a.m.
since Christmas last year more access to 44net for my subnet
44.144.11.128/29
what can i do ???
with the help of Belgian IP Coordinator I used a PPP connection with a
RouterBoard but since then pluis possible connection
My Belgian coordinator does not respond at all to my requests
which has a solution?
thank you in advance
André ON4HU
--
http://on4hu.dyndns.org:81/ http://www.on4hu.be/ http://44.144.11.136/
ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ http://on4hu.eu/
COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING
PROPERLY AS SOON AS YOU OPEN WINDOWS.
27 Jan
27 Jan
6:47 a.m.
Cher OM,
il semble que aucune route pour 44.144.0.0/16 se trouve dans le fichier
encap.txt. Le réseau Belge est donc injoignable via le réseau IPIP.
Par contre le réseau Belge était toujours annoncé directement par BGP
sur Internet. Il semble que cette annonce est toujours active:
[lx1duc(a)LX044-17.ampr.org] > ip route print detail where dst-address in
44.144.0.0/16
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r
- rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P -
prohibit
0 ADb dst-address=44.144.0.0/16 gateway=46.29.182.225
gateway-status=46.29.182.225 reachable via ether10 distance=250
scope=40 target-scope=10
bgp-as-path="60391,51405,24611,3356,30781,35701,62383"
bgp-origin=igp
bgp-communities=3356:2,3356:22,3356:100,3356:123,3356:502,3356:2066,30781:22011,30781:33000,30781:40000,30781:65000,30781:65010,51405:352,51405:1100,51405:2003,51405:10010,51405:10012
received-from=AS60391_v4
Un traceroute s'arrête à 195.234.45.122
traceroute to 44.144.11.128 (44.144.11.128), 30 hops max, 60 byte
packets
1 lx044-18.ampr.org (44.161.204.1) 0.253 ms 0.212 ms 0.153 ms
2 tunnels.lx044.ampr.org (44.161.230.255) 7.328 ms 7.364 ms 7.358
ms
3 mkk1.co-lux-lu.as60391.net (46.29.182.225) 7.953 ms 7.996 ms
7.948 ms
4 v49.e2.mkk176-1.lux.lu.as51405.net (46.29.176.18) 8.123 ms 8.123
ms 8.020 ms
5 v2200.e1.mkk176-6.wdh.lu.as51405.net (46.29.176.110) 8.153 ms
8.167 ms 8.161 ms
6 80-92-83-153.ip.dclux.com (80.92.83.153) 9.284 ms 10.068 ms 9.888
ms
7 ge-5-0-3.bar2.Brussels1.Level3.net (212.162.11.45) 15.219 ms
15.249 ms 15.188 ms
8 ae-2-70.edge4.Paris1.Level3.net (4.69.168.71) 26.406 ms
ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.574 ms
ae-4-90.edge4.Paris1.Level3.net (4.69.168.199) 26.547 ms
9 ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.286 ms
ae-2-70.edge4.Paris1.Level3.net (4.69.168.71) 26.135 ms
ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.110 ms
10 JAGUAR-NETW.edge4.Paris1.Level3.net (212.3.235.62) 35.198 ms
35.444 ms 35.475 ms
11 85.31.194.234 (85.31.194.234) 32.841 ms 32.702 ms 32.543 ms
12 as35701.cust.jaguar-network.net (78.153.224.146) 25.356 ms 25.309
ms 25.486 ms
13 powered.by.as35701.net (195.234.45.122) 26.087 ms !H 26.035 ms !H
25.981 ms !H
L'adresse 195.234.45.122 fait partie du AS35701, il peut par contre
aussi s'agir de l'adresse externe d'un routeur du AS62383, peut importe
le routeur 195.234.45.122 rapporte que la destination est non
accessible.
Cette liste ne peut pas vous aider beaucoup, car la liste ne s'occupe
pas des annonces BGP, la liste s'occupe principalement du réseau IPIP.
A priori, seul l'opérateur du routeur 195.234.45.122 pourra vous donner
plus d'information sur l'origine du problème.
Au Grand-Duché (LX) on supporte le réseau IPIP et on annonce par le BGP.
Ceci évite certains problèmes (notamment si le réseau 44 d'un OM distant
se trouve derrière un NAT) et notre réseau est compatible avec les
principales méthodes de connectivité (IPIP et BGP) du réseau 44.
vy 73 de Marc, LX1DUC
On 2015-01-27 12:03, on4hu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
since Christmas last year more access to 44net for my subnet
44.144.11.128/29
what can i do ???
with the help of Belgian IP Coordinator I used a PPP connection with a
RouterBoard but since then pluis possible connection
My Belgian coordinator does not respond at all to my requests
which has a solution?
thank you in advance
André ON4HU
--
Marc, LX1DUC
--
www.laru.lu - Luxembourg Amateur Radio Union
www.emcomm.services - Emergency Communication
www.ham-dmr.lu - DMR Infos for HAMs
6:59 a.m.
Currently reorganising the entire routing structure of 44.144.0.0/16
with new routing partners. Old routing partners dropped us after we
got a DDOS.
Now moving to paid partners instead of sponsored partners.
When completed all issues will be addressed, including on4hu of which
I am aware. All vpn ip's have also changed since the subnets from the
old partner have been deleted. We have aquired a commercial /24 for
this purpose but are still setting it up.
I don't speak french so i have no clue what you are a saying though.
Please use english on this english mailing list.
73s
Robbie ON4SAX
44.144 coordinator.
On Tue, Jan 27, 2015 at 12:47 PM, Marc, LX1DUC <lx1duc(a)laru.lu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Cher OM,
il semble que aucune route pour 44.144.0.0/16 se trouve dans le fichier
encap.txt. Le réseau Belge est donc injoignable via le réseau IPIP.
Par contre le réseau Belge était toujours annoncé directement par BGP sur
Internet. Il semble que cette annonce est toujours active:
[lx1duc(a)LX044-17.ampr.org] > ip route print detail where dst-address in
44.144.0.0/16
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r -
rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P -
prohibit
0 ADb dst-address=44.144.0.0/16 gateway=46.29.182.225
gateway-status=46.29.182.225 reachable via ether10 distance=250 scope=40
target-scope=10 bgp-as-path="60391,51405,24611,3356,30781,35701,62383"
bgp-origin=igp
bgp-communities=3356:2,3356:22,3356:100,3356:123,3356:502,3356:2066,30781:22011,30781:33000,30781:40000,30781:65000,30781:65010,51405:352,51405:1100,51405:2003,51405:10010,51405:10012
received-from=AS60391_v4
Un traceroute s'arrête à 195.234.45.122
traceroute to 44.144.11.128 (44.144.11.128), 30 hops max, 60 byte packets
1 lx044-18.ampr.org (44.161.204.1) 0.253 ms 0.212 ms 0.153 ms
2 tunnels.lx044.ampr.org (44.161.230.255) 7.328 ms 7.364 ms 7.358 ms
3 mkk1.co-lux-lu.as60391.net (46.29.182.225) 7.953 ms 7.996 ms 7.948 ms
4 v49.e2.mkk176-1.lux.lu.as51405.net (46.29.176.18) 8.123 ms 8.123 ms
8.020 ms
5 v2200.e1.mkk176-6.wdh.lu.as51405.net (46.29.176.110) 8.153 ms 8.167 ms
8.161 ms
6 80-92-83-153.ip.dclux.com (80.92.83.153) 9.284 ms 10.068 ms 9.888 ms
7 ge-5-0-3.bar2.Brussels1.Level3.net (212.162.11.45) 15.219 ms 15.249 ms
15.188 ms
8 ae-2-70.edge4.Paris1.Level3.net (4.69.168.71) 26.406 ms
ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.574 ms
ae-4-90.edge4.Paris1.Level3.net (4.69.168.199) 26.547 ms
9 ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.286 ms
ae-2-70.edge4.Paris1.Level3.net (4.69.168.71) 26.135 ms
ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.110 ms
10 JAGUAR-NETW.edge4.Paris1.Level3.net (212.3.235.62) 35.198 ms 35.444 ms
35.475 ms
11 85.31.194.234 (85.31.194.234) 32.841 ms 32.702 ms 32.543 ms
12 as35701.cust.jaguar-network.net (78.153.224.146) 25.356 ms 25.309 ms
25.486 ms
13 powered.by.as35701.net (195.234.45.122) 26.087 ms !H 26.035 ms !H
25.981 ms !H
L'adresse 195.234.45.122 fait partie du AS35701, il peut par contre aussi
s'agir de l'adresse externe d'un routeur du AS62383, peut importe le routeur
195.234.45.122 rapporte que la destination est non accessible.
Cette liste ne peut pas vous aider beaucoup, car la liste ne s'occupe pas
des annonces BGP, la liste s'occupe principalement du réseau IPIP.
A priori, seul l'opérateur du routeur 195.234.45.122 pourra vous donner plus
d'information sur l'origine du problème.
Au Grand-Duché (LX) on supporte le réseau IPIP et on annonce par le BGP.
Ceci évite certains problèmes (notamment si le réseau 44 d'un OM distant se
trouve derrière un NAT) et notre réseau est compatible avec les principales
méthodes de connectivité (IPIP et BGP) du réseau 44.
vy 73 de Marc, LX1DUC
On 2015-01-27 12:03, on4hu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
since Christmas last year more access to 44net for my subnet
44.144.11.128/29
what can i do ???
with the help of Belgian IP Coordinator I used a PPP connection with a
RouterBoard but since then pluis possible connection
My Belgian coordinator does not respond at all to my requests
which has a solution?
thank you in advance
André ON4HU
--
Marc, LX1DUC
--
www.laru.lu - Luxembourg Amateur Radio Union
www.emcomm.services - Emergency Communication
www.ham-dmr.lu - DMR Infos for HAMs
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
7:22 a.m.
After some carefull translation:
195.235.45.122 is the router where 44.144.0.0/16 is being announced
(the bgp endpoint of as62383, which is us)
This router has an 44.144.0.0/16 -> unreachable default route to avoid
internet storm from passing onto the network.
All subnets inside the 44.144.0.0/16 network are smaller dan /16 and
thus are reachable.
However, since the public ip's for the vpn endpoints (193.22.238.x or
46.18.35.x) no longer exist (blackholed subnets due to ddos), the
router at on4hu is no longer able to connect to our vpn servers. We
are currently migrating this to a new /24 and then the vpn can be
restored. I will contact on4hu offlist when this is the case. We are
not allowed to use bgp endpoints for anything other then bgp. (so no
vpn on top of 195.235.45.122)
Since the vpn of on4hu is not connected, your trace to 44.144.11.128
is catched by the 44.144.0.0/16 -> unreachable route.
This is why 195.235.45.122 is saying that the destination cannot be reached.
73s
Robbie
ON4SAX
On Tue, Jan 27, 2015 at 12:47 PM, Marc, LX1DUC <lx1duc(a)laru.lu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Cher OM,
il semble que aucune route pour 44.144.0.0/16 se trouve dans le fichier
encap.txt. Le réseau Belge est donc injoignable via le réseau IPIP.
Par contre le réseau Belge était toujours annoncé directement par BGP sur
Internet. Il semble que cette annonce est toujours active:
[lx1duc(a)LX044-17.ampr.org] > ip route print detail where dst-address in
44.144.0.0/16
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r -
rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P -
prohibit
0 ADb dst-address=44.144.0.0/16 gateway=46.29.182.225
gateway-status=46.29.182.225 reachable via ether10 distance=250 scope=40
target-scope=10 bgp-as-path="60391,51405,24611,3356,30781,35701,62383"
bgp-origin=igp
bgp-communities=3356:2,3356:22,3356:100,3356:123,3356:502,3356:2066,30781:22011,30781:33000,30781:40000,30781:65000,30781:65010,51405:352,51405:1100,51405:2003,51405:10010,51405:10012
received-from=AS60391_v4
Un traceroute s'arrête à 195.234.45.122
traceroute to 44.144.11.128 (44.144.11.128), 30 hops max, 60 byte packets
1 lx044-18.ampr.org (44.161.204.1) 0.253 ms 0.212 ms 0.153 ms
2 tunnels.lx044.ampr.org (44.161.230.255) 7.328 ms 7.364 ms 7.358 ms
3 mkk1.co-lux-lu.as60391.net (46.29.182.225) 7.953 ms 7.996 ms 7.948 ms
4 v49.e2.mkk176-1.lux.lu.as51405.net (46.29.176.18) 8.123 ms 8.123 ms
8.020 ms
5 v2200.e1.mkk176-6.wdh.lu.as51405.net (46.29.176.110) 8.153 ms 8.167 ms
8.161 ms
6 80-92-83-153.ip.dclux.com (80.92.83.153) 9.284 ms 10.068 ms 9.888 ms
7 ge-5-0-3.bar2.Brussels1.Level3.net (212.162.11.45) 15.219 ms 15.249 ms
15.188 ms
8 ae-2-70.edge4.Paris1.Level3.net (4.69.168.71) 26.406 ms
ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.574 ms
ae-4-90.edge4.Paris1.Level3.net (4.69.168.199) 26.547 ms
9 ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.286 ms
ae-2-70.edge4.Paris1.Level3.net (4.69.168.71) 26.135 ms
ae-1-60.edge4.Paris1.Level3.net (4.69.168.7) 26.110 ms
10 JAGUAR-NETW.edge4.Paris1.Level3.net (212.3.235.62) 35.198 ms 35.444 ms
35.475 ms
11 85.31.194.234 (85.31.194.234) 32.841 ms 32.702 ms 32.543 ms
12 as35701.cust.jaguar-network.net (78.153.224.146) 25.356 ms 25.309 ms
25.486 ms
13 powered.by.as35701.net (195.234.45.122) 26.087 ms !H 26.035 ms !H
25.981 ms !H
L'adresse 195.234.45.122 fait partie du AS35701, il peut par contre aussi
s'agir de l'adresse externe d'un routeur du AS62383, peut importe le routeur
195.234.45.122 rapporte que la destination est non accessible.
Cette liste ne peut pas vous aider beaucoup, car la liste ne s'occupe pas
des annonces BGP, la liste s'occupe principalement du réseau IPIP.
A priori, seul l'opérateur du routeur 195.234.45.122 pourra vous donner plus
d'information sur l'origine du problème.
Au Grand-Duché (LX) on supporte le réseau IPIP et on annonce par le BGP.
Ceci évite certains problèmes (notamment si le réseau 44 d'un OM distant se
trouve derrière un NAT) et notre réseau est compatible avec les principales
méthodes de connectivité (IPIP et BGP) du réseau 44.
vy 73 de Marc, LX1DUC
On 2015-01-27 12:03, on4hu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
since Christmas last year more access to 44net for my subnet
44.144.11.128/29
what can i do ???
with the help of Belgian IP Coordinator I used a PPP connection with a
RouterBoard but since then pluis possible connection
My Belgian coordinator does not respond at all to my requests
which has a solution?
thank you in advance
André ON4HU
--
Marc, LX1DUC
--
www.laru.lu - Luxembourg Amateur Radio Union
www.emcomm.services - Emergency Communication
www.ham-dmr.lu - DMR Infos for HAMs
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
8:13 a.m.
Hello Robbie,
glad to see that you are working on the issue. If I can be of any
assistance or if you want to extend your peerings, please let me know.
In my previous message I was merely trying to help the OM in the
language he seems to understand best, it seemed to me that he used a
translation engine to translate from french into english, so I thought
that an answer in english would be difficult for him to understand.
It was not my intention to harm feelings of Belgian OMs that don't speak
french.
vy 73 de Marc
On 2015-01-27 12:59, Robbie De Lise wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Currently reorganising the entire routing structure of 44.144.0.0/16
with new routing partners. Old routing partners dropped us after we
got a DDOS.
Now moving to paid partners instead of sponsored partners.
When completed all issues will be addressed, including on4hu of which
I am aware. All vpn ip's have also changed since the subnets from the
old partner have been deleted. We have aquired a commercial /24 for
this purpose but are still setting it up.
I don't speak french so i have no clue what you are a saying though.
Please use english on this english mailing list.
73s
Robbie ON4SAX
44.144 coordinator.
4:40 p.m.
Hello Marc lx1duc, hello Robbies on4asx
finally a expliocation!
March thank you for the response and also Mark, who still pursue the
subject to solve this problem!
little easier not know the French language and explain in another language
Vy73s
André ON4HU
Le 27/01/15 14:13, Marc, LX1DUC a écrit :
(Please trim inclusions from previous messages)
_______________________________________________
Hello Robbie,
glad to see that you are working on the issue. If I can be of any
assistance or if you want to extend your peerings, please let me know.
In my previous message I was merely trying to help the OM in the
language he seems to understand best, it seemed to me that he used a
translation engine to translate from french into english, so I thought
that an answer in english would be difficult for him to understand.
It was not my intention to harm feelings of Belgian OMs that don't
speak french.
vy 73 de Marc
On 2015-01-27 12:59, Robbie De Lise wrote:
--
http://on4hu.dyndns.org:81/ http://www.on4hu.be/ http://44.144.11.136/
ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ http://on4hu.eu/
COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING
PROPERLY AS SOON AS YOU OPEN WINDOWS.
(Please trim inclusions from previous messages)
_______________________________________________
Currently reorganising the entire routing structure of 44.144.0.0/16
with new routing partners. Old routing partners dropped us after we
got a DDOS.
Now moving to paid partners instead of sponsored partners.
When completed all issues will be addressed, including on4hu of which
I am aware. All vpn ip's have also changed since the subnets from the
old partner have been deleted. We have aquired a commercial /24 for
this purpose but are still setting it up.
I don't speak french so i have no clue what you are a saying though.
Please use english on this english mailing list.
73s
Robbie ON4SAX
44.144 coordinator.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
3395
days inactive
3395
days old
5 comments
3 participants
participants (3)
-
Marc, LX1DUC -
on4hu -
Robbie De Lise