SEARCH  

NEWS

2010.10.06:11:36:28
Ustawowe wsparcie rozwoju sieci telekomunikacyjnych
Ustawa o wspieraniu rozwoju usług i sieci telekomunikacyjnych, która weszła w życie 15 lipca br., wprowadza szereg nowatorskich rozwiązań, mających na celu przyspieszenie rozwoju i upowszechnienie usług telekomunikacyjnych w Polsce. Doprowadzi do obniżenia kosztów przedsiębiorców telekomunikacyjnych i odbiorców tych usług (tzw. użytkowników końcowych).

 

messageID:599260007246
author:Jee JZ
title:Re network setup help
On Sunday 11 April 2004 12:33 am, Jee J.Z. wrote: Hi Antony, Thanks for getting the spelling right - lots of people round here dont :) Look at the routing table of each machine the packets are going through, and then the replies trying to get back again, and see if (a) there is a path, and (b) it makes sense. Both PC2 and PC3s routing look like: Destination Gateway Genmask Flags Metric Ref Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 eth1 144.32.xxx.0 0.0.0.0 255.255.254.0 U 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo 0.0.0.0 144.32.xxx.yyy 0.0.0.0 UG 0 0 eth0 Okay, Im assuming that 144.32.xxx.yyy is not the address of PC1 - its something else which is connected to your switch - however thats not too important here. Heres what I think is going on: PC1 has a simple routing table saying "network 144.32.xxx.0/23 is on eth0, and the deafult gateway is 144.32.xxx.yyy". That means if you ping 192.168.0.2 from PC1 it will send the packets to the default gateway :( Set a network route on PC1 to tell it how to find the 192.168.0.0/24 network, via PC2 as a router: route add -net 192.168.0.0 netmask 255.255.255.0 gw 144.32.xxx.b where 144.32.xxx.b is the IP address on PC2/eth0 Once you have done that I think the pings will work, however they will not work the way you would like them to :) An echo request packet will come from 144.32.xxx.a (PC1/eth0) to 192.168.0.2 and get routed (by your new routing table entry on PC1) via 144.32.xxx.b, where PC2 will decide "192.168.0.2? Oh, thats on my eth1", and will send it to PC2. However, if PC2/eth0 is still operational and plugged in, it will think "I have to send an echo response packet to 144.32.xxx.a, and thats on this subnet connected to my eth0", so it will send the reply packet out through eth0. This will actually work for pings, but its not the way you want TCP packets to flow (remember that pings are ICMP packets), and it certainly wont work once you start doing nat on PC2 (which I assume, for some reason, that you do want to do?). However, I still remain puzzled about why you have this crazy setup in the first place, and what youre trying to achieve by sending pings from PC1 to PC3 via PC2, so add the routing table entry to PC1, check whether a ping works (with all the cables plugged in, so all the paths shown on your original diagram are available), and then try to explain to us why you are doing things this way and what you want to achieve. Regards, Antony. -- If at first you dont succeed, destroy all the evidence that you tried. Please reply to the list; please dont CC me.
Index