Dinh Tran

No, it doesnt exist. But I think we dont need that, right?

Hi, I want my machine 192.168.242.1 become a arp proxy for 192.168.242.2. I entered this command: arp -Ds 192.168.242.2 eth0 Using arp -n, I verify that 192.168.242.2 is displayed on the list. When I try to ping from another machine to 192.168.242.2. I can see a arp who-has arrived to 192.168.242.1 but no reply found. Anyone of you have experience about this please help me!!!!! Thanks a lot, Best regards, Dinh Tran

hichic, I really dont know why. May be it's the problem of Linux? Using an application, I can set up a tunnel. However, I have to wait about 5 minutes to have it worked. Before that the packets either do not go into the tunnel or get errors.

Hi, I want to set up a IPIP tunnel between 2 machines running Mandriva 2006. Machine A have IP address = 192.168.240.1 and machine B have 192.168.242.1. A: eth1 192.168.240.1 eth0 192.168.241.2 X: eth1 192.168.241.3 eth0 192.168.242.3 B: eth0 192.168.242.1 On machine A: ip tunnel add mode tunl1 local 192.168.240.1 remote 192.168.242.1 ip addr add dev tunl1 local 192.168.240.1 peer 192.168.242.1 ip link set tunl1 up On machine B: ip tunnel add mode tunl1 local 192.168.242.1 remote 192.168.240.1 ip addr add dev tunl1 local 192.168.242.1 peer 192.168.240.1 ip link set tunl1 up Using ifconfig, I see that tunl1 is up. But I can not ping from A to B or inverse. Could anyone help me what the probleme would be please? If you have any documents related to this topic, could you please send it to me too? I was searching for one online but I didn't really find anything. Thanks a lot, Best regards, Dinhh Tran

Hi, I got the answer from Chris and it worked for me so I post it here for everyone in case that you need. Thanks a lot Chris, Best regard, Dinh Tran Hi! First, do you need to do this, or can you use a hub/switch? (Perhaps you are doing it for the exercise, in which case, good on you!!) Each side of each PC must be on a different subnet: PC1 eth0 192.168.1.1 PC2 eth0 192.168.1.2 eth1 192.168.2.2 PC3 eth0 192.168.2.3 eth1 192.168.3.3 PC4 eth0 192.168.3.4 Subnet masks should all be 255.255.255.0 in this scenario. If you have an allocated pool of IP addresses you must use, then you will need to do subnetting - more complicated, but start off simple to begin with and use the private address range 192.168.x.x ... Each PC then needs to have either a routing protocol running or static routing set up, so that they know where to find each network. eg (on the command line): #PC1 route add default gw 192.168.1.2 eth0 # As long as there are no other network connections on this PC, that is all you need. This will send all unknown packets to PC2, which should route them onwards to the correct destination. #PC2 route add -net 192.168.3.0 netmask 255.255.255.0 gw 192.168.2.3 eth1 #This PC already knows about 192.168.1.x and 192.168.2.x because they are directly connected. We are telling it about 192.168.3.x, and how to get to it. If you have an Internet connection, you can add a default gateway using a similar line to PC1 - the interface and address will depend on which direction the data needs to go. #PC3 route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.2.2 eth0 # same comment as PC2 #PC4 route add default gw 192.168.3.3 eth0 # same comment as PC1 You can view the routing table with route -n It should look something like this on PC1: [root@shower chris]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.2 0.0.0.0 UG 10 0 0 eth0 The first line is the PC1's own interface, 2nd line is the local pseudo interface, 3rd line is the default gateway. The 3rd line means send any packet that has not matched line 1 or 2 to the device at 192.168.1.2 through eth0. When set up correctly, PC2 may look like something like this: [root@shower chris]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.3.0 192.168.2.3 255.255.255.0 U 10 0 0 eth1 192.168.2.0 0.0.0.0 255.255.255.0 U 10 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo #The default gateway (on PC2) may or may not be needed - if it is connecting to the Internet or #other networks through PC1 it will be something like: 0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth0 #Or if going through PC4: 0.0.0.0 192.168.2.3 0.0.0.0 UG 10 0 0 eth1 # note the address is the next hop - PC3 in this case. #You will also need a default gateway set up on the other PCs in this case, and set up routing individually to each subnet on PC 1 & 4... You will need to tell Iptables to allow packet forwarding too with this kind of thing: iptables -A FORWARD -s 192.168.1 -j ACCEPT needs to be added at the top of the forward chain You also need to put the following command at the beginning of /etc/sysctl.conf net.ipv4.ip_forward=1 to allow forwarding at all. So what is probably happening at the moment is you have a default gateway set up on PC2 & 3 sending the packets the wrong way, or no route at all. Hope this makes sense, or at least gives you a clue! Chris PS. I haven't tested it... :)

Hi, I have got stuck in this configuration for a while and I really dont know how to make it work. Please help me to solve out this problem. I have the following system: PC1==========PC2=============PC3=============PC4 eth0 eth1 eth0 eth1 eth0 eth0 x.240.5 x.240.1 x.240.2 x.240.3 x.242.3 x.242.1 I could not ping from PC1 and PC2 to PC3 and PC4. So, at the beginning, I tried to run this PC2============PC3==============PC4 eth1 eth1 eth0 eth0 x.240.2 x.240.3 x.242.3 x.242.1 Using the configuration given on http://www.iwpcs.co.uk/simple_net_setup.html for PC2 and http://www.iwpcs.co.uk/ics.html for PC3, I made it worked. Then I added the PC1, from PC1 I can not ping PC2, PC3 and PC4. From PC1, I ping 240.1 on eth1 of PC2 and then watch the tcpdump on that same eth1. I got a "arp who-has 192.168.240.1 tel 192.168.240.5". Could you help me out please? I wonder if this is the problem of iptables but I am really not sure. Thanks a lot and have a nice day, Best regards, Dinh Tran

Hi, Sorry for keep asking about the same problem. My 2 LAN connecting to each other can be represented as below: Windows=================Mandriva1====================Mandriva2 eth1 eth0 eth0 192.168.240.2 192.168.240.1 192.168.242.3 192.168.242.2 From 240.2, I can ping successfully 240.1 and 242.3 but not 242.2. Using tcpdump, I can see the ICMP echo request coming from 240.2 at 242.2 machine, then 242.2 send out a "arp who-has 192.168.240.2 tell 192.168.242.1". 242.2 machine doesnt send back the echo reply. I already set rp_filter to 0. From 242.2, I dont succeed to ping 240.2 neither. I get a Destination Host Unreachable. Using tcpdump, the only traffic displayed is: "arp who-has 192.168.240.2 tell 192.168.242.1". Pinging 240.1 and 242.3 is with success from 242.2 Actually, I am running an application, in which these 3 machines communicate to each other using ICMP and UDP. After the initiation phase, the application should establish an ipip tunnel between 240.1 and 242.2. And I'm supposed to be able to ping between these 3 machines but I got the same error as I described above. Thus, I want to firstly succeed to ping normally from one machine to the others, which still doesnt work for me. Could you help me out please? Thanks a lot for your help, Best regards, Dinh Tran

Thanks, I got shorewall and iptables all off. But does it exist any other firewall please? Because I run a udp client and server on these 2 mandriva machines (code from here: http://sage.mc.yu.edu/kbeen/teaching/netwo...es/sockets.html ), but server can never receive message from client. However using tcpdump, I see that the packet udp already arrived to server. Would this be a problem of firewall? Thanks, Best regards, Dinh Tran

Hi, Bonjour, :D :) thanks so much for all your replies. After disactivating firewall on windows machine, I can ping it. So may be the problem comes from firewall. Concerning the 2 Lan connecting to each other, I can not ping. But using my application, I checked that the communication between Desktop2 and laptop was ok, between the 2 desktops was ok too. I am not yet able to check the one between laptop and desktop 1 :(. I'll let you know if I succeed. If so, it means it's really problem of firewall. By the way, how can we disable all the firewall please? is it in /proc/sys/net/ipv4/conf/all/ and we have to change all the parameter related to firewall to 0? One thing so strange is that I didn't use cross over (thanks for the word :D ) cables for both connexions, but straigh through ones. Thanks again :)

Yes I do have red lights on the 2 desktops if they are connected directly to each other. But If I connect them to internet, the lights are green. I checked the cables and nothing's wrong with them. Do you know any other reasons please?? :( I dont have a router and I dont know if I can get one. Thanks, Dinh Tran

Hi, I succeed to configure a mandriva as a router for internet sharing but not for connexion between 2LAN. And here's the system that I want to have: Desktop 1 Mandriva <--->Desktop 2 Mandriva with 2 ethernet cards <----> Laptop winXP 192.168.18.1 <--->192.168.18.29 192.168.240.1<---->192.168.240.2 From desktop 1, I can not ping anything, even 192.168.18.29 From desktop 2, I can not ping anything including 192.168.18.1 and 192.168.240.2 From laptop, I can ping 192.168.240.1, 192.168.18.29 but not 192.168.18.1 Between desktop 1 and 2; desktop 2 and laptop, i use non-crossed cables (actually i tried also the crossed ones but it doesnt help) Previously, for internet sharing, my system is Internet <----->Desktop 2 Mandriva with 2 ethernet cards <----> Laptop winXP 192.168.18.1 <--->192.168.18.29 192.168.240.1<---->192.168.240.2 non-crossed cable between desktop 2 and laptop. From the laptop, I can ping any IP and go on internet web pages. But from desktop 2, I can not ping the laptop, even after "route add -net 192.168.240.0 netmask 255.255.255.0 gw 192.168.240.1". Is it normal please? Thanks a lot for helping me out and tell me which cable I should use please, crossed or non crossed one? I am confused ... Best regards, Dinh Tran

hiihih, it worksssssss fine. I can now go on internet from the other machine :D So I think it's really the problem of installing wrong version of Mandriva. I still have to force to install caching-nameserver as you told me but the rest is installed automatically with the dvd. Thanks thanks a lot for your help, Have a nice day :) Dinh Tran

:(( my machine was installed with a Mandriva for i586 and not Mandriva x86_64. hichic, I think that's the problem. I will make it installed again with the right one and let you know if it works :D Thanks thanks a lot ianw1974 Dinh Tran

huhuhuuhuh how terrible it is :cry: I succeed to install caching-nameserver. Thanks a lot. Then the next step is installing dhcp server I downloaded the package and tried to install. I got the error: [root@localhost Téléchargement]# rpm -ivh dhcp-server-3.0.3-3mdk.x86_64.rpm attention: dhcp-server-3.0.3-3mdk.x86_64.rpm: Entête V3 DSA signature: NOKEY, key ID 26752624 erreur: Dépendances requises: libc.so.6()(64bit) est nécessaire pour dhcp-server-3.0.3-3mdk.x86_64 libc.so.6(GLIBC_2.2.5)(64bit) est nécessaire pour dhcp-server-3.0.3-3mdk.x86_64 libc.so.6(GLIBC_2.3.4)(64bit) est nécessaire pour dhcp-server-3.0.3-3mdk.x86_64 libc.so.6(GLIBC_2.3)(64bit) est nécessaire pour dhcp-server-3.0.3-3mdk.x86_64 liblber-2.3.so.0()(64bit) est nécessaire pour dhcp-server-3.0.3-3mdk.x86_64 libldap-2.3.so.0()(64bit) est nécessaire pour dhcp-server-3.0.3-3mdk.x86_64 I found there's existing libd.so.6 for i686 and add the path to LD_LIBRARY_PATH but it doesnt help. [root@localhost lib]# locate libc.so.6 /lib/i686/libc.so.6 /lib/tls/libc.so.6 /lib/libc.so.6 [root@localhost Téléchargement]# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib/i686/ [root@localhost Téléchargement]# Then, I tried to install glibc-2.3.4-2.x86_64.rpm. [root@localhost Téléchargement]# rpm -ivh glibc-2.3.4-2.x86_64.rpm attention: glibc-2.3.4-2.x86_64.rpm: Entête V3 DSA signature: NOKEY, key ID 652e84dc erreur: Dépendances requises: glibc-common = 2.3.4-2 est nécessaire pour glibc-2.3.4-2.x86_64 shadow-utils < 2:4.0.3-20 entre en conflit avec glibc-2.3.4-2.x86_64 glibc < 6:2.3.3-2mdk entre en conflit avec sash-3.7-3mdk.i586 [root@localhost Téléchargement]# ok, then it seems that sash is installed but with a wrong one (i586). I tried to change to the x86_64 one [root@localhost Téléchargement]# rpm -ivh sash-3.7-3mdk.x86_64.rpm Préparation... (10########################################### [100%] le paquetage sash-3.7-3mdk est prévu pour une archicture x86_64 paquetage sash-3.7-3mdk déjà installé le fichier /sbin/sash de l'installation de sash-3.7-3mdk entre en conflit avec le fichier du paquetage sash-3.7-3mdk [root@localhost Téléchargement]# [root@localhost Téléchargement]# rpm -q sash sash-3.7-3mdk I tried to uninstall the existing sash. But the displayed error is: [root@localhost Téléchargement]# rpm -e sash erreur: Dépendances requises: sash est nécessaire pour (déjà installé) basesystem-10.1-5mdk.i586 [root@localhost Téléchargement]# huhuhuhu it seems lots of things are installed with i586. What should I do please? Thanks thanks alot for your help, Dinh Tran

I got the same error message while trying to install the downloaded package and mandriva package. Here"s the error message for mandriva one: [root@localhost Téléchargement]# urpmi caching-nameserver Certains paquetages demandés ne peuvent pas être installés : caching-nameserver-9.2-2mdk.noarch (car bind[*][>= 9.2.3-0.rc2.1mdk] est non satisfait) Continuer ? (O/n) o [root@localhost Téléchargement]# Some asked packages can not be installed: caching-nameserver-9.2-2mdk.noarch (because bind[*][>= 9.2.3-0.rc2.1mdk] is not satisfied) Continu ? (Y/n) Y So actually we can not force to install, 'cause I choose to continue but nothing happened