Maybe someone knows who '44.64.193.1' is and can contact him? tnx jerome - ve7ass
Fri Feb 21 20:08:58 2014 - tun0 recv: IP: len 96 24.229.88.253->192.168.1.149 ihl 20 ttl 240 prot IP IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 1 tos 192 prot 89 0000 ...,.,.......r.....................(....................
Fri Feb 21 20:08:58 2014 - tun0 recv: IP: len 96 24.229.88.253->192.168.1.149 ihl 20 ttl 240 prot IP IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 1 tos 192 prot 89 0000 ...,.,.......r.....................(.................... (encap) 44.64.193.1->224.0.0.5 prot 89 0000 ...,.,.......r.....................(.................... (encap) 44.135.160.40->44.64.193.1 ICMP Time ExceededTime-to-live Returned 44.64.193.1->224.0.0.5 prot 89 0000 ...,.,..
Fri Feb 21 20:08:58 2014 - tun0 sent: IP: len 76 192.168.1.149->24.229.88.253 ihl 20 ttl 254 prot IP IP: len 56 44.135.160.40->44.64.193.1 ihl 20 ttl 254 tos 192 prot ICMP ICMP: type Time Exceeded code Time-to-live Returned IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 0 tos 192 prot 89 0000 ...,.,..
On Fri, 2014-02-21 at 20:32 -0800, Jerome Schatten spake:
n1uro@gw.kmmb.ampr.org:/uronode$ host 44.64.193.1 Host name information for 44.64.193.1: Hostname: wc3xs-193.ampr.org Aliases: Address(es): 44.64.193.1
Jerome,
My most humble apologies. I just reconfigured my network to use my Cisco router for AMPRnet routing and realized I did not passive out the tunnel interfaces for my OSPF process.
The HELO packets should have stopped now.
Jesse - WC3XS
On Feb 21, 2014, at 11:32 PM, Jerome Schatten romers@shaw.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ Maybe someone knows who '44.64.193.1' is and can contact him? tnx jerome - ve7ass
Fri Feb 21 20:08:58 2014 - tun0 recv: IP: len 96 24.229.88.253->192.168.1.149 ihl 20 ttl 240 prot IP IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 1 tos 192 prot 89 0000 ...,.,.......r.....................(....................
Fri Feb 21 20:08:58 2014 - tun0 recv: IP: len 96 24.229.88.253->192.168.1.149 ihl 20 ttl 240 prot IP IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 1 tos 192 prot 89 0000 ...,.,.......r.....................(.................... (encap) 44.64.193.1->224.0.0.5 prot 89 0000 ...,.,.......r.....................(.................... (encap) 44.135.160.40->44.64.193.1 ICMP Time ExceededTime-to-live Returned 44.64.193.1->224.0.0.5 prot 89 0000 ...,.,..
Fri Feb 21 20:08:58 2014 - tun0 sent: IP: len 76 192.168.1.149->24.229.88.253 ihl 20 ttl 254 prot IP IP: len 56 44.135.160.40->44.64.193.1 ihl 20 ttl 254 tos 192 prot ICMP ICMP: type Time Exceeded code Time-to-live Returned IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 0 tos 192 prot 89 0000 ...,.,..
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Many thanks Jesse! Best Jerome
Sent from my iPhone
On Feb 21, 2014, at 20:49, Jesse Hindmarsh jesse@hindmarsh.cc wrote:
(Please trim inclusions from previous messages) _______________________________________________ Jerome,
My most humble apologies. I just reconfigured my network to use my Cisco router for AMPRnet routing and realized I did not passive out the tunnel interfaces for my OSPF process.
The HELO packets should have stopped now.
Jesse - WC3XS
On Feb 21, 2014, at 11:32 PM, Jerome Schatten romers@shaw.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ Maybe someone knows who '44.64.193.1' is and can contact him? tnx jerome - ve7ass
Fri Feb 21 20:08:58 2014 - tun0 recv: IP: len 96 24.229.88.253->192.168.1.149 ihl 20 ttl 240 prot IP IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 1 tos 192 prot 89 0000 ...,.,.......r.....................(....................
Fri Feb 21 20:08:58 2014 - tun0 recv: IP: len 96 24.229.88.253->192.168.1.149 ihl 20 ttl 240 prot IP IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 1 tos 192 prot 89 0000 ...,.,.......r.....................(.................... (encap) 44.64.193.1->224.0.0.5 prot 89 0000 ...,.,.......r.....................(.................... (encap) 44.135.160.40->44.64.193.1 ICMP Time ExceededTime-to-live Returned 44.64.193.1->224.0.0.5 prot 89 0000 ...,.,..
Fri Feb 21 20:08:58 2014 - tun0 sent: IP: len 76 192.168.1.149->24.229.88.253 ihl 20 ttl 254 prot IP IP: len 56 44.135.160.40->44.64.193.1 ihl 20 ttl 254 tos 192 prot ICMP ICMP: type Time Exceeded code Time-to-live Returned IP: len 76 44.64.193.1->224.0.0.5 ihl 20 ttl 0 tos 192 prot 89 0000 ...,.,..
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On 14-02-21 10:18 PM, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Fri, Feb 21, 2014 at 08:32:10PM -0800, Jerome Schatten wrote:
Maybe someone knows who '44.64.193.1' is and can contact him?
Just a note to say that we're working on a WHOIS service so that people will be able to look up and contact folks when cases like this arise.
- Brian
Excellent! Thanks, jerome
-
Brian -
Brian Kantor -
Jerome Schatten -
Jesse Hindmarsh