Help Debugging connection to ip?
-
Hello,
I am unable to connect to the ip 66.70.234.210Two days ago, before installing the pfsense box I could
Using 3rd party websites, I can ping that addressFrom the pfsense box I always get:
PING 66.70.234.210 (66.70.234.210): 56 data bytes --- 66.70.234.210 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss
In the firewall log I see:
PASS Apr 6 15:32:13 ► WAN let out anything from firewall host itself (1000110341) 66.74.215.113 66.70.234.210 ICMP PASS Apr 6 15:26:32 ► WAN let out anything from firewall host itself (1000110341) 66.74.215.113 66.70.234.210 ICMP PASS Apr 6 15:23:19 ► WAN let out anything from firewall host itself (1000110341) 66.74.215.113 66.70.234.210 ICMP
(the above has a destination filter for 66.70.234.210 set)
I am at a loss of how or what tools I would use to debug this.
Any help would be appreciated
notes:
I am using the following packages:
Avahi
pfBlockerNG (already checked the logs and nothing) -
If your sending it out your wan, and you get no answer.. Either they do not answer ping or your pings are not getting there.
Seems to answer ping
ping 66.70.234.210
PING 66.70.234.210 (66.70.234.210) 56(84) bytes of data.
64 bytes from 66.70.234.210: icmp_seq=1 ttl=49 time=44.4 ms
64 bytes from 66.70.234.210: icmp_seq=2 ttl=49 time=42.9 ms
64 bytes from 66.70.234.210: icmp_seq=3 ttl=49 time=41.4 msWhat does your traceroute show?
when I hit that IP via http it comes back
mining server onlineWhat are you trying to do exactly?
Those seem to be OVH ips, so their DC.. So some VPS or dedicated box? Looks like those IPs are failover?
NetRange: 66.70.234.0 - 66.70.234.255
CIDR: 66.70.234.0/24
NetName: OVH-DEDICATED-FO
NetHandle: NET-66-70-234-0-1
Parent: HO-2 (NET-66-70-128-0-1)
NetType: Reassigned
OriginAS: AS16276
Organization: OVH (NWK) (ON-6)
RegDate: 2017-06-21
Updated: 2017-06-21
Comment: Failover IPs -
I am attempting to connect to:
xmr-usa.dwarfpool.com
There are four ips associated. I seem unable to connect to any of them. I decided to pick one to debug as a method of simplifying my problem.
I am able to connect to xmr-eu.dwarfpool.com. However, this comes with a 220ms latency, which means I am wasting 1/4th a second every block switch.
The tracert result is below:
1 142.254.186.169 (142.254.186.169) 9.315 ms 8.921 ms 8.643 ms 2 agg62.plspcajn02h.socal.rr.com (76.167.16.253) 23.787 ms 21.092 ms 21.938 ms 3 agg21.pldscabx02r.socal.rr.com (72.129.38.44) 11.796 ms 11.893 ms 11.122 ms 4 72.129.37.2 (72.129.37.2) 18.525 ms 16.012 ms 15.858 ms 5 bu-ether26.tustca4200w-bcr00.tbone.rr.com (66.109.3.232) 18.139 ms 15.975 ms 15.723 ms 6 * * * 7 * * * 8 chi-1-a9.il.us (198.27.73.66) 102.445 ms 102.852 ms 103.351 ms 9 be100-1320.bhs-g1-nc5.qc.ca (198.27.73.206) 103.989 ms 106.690 ms 104.195 ms 10 * * * 11 be50-5.bhs-3a-a9.qc.ca (198.27.73.92) 203.958 ms 233.496 ms be50-5.bhs-3b-a9.qc.ca (198.27.73.96) 105.108 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * or icmp version: 1 142.254.186.169 (142.254.186.169) 10.882 ms 8.525 ms 8.066 ms 2 agg62.plspcajn02h.socal.rr.com (76.167.16.253) 28.071 ms 21.638 ms 21.982 ms 3 agg21.pldscabx02r.socal.rr.com (72.129.38.44) 13.708 ms 11.712 ms 11.523 ms 4 72.129.37.2 (72.129.37.2) 16.385 ms 15.928 ms 16.161 ms 5 bu-ether26.tustca4200w-bcr00.tbone.rr.com (66.109.3.232) 19.546 ms 15.761 ms 16.272 ms 6 * * 4.68.111.101 (4.68.111.101) 13.825 ms 7 * ae-1-3507.ear4.Chicago2.Level3.net (4.69.142.105) 70.355 ms * 8 chi-1-a9.il.us (198.27.73.66) 102.583 ms 104.058 ms 102.287 ms 9 be100-1320.bhs-g1-nc5.qc.ca (198.27.73.206) 102.112 ms 105.070 ms 102.455 ms 10 * * * 11 be50-5.bhs-3b-a9.qc.ca (198.27.73.96) 103.115 ms 104.946 ms 103.255 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * *
I also emailed dwarfpool to see if they had any suggestions.