Re: [44net] Help in finding Tunnel Problem

Can you check that the replies use the tunnel endpoint's address as source (44.138.1.1), and use the tunnel interface as outgoing If? It happens on some machines that the replies are sent through the external interface instead of the tunnel... -----Original Message----- From: R P Sent: Thursday, February 18, 2016 21:23 To: AMPRNet working group Subject: Re: [44net] Help in finding Tunnel Problem (Please trim inclusions from previous messages) _______________________________________________ Ok I have little progress with the correct tunnel address the tunnel interface seem to receive packets when i trace route to its 44 net from the outside world and appear to send packet as reply but still no go I have taken all access list out any help is welcome Please Advice Ronen - 4Z4ZQ http://www.ronen.org Cisco1005_HAIFA#sh int tun0 Tunnel0 is up, line protocol is up Hardware is Tunnel Interface is unnumbered. Using address of Ethernet0 (10.0.0.180) MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255 Encapsulation TUNNEL, loopback not set, keepalive set (10 sec) Tunnel source 10.0.0.180 (Ethernet0), destination 169.228.66.251 Tunnel protocol/transport IP/IP, key disabled, sequencing disabled Checksumming of packets disabled Last input 00:00:02, output 00:00:28, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677 Queueing strategy: fifo Output queue 0/0 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 395 packets input, 94081 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 153001 packets output, 16476952 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out Cisco1005_HAIFA# Cisco1005_HAIFA# Cisco1005_HAIFA#sh int tun0 Tunnel0 is up, line protocol is up Hardware is Tunnel Interface is unnumbered. Using address of Ethernet0 (10.0.0.180) MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255 Encapsulation TUNNEL, loopback not set, keepalive set (10 sec) Tunnel source 10.0.0.180 (Ethernet0), destination 169.228.66.251 Tunnel protocol/transport IP/IP, key disabled, sequencing disabled Checksumming of packets disabled Last input 00:00:01, output 00:00:08, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 93677 Queueing strategy: fifo Output queue 0/0 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 505 packets input, 120749 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 153015 packets output, 16479248 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out Cisco1005_HAIFA# ________________________________________ From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Brian Kantor <Brian(a)UCSD.Edu> Sent: Thursday, February 18, 2016 10:29 AM To: AMPRNet working group Subject: Re: [44net] Help in finding Tunnel Problem (Please trim inclusions from previous messages) _______________________________________________ On Thu, Feb 18, 2016 at 06:24:15PM +0000, R P wrote: That is the wrong address. The UCSD tunnel is at 169.228.66.251. - Brian _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net