<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Les Mikesell escribió:
<blockquote cite="mid:4D0E7939.6080705@gmail.com" type="cite">
<pre wrap="">On 12/19/10 2:30 PM, Jose Maria Terry Jimenez wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">This doesn't make much sense without a route. Can you try a traceroute to the
fedora box address from the 192.168.236.80 box to see how/why it gets there</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
<blockquote cite="mid:4D0E7939.6080705@gmail.com" type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Hope it helps (all addresses are 192.168. Trimmed to compact the schema):
---------- ---------- -----------
! 1.3 !------!1.100 ! !gw 236.21!
! gw 1.1 ! ! ! 236.74!-----! 236.80 !
---------- ! ! gw 1.1 ! ! -----------
! ---------- !
! !
[Router1] [Router2]
Router 1 is a PFSense and its IP is 192.168.1.1
Router 2 is "something" (it is managed by other person, and i think is
somekind of win server) and IP is 192.168.236.21
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->
This still doesn't explain why the 192.168.236.80 box can return packets to the
fedora at 192.168.1.3 when you said it didn't have a route going through
192.168.236.74. Can you check what routes you do have on 192.168.236.80 and
traceroute from there to 192.168.1.3?
</pre>
</blockquote>
Apologies by confusing you. I forgot that "the other" CentOS had 2
NICs, this is the machine where i began these tests. It's in a remote
site and now when listing the routes remembered that.<br>
<br>
It's conected to the 1. network with a second NIC and IP:
192.168.1.102. Replies must be return by that iface, really?<br>
[root@control ~]# route<br>
Kernel IP routing table<br>
Destination Gateway Genmask Flags Metric Ref Use
Iface<br>
192.168.1.0 * 255.255.255.0 U 0 0 0
eth1<br>
192.168.236.0 * 255.255.255.0 U 0 0 0
eth0<br>
169.254.0.0 * 255.255.0.0 U 0 0 0
eth0<br>
default 192.168.236.21 0.0.0.0 UG 0 0
0 eth0<br>
<br>
I Configured a printer in the 236. network to use 192.168.236.74 as
gateway and now i can access it from 1. Thanks.<br>
[jose@IDi ~]$ ping 192.168.236.74<br>
PING 192.168.236.74 (192.168.236.74) 56(84) bytes of data.<br>
64 bytes from 192.168.236.74: icmp_req=1 ttl=64 time=0.276 ms<br>
64 bytes from 192.168.236.74: icmp_req=2 ttl=64 time=0.245 ms<br>
<br>
Thanks again<br>
<br>
Best
<br>
<br>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<br>
Scanned with <a href='http://www.copfilter.org'>Copfilter</a> Version 0.84beta3a (<a href='http://memberwebs.com/nielsen/software/proxsmtp'>ProxSMTP</a> 1.6)<br>
AntiVirus: <a href='http://www.clamav.net'>ClamAV</a> 0.95.2/12415 - Sun Dec 19 04:26:57 2010<br>
by Markus Madlener @ <a href='http://www.copfilter.org'>http://www.copfilter.org</a><br>
<br>
</body>
</html>