Re: Would using iptables limit my number of possible hops?

On Thu, 30 Aug 2007 10:35:02 -0000, dominic.jacobssen@xxxxxxxxx wrote:

On Aug 30, 12:59 pm, elsid*** <elsid...@xxxxxxxxx> wrote:

I dont think the problem is with the ISP - its somewhere in your
configuration.
Some isps lately must of them block all traceroute/ping queries at
their firewall. and it will never reach the target host. thats not the
issue.
dig somewhere else or try your log files, try to find out whats
blocking/wont let you connect to that mailserver.
ur firewall may be an issue .

zaher el sid***

Hi Zaher, thanks for your reply.

As I said in another reply, it's not just the traceroute/ping traffic
that fails, everything fails (SMTP, HTTP, POP3). This is something
that has been working for a couple of years and has recently stopped
working, with no change to my firewall (the script that initialises
the firewall is kept in SVN, so I know its modification history).

Besides, if it were the firewall, surely that would imply that:

- I wouldn't be able to make the *first* hop, let alone multiple
subsequent hops;
- The protocol would be blocked to *any* remote server, not just a
particular set of servers. For example, my colleague is using
livemail.co.uk, but I'm using the same protocols (pop3, smtp) exactly
with multiple other mail servers and my email works fine.

Cheers,

Dom

There is a way to limit the number of hops with iptables, but it is
doubtful that it is implemented. If you have doubts, turn off the
firewall during your trace. And use tcptracert -n DEST PORT rather
than tracepath / traceroute.

http://michael.toren.net/code/tcptraceroute/
--
buck

.

Quantcast