From: Vikas K. <ka...@co...> - 2004-07-20 07:11:15
|
I think I know your problem now. You should enable ip forwarding in your kernel and also turn off icmp redirects. The fastest way would be to copy the snippet provided below onto /etc/sysctl.conf and then run sysctl -p -vikas #------------------------------------- ### /etc/sysctl.conf # Enable packet forwarding net.ipv4.ip_forward = 1 # Enables source route verification net.ipv4.conf.default.rp_filter = 1 # Enable the magic-sysrq key kernel.sysrq = 1 # Controls whether core dumps will append the PID to the core filename. # Useful for debugging multi-threaded applications. kernel.core_uses_pid = 1 # disable all redirecting # useful in forcing certain topologies # escpecially when a weak link exists net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.default.accept_redirects = 0 net.ipv4.conf.default.secure_redirects = 0 net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.all.secure_redirects = 0 #----------------------------------------- On Tue, 20 Jul 2004, Luo Yang wrote: ->Vikas: -> Thank you for your quick reply. -> ->When I tried to move all machines together, i.e. every node can see the ->other two nodes directly, The PING test between any two nodes was ->successful, so it is with SSH. But both failed when it requires a ->multi-hop. -> ->* There's another thing I don't know whether it's helpful. When I ->compile the AODV-UIUC source code, I got one warning message: ->================== ->aodv.cc: In member function `void aodv::resendRREQ(void*)': ->aodv.cc:1033: warning: taking address of temporary ->================== -> ->* I also checked the iptables with "iptables -L", the output is: -> [root@localhost /]# iptables -L -> Chain INPUT (policy ACCEPT) -> target prot opt source destination -> -> -> Chain FORWARD (policy ACCEPT) -> target prot opt source destination -> -> Chain OUTPUT (policy ACCEPT) -> target prot opt source destination -> ->The table is empty. Should I add some entry to the Chain FORWARD? -> ->Thanks ->Luo Yang -> ->From: Vikas Kawadia [mailto:ka...@co...] ->To: Luo Yang ->Cc: asl...@li... ->Subject: Re: [ASL] AODV-UIUC help -> -> -> ->There are too many things in a "system configuration: to just "kindly ->tell". -> ->As a first guess, I would suspect you have turned on a firewall ->(iptables) ->which is eating up all the ping packets. -> ->Can you ssh. -> ->-vikas -> -> ->On Tue, 20 Jul 2004, Luo Yang wrote: -> ->->Dear all: ->-> During last few weeks I was trying to setup AODV-UIUC on 2 ->notebooks ->->and 1 desktop. So far: ->->* The ASL-a-0.5, AODV-UIUC-0.5 are successfully compiled/installed ->->* each node able to find neighbours using HELLO and KRT updated ->->* When I tried to PING a unknown node(10.1.1.3) from node ->->10.1.1.4, the AODV program worked well, adding route to the node in ->->the KRT.I type the KRT of 10.1.1.4 below: ->->DEST Gateway Genmask Flags ->->Metric Ref Use Iface ->->10.1.1.3 10.1.1.2 255.255.255.255 UGH ->->0 0 0 eth1 ->->10.1.1.2 10.1.1.4 255.255.255.255 UGH ->->0 0 0 eth1 ->->127.0.0.0 * 255.0.0.0 ->->U 0 0 0 lo ->->default * 0.0.0.0 ->->U 0 0 0 tun ->-> ->-> The network topology is shown below: ->-> 10.1.1.4 <----------->10.1.1.2 <----------------> ->->10.1.1.3 ->-> ->-> Well, my problem is although the AODV works fine, but my data is ->not ->->transmitted as it should be. When I PING 10.1.1.3 from 10.1.1.4. I can -> ->->saw the KRT updated but there wasn't any reply received at 10.1.1.4. I -> ->->doubt it's due to the system configuration since routing table is ->->correct. ->-> ->-> I'm using RedHat 8.0 (kernel 2.4.18-14). Can u kindly tell me ->what ->->system configuration I should use to overcome the problem? ->-> ->-> Thank you for your kind help ->-> -> -> -- |