Login: GUEST @ JH4XSY.14.JNET1.JPN.AS [Tsuchiura]
home | newest check | boards | help index | log | ps | userlogin | send sysop | slog | status forward | bcm news | users | version | remove cookieI0OJJ > SYSOP 08.06.25 22:23l 85 Lines 3492 Bytes #6 (0) @ WW BID : 86ZI0OJJ_002 Read: GUEST Subj: Re: IPIP failure Path: JH4XSY<IW0QNL<HB9ON<DK0WUE<PI8ZTM<PI8LAP<VE2PKT<PY2BIL<LU9DCE<EA2RCF< I0OJJ Sent: 250608/1320z @:I0OJJ.ITA.EU [Rome] obcm1.08-10-g596e From: I0OJJ @ I0OJJ.ITA.EU (Gustavo) To: SYSOP @ WW X-Info: This message was generated automatically Hi, generally I read msgs from several ML but I learnt for some reasons to not reply to debacts because time limitation... But since the matter is always interesting I want to contribute by using the packet and give support with my findings. The IPIP matter is deeply explained on several places, so the reader is addressed to learn by those means. After the creation of the IPIP tunnel, i.e. tunl0, the easy way is to capture the RIP IPv4 from ucsd.edu, necessary to establish on the linux machine the networks toward other ampr.org sites. The format of broadcasts is similar to the following: 09:45:00.754915 IP (tos 0x0, ttl 47, id 44672, offset 0, flags [none], proto IPIP (4), length 552) amprgw.ucsd.edu > rmgate.ampr.org: IP (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto UDP (17), length 532) gw.ampr.org.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 504, routes: 25 or less Simple Text Authentication data: xxxxxxxxxxxxxxxx AFI IPv4, gw.ampr.org/32, tag 0x0004, metric: 1, next-hop: amprgw.ucsd.edu AFI IPv4, k9jm.ampr.org/32, tag 0x0004, metric: 1, next-hop: h94.3.40.69.dynamic.ip.windstream.net AFI IPv4, 44.2.2.0/24, tag 0x0004, metric: 1, next-hop: black-mountain-communications.e0-21.switch17.fmt2.he.net AFI IPv4, 44.2.7.0/30, tag 0x0004, metric: 1, next-hop: c-98-56-227-244.hsd1.ca.comcast.net AFI IPv4, 44.2.10.0/29, tag 0x0004, metric: 1, next-hop: c-50-189-14-165.unallocated.comcastbusiness.net AFI IPv4, 44.2.10.8/29, tag 0x0004, metric: 1, next-hop: 104.49.12.133 AFI IPv4, 44.2.11.8/29, tag 0x0004, metric: 1, next-hop: syn-174-087-201-164.res.spectrum.com AFI IPv4, 44.2.50.0/29, tag 0x0004, metric: 1, next-hop: syn-097-094-148-032.res.spectrum.com AFI IPv4, gw-kn6ixm.ampr.org/29, tag 0x0004, metric: 1, next-hop: 216.218.193.200 AFI IPv4, 44.4.2.160/29, tag 0x0004, metric: 1, next-hop: 70-90-167-65-CA.hfc.comcastbusiness.net AFI IPv4, 44.4.2.208/29, tag 0x0004, metric: 1, next-hop: 108-228-10-20.lightspeed.sntcca.sbcglobal.net AFI IPv4, ki6zhd-net.ampr.org/29, tag 0x0004, metric: 1, next-hop: ampr.trinnet.net <SNIP> Since things are not always perfect, it happens that the RIP broadcasts may be missing also for several days. Things are greatly improved as today and so (normally) the portal.ampr.org is able to re-syncronize my dynamic IP changes in, say, one/two hours. Method used from new generations is the rip44d/ampr-ripd utilities. Me, old man generation, prefer to mungle with encap.txt to obtain the scope. However, to reply to the OM on the ARDC ML, if you, obtain an 'ifconfig' reply similar to the following, it means that your ADSL router receives all IPIP traffic but cut away the retransmission of IPIP traffic, so no 44net operation is feasible. tunl0: flags=193<UP,RUNNING,NOARP> mtu 1480 inet 192.168.1.100 netmask 255.255.255.255 tunnel txqueuelen 1000 (IPIP Tunnel) RX packets 1935255 bytes 113660026 (108.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 493 bytes 23087 (22.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 My actual setup operation make the use of a good ADSL router but it have the limitation just described above. -- 73 and ciao, gustavo i0ojj/ir0aab/ir0eq non multa, sed multum
前のメール | 次のメール