search for: tcptraceroute

...r the following simple scenario (all subnets are /24): host1 <------> router/firewall <------> host2 10.0.0.1 10.0.0.2/192.168.91.222 192.168.91.202 Both host1 and host2 have default routes via router box. Let's do some pure routing (ie. no netfilter rules): host1:~# tcptraceroute 192.168.91.202 223 Tracing the path to 192.168.91.202 on TCP port 223, 30 hops max 1 10.0.0.2 0.404 ms 0.166 ms 0.141 ms 2 192.168.91.202 [closed] 0.436 ms 0.376 ms 0.322 ms Now let's add some NAT on router/fw: root@router:~# iptables -t nat -A PREROUTING -p tcp -d 192.168.91.202 --...

...DEBUG: if eth1: Don't Match (but seems to be UP) DEBUG: if eth2: OK using eth2, addr: 172.16.6.60, MTU: 1500 It supposedly binds to eth2. But tcpdump tells another story. Packets get sent out via the default route (eth1) with the IP from eth2 set as the source address. The same happens with tcptraceroute (tcptraceroute-1.5-0.beta7.el5.rf.i386.rpm). I have tried various routing policies, but I have yet to find a solution that works. I have used iptables to log the packets in the OUTPUT chain, but they arrive there with the interface already set to eth1. Can anyone help ? Regards, Mitja Mihelic

...mail server was an MS Exchange 5.5/SP4 server running on NT4.0/SP6a. This server was front ended by a Cisco PIX firewall. What I could never determine was "where" the packet was being dropped due to the ecn bit. For all I know, my customers ISP router could have been dropping it. FWIW: A tcptraceroute to port 25 worked. Steve Cowles

Hi, I am setting up a firewall on CENTOS 4.4. I have done default block iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP I have enabled ICMP to www.google.com iptables -A OUTPUT -p icmp -d 64.233.189.104 -j ACCEPT iptables -A INPUT -p icmp -s 64.233.189.104 -j ACCEPT Ping works fine as below [root at firebox rc.d]# ping 64.233.189.104 PING 64.233.189.104 (

...##################################### But when I try to trace the route of a packet with destination address such that according to ip rule table ALTER should be considered ... its not following the rule... its always following table Main... ##################################### ebox:100.254~# tcptraceroute -n 202.141.80.6 Selected device ppp0, address 10.0.0.1, port 40113 for outgoing packets Tracing the path to 202.141.80.6 on TCP port 80 (http), 30 hops max 1 10.0.0.254 0.333 ms 0.212 ms 0.210 ms 2 202.141.80.6 [open] 0.589 ms 0.591 ms 0.588 ms ######################################...

hi, I have a debian system with shorewall acting as a router between my adsl line and my local network. One of the things on that local network is my playstation, and I''m having trouble playing an online game with it - the game tries to access the internet, and then fails at the stage where it tries to find the game servers. The debian machine is 192.168.0.3, and the playstation is

Dear all, If I do cause offence by posting OT here I apologise in advance, I am however desperate for help and after posting on other forums without any ideas I know many networking experts will see this here and hope they can enlighten me. I will gladly donate some PayPal money to the person who can help. I have a leased line on 83.111.160.6 (/30 subnet, gw is 83.111.160.5), and they