Dear all,

I'm trying to run my own routing protocol in aqua-sim, but i face a problem.

The packet type gets changed during transmission. What might cause that problem? and what are the packet headers (in addition with common, Ip and my own routing header) that I need to include in the tcl file. if I'm using
Channel/UnderwaterChannel as a channel type,
Propagation/UnderwaterPropagation as an Underwater propagation model,
Phy/UnderwaterPhy as an Underwater physical layer,
Mac/UnderwaterMac/BroadcastMac as Mac type,
Queue/DropTail/PriQueue as an Interface queue type.

Thank you in advance.

Does your routing protocol conform to a known standard or have you trained all the hardware to accept your new protocol?

Sorry, I couldn't get your question. I'm new to the simulation.

Could you please rephrase it?

Now worries, Faiza, my written English to closely mirrors my spoken English so if you're not a native speaker, I tend to be confusing, let me know anytime that's a problem.

TCP/IP4 (for example) contains a known routing element that all hardware on the TCP/IP4 network understand. The routing "protocol" encapsulates in the packet header, every machine that touches the packet manipulates the information in the header based on that shared understanding and it's the aggregate of that information that allows the routing protocol associated with TCP/IP4 to route.
If you create your own protocol and modify the meaning of the bits in the header of your packets, no other machine on your network will understand the changes unless you modify their programming to understand it. They will, most likely, just treat the packet like TCP/IP4 and mangle the custom header, returning a TCP/IP4 packet back to you (albeit, with a mangled header).
In your original post that sounded to me like what was happening.

1 members found this post helpful.

#2, #4 @dijetlo.

`Aqua-Sim´ is a simulator : Network Simulator ns-2.31 + the underwater code.
Aqua-Sim http://obinet.engr.uconn.edu/wiki/index.php/Aqua-Sim
Ns2 http://nsnam.isi.edu/nsnam/index.php/User_Information

I.e. not hardware based.

-

@knudfl

#1
That suggested to me his new protocol wasn't fully implemented. I got off onto the topic of copper networks because it was easier for me to explain why a failure to fully import the new protocol might be causing this problem.
#4

The problem solved by adding TCP or RTP(which can be used as a UDP) header in the tcl file.

Thank you

The question now is that in my packet header, I declare some string variables,
but when I create a packet and try to assign them values I get Segmentation fault (core dump) error.

How it can be solved, please?

I agree with dijetlo do so and see what will be the result.

The packet is being "formed" on the adapter, Faiza.
It's my understanding the packet interactions are handled at the machine level by specifically designed hardware on the adapter. I'd check to make sure what your doing is something that hardware can understand and accommodate. You can make a header so large it pops the packet buffer in the adapter. Keep in mind, when the network is active, that adapter is going to be handling an awful lot of packets/per second.
The facility exists in Linux to inject data into existing variables in outbound TCP/IP packets and to read the custom values from the inbound, so the basis of what your trying is solid. Before I created new variables, I'd try to better utilize the ones that already exist in the packet and watch your bit counts in the header, 1 bit over is going to give you the same result as 100 bits over, just not as quickly.