Les Mikesell escribió:
On 12/19/10 1:45 PM, Jose Maria Terry Jimenez wrote:
I wanted the reverse path. Traceroute from the 192.168.236.80 box back to the
fedora address. It doesn't make sense that it can return packets without a
route going through the Centos box.
Hello
This arrive
Andrej Moravcik escribió:
Hello Jose,
from the picture you provided the situation looks pretty simple.
- you have enabled IP forwarding on router, I recommend you to put it
into /etc/sysctl.conf for persistence.
- you have configured firewall rules on router to allow forwarding
traffic from
Hello Jose,
from the picture you provided the situation looks pretty simple.
- you have enabled IP forwarding on router, I recommend you to put it
into /etc/sysctl.conf for persistence.
- you have configured firewall rules on router to allow forwarding
traffic from left to right subnet. You ca
El 19/12/2010, a las 23:15, Les Mikesell escribió:
> On 12/19/10 4:08 PM, José María Terry Jiménez wrote:
>> Les Mikesell escribió:
>>> On 12/19/10 2:30 PM, Jose Maria Terry Jimenez wrote:
>>>
This doesn't make much sense without a route. Can you try a
traceroute to the
On 12/19/10 4:08 PM, José María Terry Jiménez wrote:
> Les Mikesell escribió:
>> On 12/19/10 2:30 PM, Jose Maria Terry Jimenez wrote:
>>
>>> 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/
Les Mikesell escribió:
On 12/19/10 2:30 PM, Jose Maria Terry Jimenez wrote:
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
Hope it helps (all addresses are 192.168. Trimmed to compac
On 12/19/10 2:30 PM, Jose Maria Terry Jimenez wrote:
>
>
> 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?
>>
> Hope it helps (all addresses are 192.168. Tri
El 19/12/10 21:17, Michel van Deventer escribió:
> Hi,
>
> The Fedora box (1. network):
> [j...@idi ~]$ ping 192.168.236.80
> PING 192.168.236.80 (192.168.236.80) 56(84) bytes of data.
> 64 bytes from 192.168.236.80: icmp_req=1 ttl=64 time=1.61 ms
> 64 bytes from 192.168.236.80:
Hi,
> >>> The Fedora box (1. network):
> >>> [j...@idi ~]$ ping 192.168.236.80
> >>> PING 192.168.236.80 (192.168.236.80) 56(84) bytes of data.
> >>> 64 bytes from 192.168.236.80: icmp_req=1 ttl=64 time=1.61 ms
> >>> 64 bytes from 192.168.236.80: icmp_req=2 ttl=64 time=0.684 ms
> >>> [j...@idi ~]$
On 12/19/10 1:45 PM, Jose Maria Terry Jimenez wrote:
>
> El 19/12/2010, a las 20:34, Les Mikesell escribió:
>
>> On 12/19/10 12:31 PM, Jose Maria Terry Jimenez wrote:
>
> First make sure that you can ping/access those 'other' services from the
> centos
> box with 2 nics. It shoul
El 19/12/2010, a las 20:34, Les Mikesell escribió:
> On 12/19/10 12:31 PM, Jose Maria Terry Jimenez wrote:
First make sure that you can ping/access those 'other' services from the
centos
box with 2 nics. It should source from the .236 interface and 'just
work'. If
>
On 12/19/10 12:31 PM, Jose Maria Terry Jimenez wrote:
>>>
>>> First make sure that you can ping/access those 'other' services from the
>>> centos
>>> box with 2 nics. It should source from the .236 interface and 'just
>>> work'. If
>>> not, you have firewalls or something else blocking traffic
El 19/12/10 20:23, Les Mikesell escribió:
> On 12/19/10 12:15 PM, Jose Maria Terry Jimenez wrote:
>>> First make sure that you can ping/access those 'other' services from the
>>> centos
>>> box with 2 nics. It should source from the .236 interface and 'just
>>> work'. If
>>> not, you have fire
On 12/19/10 12:15 PM, Jose Maria Terry Jimenez wrote:
>
>>
>> First make sure that you can ping/access those 'other' services from the
>> centos
>> box with 2 nics. It should source from the .236 interface and 'just work'.
>> If
>> not, you have firewalls or something else blocking traffic.
>>
>> First make sure that you can ping/access those 'other' services from the
>> centos
>> box with 2 nics. It should source from the .236 interface and 'just work'.
>> If
>> not, you have firewalls or something else blocking traffic. When you route
>> other traffic from the .1 network,
El 19/12/2010, a las 19:01, Les Mikesell escribió:
> On 12/19/10 11:07 AM, Jose Maria Terry Jimenez wrote:
>> Hello All
>>
>> First, sorry by my poor english, hope you understand me :-)
>>
>> I have a problem, i don't understand or don't know how to solve
>>
>> I need to interconnect 2 network
On 12/19/10 11:07 AM, Jose Maria Terry Jimenez wrote:
> Hello All
>
> First, sorry by my poor english, hope you understand me :-)
>
> I have a problem, i don't understand or don't know how to solve
>
> I need to interconnect 2 networks with different numbers. One is
> 192.168.236.0/24 the other 192
Hello All
First, sorry by my poor english, hope you understand me :-)
I have a problem, i don't understand or don't know how to solve
I need to interconnect 2 networks with different numbers. One is
192.168.236.0/24 the other 192.168.1.0/24. Mainly i need to access services in
the 236. from th
18 matches
Mail list logo
