|
From: Saverio <sa...@an...> - 2008-01-27 18:02:25
|
Thank you for the reply, Asanga.
I've installed successfully UobwinAODV on three PCs and it works well... but
I've the following problem:
pc "A" can ping pc "B", but pc "B" can't ping pc "A".
Why this?
I follow these steps for all the PCs:
- stop all firewall/antivirus
- connect to AODV through Windows Interface, in order to acquire IP
address(for all PCs, IP is 192.168.1.x, without gateway)
- start UoBWinAODV in console mode
Is there anything wrong in these steps?
Moreover, I don't see new route entry in UobWinAODV output...
I hope you could help me.
In the following you can find my configurations
Kind regards.
Saverio
Here "route print" output (151.x.x.x is my internet connection):
===========================================================================
Elenco interfacce
0x1 ........................... MS TCP Loopback interface
0x2 ...00 15 e9 32 02 bd ...... D-Link AirPlus DWL-G520 Wireless PCI
Adapter(rev
.B) - Miniport dell'Utilita' di pianificazione pacchetti
0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfac. Metric
0.0.0.0 0.0.0.0 151.33.112.216 151.33.112.216 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
151.23.225.12 255.255.255.255 151.33.112.216 151.33.112.216 1
151.33.112.216 255.255.255.255 127.0.0.1 127.0.0.1 50
151.33.255.255 255.255.255.255 151.33.112.216 151.33.112.216 50
192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1 30
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 30
224.0.0.0 240.0.0.0 192.168.1.1 192.168.1.1 30
224.0.0.0 240.0.0.0 151.33.112.216 151.33.112.216 1
255.255.255.255 255.255.255.255 151.33.112.216 151.33.112.216 1
255.255.255.255 255.255.255.255 192.168.1.1 192.168.1.1 1
Gateway predefinito: 151.33.112.216
===========================================================================
Route permanenti:
Nessuno
Here "Factotum.exe /enum" output:
Factotum of UoB WinAODV Protocol Handler
Copyright (c) 2004 ComNets, University of Bremen
Copyright (c) 2003 Printing Communications Assoc., Inc. (PCAUSA)
Copyright (c) 1982, 1986, 1993 The Regents of the University of California.
All rights reserved.
Driver Bindings:
"\Device\{29EA3AF8-8C50-4560-B2FA-56CEB52A261C}"
"\DEVICE\{3D0B6DEE-7CB7-49B0-87DD-84A2A9EBD041}"
Description: " D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B)"
Medium: 802.3; Mac address = 00-15-E9-32-02-BD
"\Device\{D780BB03-EE50-485F-A8B4-EC5C86CF038E}"
"\DEVICE\NDISWANIP"
Description: " NdisWan Adapter"
Medium: 802.3; Mac address = DA-F6-20-52-41-53
Here UobWinAODV.cfg file
ExecutionMode=Console
IPVersion=IPv4
IPAddress=192.168.1.1
##IfaceName=\Device\{CFC55494-0CF2-4219-8721-BE643975F5F4}
IfaceName=\DEVICE\{3D0B6DEE-7CB7-49B0-87DD-84A2A9EBD041}
#GatewayIPAddress=192.168.1.1
LoggingStatus=Yes
LoggingMode=File
LoggingLevel=4
LogFile=.\UoBWinAODV.log
OnlyDestination=Yes
GratuitousRREP=No
RREPAckRequired=no
##IPAddressMulticast=224.10.10.100
IPAddressMulticast=255.255.255.255
RERRSendingMode=unicast
DeletePeriodMode=Hello
RouteDiscoveryMode=non-ERS
PacketBuffering=Yes
PrintFrequency=1000
ActiveRouteTimeout=6000
AllowedHelloLoss=3
HelloInterval=1000
LocalAddTTL=2
NetDiameter=20
NodeTraversalTime=40
RERRRatelimit=10
RREQRetries=5
RREQRateLimit=10
TimeoutBuffer=2
TTLStart=5
TTLIncrement=2
TTLThreshold=15
-----Messaggio originale-----
Da: Asanga Udugama [mailto:ad...@co...]
Inviato: domenica 27 gennaio 2008 12.37
A: 'Saverio Calvano';
Oggetto: RE: [Aodvimpl] Help about UobWinAodv
Hello Saverio,
I see that you have downloaded and installed the UoBWinAODV. The site was
down for sometime due to maintenance work.
To make UoBWinAODV work, a communication session must start. One simple
communication tool is the ping command. Try pinging one node from another.
If this does not work, it may be due to configuration issues. You can send
me the following information so that I can look to see if you have any
problems with the way you have configured UoBWinAODV.
- output of factotum /enum
- output of ipconfig /all and route print
- uobwinaodv.conf
- uobwinaodv.log
Kind regards,
Asanga
> -----Original Message-----
> From: aod...@li... [mailto:aodvimpl-
> pub...@li...] On Behalf Of Saverio Calvano
> Sent: Friday, January 25, 2008 10:01 AM
> To: aod...@li...
> Subject: [Aodvimpl] Help about UobWinAodv
>
> Hi everyone,
>
> I'm trying to use UobWinAODV in order to make a mesh network among 3
> nodes.
>
> I've installed it on all my nodes.
> I run UobWinAODV application but the nodes cannot see each other (I
> stopped all firewall and antivirus).
>
> Couls anyone explain me how to configure this application in order to
> make a mesh network?
>
> Thanks in advance
>
>
> Regards
>
> Saverio
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Aodvimpl-public mailing list
> Aod...@li...
> https://lists.sourceforge.net/lists/listinfo/aodvimpl-public
|