|
|
|
|
|
|
|
|
|
|
Re: TTCN - Router [message #1803987 is a reply to message #1803552] |
Thu, 14 March 2019 16:25   |
Eclipse User |
|
|
|
Hi Elemer,
If I were to send a ICMP Echo to the OSPF router, the TTCN-3 structure representing an OSPF packet and test port would be as followed.
would I need to create a similar protocol packet and test ports for BGP ?
Regards - David
type record OSPFPacketType
{
UInt8 Version,
UInt8 Type,
UInt16 PacketLength,
UInt32 RouterID,
UInt32 AreaID,
UInt16 Checksum,
UInt8 InstanceID,
UInt8 Reserved,
octetstring PacketBody
};
// A port type used for communicating with an OSPF router
type port OSPFPort message
{
inout OSPFPacketType;
}
|
|
|
Re: TTCN - Router [message #1804089 is a reply to message #1803987] |
Mon, 18 March 2019 03:55   |
Eclipse User |
|
|
|
Hi David,
first , some architectural advice:
it's always a good idea to separate the different protocol stacks:
-you will need at least two such stacks: an ICMP/IP/L2 and an OSPF/IP/L2; this means you will need two PTC's , one implementing ICMP behaviour , with an icmp port translated to LANL2,
and one implementing OSPF behaviour, with an ospf port translated to LANL2;
-for the first you can use the already available ICMP and IP protocol modules and the LANL2 test port
-for the second you will have to write an OSPF protocol module (with RAW codec instructions) , plus use the existing IP PM, and LANL2 test port
If you want to add BGP, you need to implement BGP types ( with RAW) and add a third protocol stack/component similar with the above
You should preferably use types declared in titan.ProtocolModules.COMMON/src/General_Types.ttcn
already decorated with RAW attributes.
The MTC can be used to orchestrate the behaviour of the two(three) components wia internal test ports.
I hope this helps.
BR
Elemer
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 1.26409 seconds