Re: F29 Wail at the Firewall (long; sorry!)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/12/18 7:15 AM, Samuel Sieb wrote:
>
> traceroute beartooth.info
> traceroute -I beartooth.info
> traceroute -T -p 999 beartooth.info
>
> Some (or all) or those might require root, so best to just use root.

I was able to get the failure condition again. 

This is from a working system....

[root@acer egreshko]# traceroute -n -T -p 999 beartooth.info
traceroute to beartooth.info (208.100.51.176), 30 hops max, 60 byte packets
 1  211.75.128.254  6.136 ms  6.076 ms  6.208 ms
 2  168.95.229.46  6.158 ms  6.078 ms  6.025 ms
 3  220.128.27.94  6.525 ms  6.485 ms  6.437 ms
 4  220.128.7.69  6.788 ms 220.128.14.93  6.325 ms 220.128.7.69  6.675 ms
 5  220.128.30.253  14.755 ms  14.658 ms 220.128.6.85  6.458 ms
 6  211.72.108.81  154.862 ms  154.813 ms 211.72.108.49  144.515 ms
 7  202.39.83.45  152.368 ms 202.39.83.77  152.717 ms  152.691 ms
 8  4.28.172.121  166.896 ms 4.28.172.129  144.516 ms  142.168 ms
 9  * * *
10  4.71.248.202  195.003 ms  205.495 ms  193.438 ms
11  208.100.32.35  301.100 ms  205.363 ms  215.205 ms
12  216.86.153.98  205.625 ms  215.884 ms  215.802 ms
13  208.100.51.176  203.412 ms  215.869 ms  189.607 ms

[root@acer egreshko]# host 208.100.51.176
176.51.100.208.in-addr.arpa domain name pointer artemis.beartooth.info.

And this is from a failing one...

[root@meimei ~]# traceroute -n -T -p 999 beartooth.info
traceroute to beartooth.info (208.100.51.176), 30 hops max, 60 byte packets
 1  192.168.1.1  1.198 ms  0.321 ms  0.454 ms
 2  211.75.128.254  8.701 ms  8.184 ms  9.475 ms
 3  168.95.229.46  9.358 ms  10.435 ms  7.877 ms
 4  220.128.27.94  10.369 ms  9.341 ms  10.332 ms
 5  220.128.14.93  8.145 ms  8.735 ms  9.284 ms
 6  220.128.6.81  10.359 ms *  9.139 ms
 7  211.72.108.5  153.147 ms 211.72.108.49  148.277 ms 211.72.108.5  153.197 ms
 8  202.39.83.45  141.591 ms  144.909 ms 202.39.83.77  169.003 ms
 9  4.28.172.121  148.228 ms  144.076 ms 4.28.172.129  154.525 ms
10  * * *
11  4.71.248.202  216.858 ms  202.435 ms  216.704 ms
12  208.100.32.35  216.585 ms  202.665 ms  216.622 ms
13  216.86.153.98  216.773 ms  216.103 ms  216.158 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


FWIW, I think I triggered the "defensive" response by doing a port scan on 208.100.51.176.

I will check again in a few hours, but I think the defense may drop after a time.

-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux