|
Route prob? Can only ping self of POP
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Tuesday, 15 June 2004 10:58:33
Hi, I can only ping myself or the POPs ipv6 address, looking at the other posts I get the feeling its a routing problem?
How can this be fixed? Please help me
Im runnin slack9 linux (kernel 2.4.20), using iproute2
sixxs Link encap:UNSPEC HWaddr 0A-00-01-01-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 3ffe:4005:1000:46::2/64 Scope:Global
inet6 addr: fe80::514f:b13b/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:612 errors:0 dropped:0 overruns:0 frame:0
TX packets:854 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:63416 (61.9 Kb) TX bytes:105896 (103.4 Kb)
why is that 'Link encap:UNSPEC'? surely it should be 'IPv6 in IPv4'?
If you need any other info tell me the command to run and I will post it up!
I appreciate your help!
Rick
Route prob? Can only ping self of POP
That is not a correctly configured tunnel, read the FAQ.
Route prob? Can only ping self of POP
Shadow Hawkins on Tuesday, 15 June 2004 20:26:12
Hi, I figured something was setup wrong, but I cant find what, I have read the FAq and set it up how it says, I am keeping my PC ntp synced and everything.
I really appreciate your help
My config script is:
ip tunnel add sixxs mode sit local 81.79.34.47 remote 62.24.229.120
ip link set sixxs up
ip link set mtu 1280 dev sixxs
ip tunnel change sixxs ttl 64
ip -6 addr add 3ffe:4005:1000:46::2/64 dev sixxs
ip -6 ro add default via 3ffe:4005:1000:46::1 dev sixxs
I dont understand whats going wrong or where
Route prob? Can only ping self of POP
Carmen Sandiego on Tuesday, 15 June 2004 21:15:58
I'm no expert on this, but in the absence of any other advice.....
shouldnt 3ffe:4005:1000:46::2/64 be 3ffe:4005:1000:46::2/128
Thats how I've got my tunnel set up.
I do have one thing to add to this however. Since moving my tunnel to Kewlio from ipng pop, I havn't been able to get connectivity until today (15th).
I have my tunnel setup correctly. I could ping my IPv6 tunnel POP endpoint, and I could also ping other peoples POP and tunnel endpoints, but my packets would never get routed out onto the net. I disabled the tunnel and waited for the pings to time out, and then reenabled it to see if it would reenter the routing info correctly but that didn't work. Then today it just started working out onto the net. I now have it working beautifully.
My endpoint is 3ffe:4005:1000:40::2 Can you ping that if you can't ping anything else.
Graham
Route prob? Can only ping self of POP
Shadow Hawkins on Tuesday, 15 June 2004 22:02:32
ok its really starting to annoy me now, i have been playing around with it trying to get it to work and I have probably made it worse!
if i set it to /128 instead of 64 I cant do the last command, setting the 'via' (gateway).
Graham are you using 'ip' or ifconfig?
I think my NAT is messed up as well because I cant even ping pop anymore, NAT is done on hardware router that is crap and I cant do much about, but I will carry on trying.
also sometimes when I try to ping6 it says
ping: bind icmp socket: Invalid argument
great eh?
Rick
Route prob? Can only ping self of POP
Carmen Sandiego on Tuesday, 15 June 2004 22:31:29
Sorry Richard, Like I said I am no expert and didn't want to make things worse for you.
I'm using freebsd so the tunnel setup is all handled for me by the networking scripts.
Here's my Freebsd setup using rc.conf
ipv6_enable="YES"
gif_interfaces="gif0"
gifconfig_gif0="217.151.96.239 62.24.229.120"
ipv6_network_interfaces="gif0"
ipv6_ifconfig_gif0="3ffe:4005:1000:40::2 3ffe:4005:1000:40::1 prefixlen 128"
ipv6_defaultrouter="3ffe:4005:1000:40::1"
Which now works fine. When you had it set to /64 could you ping your own endpoint, i.e is the tunnel up. If so can you then ping my endpoint, suggesting that your default route is ok. If so, can you ping noc.sixxs.net. This is where mine was falling over. I could ping my own tunnel and other peoples endpoints, just no further.
Graham
Route prob? Can only ping self of POP
Carmen Sandiego on Tuesday, 15 June 2004 22:33:49
Richard, is your tunnel enabled. I can't even ping the POP endpoint for you, let alone your endpoint.
I can ping
3ffe:4005:1000:40::1
3ffe:4005:1000:44::1
3ffe:4005:1000:38::1
which must be other tunnels POP endpoints, but not
3ffe:4005:1000:46::1
Graham
Route prob? Can only ping self of POP
If it really is a POP problem why did you not email the staff like mentioned when one tries to post " Operational issues, abuse and other questions should be directed to the contact address." ? :)
Route prob? Can only ping self of POP
Shadow Hawkins on Tuesday, 15 June 2004 23:23:23
Info Tunnel to POP Your IPv4 Your IPv6 State
T3793 Kewlio.net Limited heartbeat 3ffe:4005:1000:46::2 Enabled
POP Description Kewlio.net Limited
POP Location London, United Kingdom (Great Britain)
POP IPv4 62.24.229.120
Your Location Gainsborough, United Kingdom (Great Britain)
Your IPv4 heartbeat
IPv6 Prefix 3ffe:4005:1000:46::1/64
POP IPv6 3ffe:4005:1000:46::1
Your IPv6 3ffe:4005:1000:46::2
Last Alive 2004-06-15 10:17:25
Last Dead 2004-06-14 05:02:31
State Heartbeat
Enabled and should be working....this would explain why I cant ping the POP endpoint...if you cant! Could this be the first time where it is the POP and not the user? (I doubt it, more likely Im gonna look the fool!)
Route prob? Can only ping self of POP
Carmen Sandiego on Tuesday, 15 June 2004 23:30:50
I'm no expert here and am out of my depth as I know nothing about the heartbeat system, but why isnt your ipv4 endpoint listed. Is the heartbeat something to do with dynamic endpoints.
My setup looks like this.
The configuration for this tunnel looks like:
POP Description Kewlio.net Limited
POP Location London, United Kingdom (Great Britain)
POP IPv4 62.24.229.120
Your Location London, United Kingdom (Great Britain)
Your IPv4 217.151.96.239
IPv6 Prefix 3ffe:4005:1000:40::1/64
POP IPv6 3ffe:4005:1000:40::1
Your IPv6 3ffe:4005:1000:40::2
Last Alive 2004-06-15 23:17:22
Last Dead 2004-06-07 13:47:22
State Enabled
Route prob? Can only ping self of POP
I only have one thing to say: Read the FAQ: My heartbeat tunnel doesn't work
Route prob? Can only ping self of POP
Shadow Hawkins on Tuesday, 15 June 2004 23:58:33
because I have a dynamic IPv4 it uses the 'heartbeat' system, a program that runs on my system updating the settings telling the server my IPv4 address
Route prob? Can only ping self of POP
Shadow Hawkins on Wednesday, 16 June 2004 13:54:17
I have read the FAQ Jeroen, but just for fun...
root@RCS:~# ntpdate ntp.demon.co.uk
16 Jun 12:28:49 ntpdate[817]: step time server 158.152.1.76 offset -0.629274 sec
NTP Synced!
root@RCS:~# traceroute 62.24.229.120
traceroute to 62.24.229.120 (62.24.229.120), 30 hops max, 38 byte packets
1 * * *
2 ge0-1.lns3-c5.brm.planet.net.uk (62.25.204.200) 353.954 ms 379.786 ms 394.360 ms
3 ge5-2.pbr-1.brm.as5388.net (62.25.204.194) 337.541 ms 308.654 ms 135.863 ms
4 ber-1.r18.telc.as5388.net (195.92.55.156) 57.811 ms 55.094 ms 23.860 ms
5 ge0-0.th1.uk.as21099.net (195.66.224.162) 27.688 ms 47.511 ms 23.601 ms
6 ge1-1.th1.uk.as21099.net (213.221.179.117) 23.960 ms 25.563 ms 109.883 ms
7 em-0.714-providence.thn.kewlio.net.uk (195.22.135.58) 55.748 ms 41.270 ms 25.887 ms
8 fa0-0.2-omnipotent.sov.kewlio.net.uk (195.22.134.254) 283.682 ms 227.442 ms 157.215 ms
9 ambient.kewlio.net (62.24.229.145) 43.861 ms 63.449 ms 25.520 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Its all very well doing that...but I dont konw what that means...I would hazard a guess something is not right becuase it didt get to the right IP address
And my server is set as the DMZ Host on my router.
TCPDUMP: eth0
12:42:58.665281 10.0.1.1.32769 > 10.0.0.02.53: 30952+ A? gblon01.sixxs.net (35) (DF)
12:42:58.830335 10.0.0.2.53 > 10.0.1.1.32769: 30952 1/3/6 A 62.24.229.120 (237)
12:42:58.830674 10.0.1.1.32769 > 62.24.229.120.3740: udp 93 (DF)
its just that over and over, and I presume thats the heartbeat. (Yes I had to type it out...if I tried to use ssh then that came up in the dump and made it awkward, there probably was a way around it but I couldnt be bothered, it was easier to type it)
Check for Proto-41 activity...how?
Route prob? Can only ping self of POP
Well you could for starters configure your heartbeat client correctly by setting the hb_behindnat option to 1... which you would most people could have told you. Then again that is even more obvious than that Harry Potter 3 movie because it is in the docs ;)
its just that over and over, and I presume thats the heartbeat. (Yes I had to type it out...if I tried to use ssh then that came up in the dump and made it awkward, there probably was a way around it but I couldnt be bothered, it was easier to type it)
"tcpdump -i eth0 not port 22" is harderd than typing it... hmm ;)
Check for Proto-41 activity...how?
The same as the above one, which will show you all the traffic. man tcpdump for more information ;)
You did btw notice the string mentioning "Operational issues, abuse and other questions should be directed to the contact address." when you try to reply ? :)
Route prob? Can only ping self of POP
Shadow Hawkins on Wednesday, 16 June 2004 14:02:46
Jeroen...Graham's connection is working...but why cant he ping my POP endpoint?
Route prob? Can only ping self of POP
His connection works indeed.
jeroen@noc:~$ traceroute6 3ffe:4005:1000:40::2
traceroute to 3ffe:4005:1000:40::2 (3ffe:4005:1000:40::2) from 2001:838:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets
1 fe0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 16.151 ms 0.355 ms 0.28 ms
2 se2.ams-ix.ipv6.concepts-ict.net (2001:838:0:10::1) 3.581 ms 5.594 ms 4.547 ms
3 ipv6.amsix.m20-tc2.trueserver.nl (2001:7f8:1::a501:5703:1) 3.991 ms 5.883 ms 5.04 ms
4 2001:7f8:5::6334:2 (2001:7f8:5::6334:2) 14.841 ms 12.014 ms 16.046 ms
5 3ffe:4005:fefe::30 (3ffe:4005:fefe::30) 19.67 ms 16.956 ms 12.432 ms
6 cl-65.lon-01.gb.sixxs.net (3ffe:4005:1000:40::2) 17.154 ms 17.243 ms 19.487 ms
Route prob? Can only ping self of POP
Shadow Hawkins on Wednesday, 16 June 2004 14:20:40
ok that was weird....I managed to get it so I could ping www.kame.net and 6bone.net....but then it died for no reason >:| I didnt do anything and it just died....great
Route prob? Can only ping self of POP
Like when you are at the shrink, they want you to explain your problem, complaining that you have a problem doesn't lead anywhere. Aka... interface and routing tables, configuration information (heartbeat configs) and of course our beloved tcpdumps. Without that there is no help just like there is no spoon.
Route prob? Can only ping self of POP
Shadow Hawkins on Wednesday, 16 June 2004 14:34:53
the truth is there is not spoon....i like it....
never mind mate...it seems to be working ok now.....*crosses his fingers and touches some wood*
I really do appreciate your help...both of you :)
thanks a lot!
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 15 June 2004 16:27:21
Posting is only allowed when you are