Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : After Trace route, what next ?

[mhhost]

After Trace route whats the next thing to do ? When my ISP dynamic IP address is some like and starts with 112.0.0.0 I cannot see all sites on the server. So what I did run a tracert on DOS prompt. After 9 hops and reach this IP 216.18.239.6 everything timed out and it cannot reach my server.

I already tested several Internet access and its reaching the server except my home DSL with the IP 112. I also checked if the IP is block on the firewall but its not present on the block list. I also mentioned this with my internet provider and still waiting for notification.

what to do next?

thank you.

[ianeeshps]

Are you sure that got blocked with ISP. ask your host to check in server firewall....

[eeg3]

Find out what the next hop is from a machine that can reach your site. Have your host turn your software firewall off just to make sure.

It is unlikely that your ISP is blocking you from your specific dedicated server.

[Winstyn]

I assume you are trying to tracert to your server. 9 hops sounds like you reached the open net but had trouble getting through the DC. A bad vLan, wrongly configured NIC even a Null-Routed port could all account for this. The support on the other end has to handle this issue unless you have IPMI or KVM.

[subinfrancis]

It seems that the network 112.1.0.0 is blocked in your server. Try the following commands. If needed unblock the network from firewall. You can also try white listing your IP in the server.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!
iptables -nL|grep 112.0.0.0
iptables -nL|grep 112.1.0.0
!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[whrss]

Your datacenter will help you out if the 9th hop is any of their Internet carriers.

If it is a hop just before reaching your datacenters n/w then you will have to solely rely on your ISP for help.

[david510]

It should be any intermediate router that is blocking that particular range of IP. Since it is happening at the 9th hop, most likely the datacenter would be able to help you in this.

[mhhost]

Originally Posted by ianeeshps

Are you sure that got blocked with ISP. ask your host to check in server firewall....

Thank you for the reply. My suspicion about this when one day my home DSL IP suddenly changed to this 112.xxx.xxx.xxx. This is the time I get complain also from my other clients who also inform me their DSL ip starts with 112.

[mhhost]

Originally Posted by eeg3

Find out what the next hop is from a machine that can reach your site. Have your host turn your software firewall off just to make sure.

It is unlikely that your ISP is blocking you from your specific dedicated server.

the next hop is the IP of my server. When you say firewall.. is this the APF/BFD ?

[whrss]

You would need to check the firewall running in your server.

Hit "apf" or "csf" commands via shell. or you should see /etc/apf or /etc/csf files.

Allow your IP in the firewall rules.

If you don't have APF/CSF then you can allow it in iptables chain

[mhhost]

hi,

Its the firewall. I stop it and I was able to see my IP. Next question would be.

How do I allow my IP that starts with 112.203. ? you see this is a dynamic IP so it changes.

I already run these as suggested by did not solved.
iptables -nL|grep 112.0.0.0
iptables -nL|grep 112.203.0.0

I also added my IP to /etc/apf/allow_hosts.rules but it looks like its not working either.

any inputs ?

[whrss]

Use the below command:

apf -a 112.203.0.0/16, This will allow the entire subnet.

[mhhost]

thank you for the reply.

I did that command but whenever APF is up my dsl still cannot see my server. I even added my ip to allow host but still not working.

Right now I stopped apf but of course it should not like this.

[whrss]

After allowing the subnet are you seeing those in the firewall rules?

----------
iptables -nL|grep 112
----------

[mhhost]

no its not showing anything when I execute
----------
iptables -nL|grep 112
----------
but when I run the command below it says
------
apf -a 112.203.0.0/16
------
------
112.203.0.0/16 already exists in /etc/apf/allow_hosts.rules
-----

thank you