🚀 go-pugleaf

On Sat, 17 Nov 2001 09:50:04 +0000, alex wrote:

> hi
> 
>> Only you can say in the IP are registered to go through the ISP or
>> not. The routing of the those may not necessarily be the same but
>> it should hit the 213.14.46.4 interface at some point.
> all ip's ar registered for my isp... !? yes i think the way should
> hit my router on this way, but it dosn't. if i tracert to
> 213.14.46.4 everything is ok. if i tracert to 217.10.0.34 there is a
> timeout in the way and i never get the host 213.14.46.4 on this
> way... may this caused on firewall rules? i think if firewall is
> blocking something here there schould be 213.14.46.4 aus the last
> reachable host - and after this host a timeout - or not?
> 

tried a traceroute from here, there seems to be a loop 

17  hgr2-core1-fa4-1-0.atlas.icix.net (165.117.59.10)  109.843 ms  
    110.427 ms  107.663 ms
18  207.86.242.66 (207.86.242.66)  703.900 ms *  665.504 ms
19  212.29.64.146 (212.29.64.146)  658.485 ms  655.103 ms  666.427 ms
20  212.29.64.10 (212.29.64.10)  687.597 ms  702.774 ms  679.887 ms
21  212.29.74.11 (212.29.74.11)  678.461 ms  686.438 ms  678.867 ms
22  212.29.74.1 (212.29.74.1)  685.816 ms  695.302 ms  694.573 ms
23  212.29.74.11 (212.29.74.11)  704.724 ms  680.603 ms *
24  212.29.74.1 (212.29.74.1)  676.989 ms  655.938 ms  685.517 ms
25  212.29.74.11 (212.29.74.11)  689.404 ms  687.851 ms  800.080 ms
26  212.29.74.1 (212.29.74.1)  688.184 ms  690.088 ms  690.977 ms
27  212.29.74.11 (212.29.74.11)  688.425 ms  710.261 ms  697.249 ms


>> I suspect the firewall rules are blocking you.  The routing table
>> sounds ok but you haven't posted the route -n output.  Get the
>> firewall config.
> i will try to post it later this day... for this i need to go to the
> ISC... a "route" gives a autput something like
> 
> 213.14.46.0  * MASK 255.255.255.248.... eth0 217.10.0.32 *  MASK
> 255.255.255.240.... eth1 217.10.0.48 * MASK 255.255.255.240.... eth2
> default 213.14.46.1...
> 
> looks ok - or not?

initially yes, although it's better to get the route -n output.

> 
>> In you have linux 2.2 check ipchains -L if you have 2.4 then run
>> iptables -L
> i've unloaded the rules by "SuSEfirewall2 stop" and activate only
> the ip_forwarding for testing! is this enough or is there a need to
> turn on/off another things...?

no, depending on SuSEfirewall2 the rules may not be open enough for
forwarding, that is why you want the ipchains -L -n (2.2) or
iptables -L -n (2.4) output.   The -n is only to display the numbers.

karl.