[Fwd: [Omnetpp-l] Broadcast in INETMANET for Omnet 4 fixed?]

Peter Staab

unread,

Oct 23, 2009, 6:06:16 AM10/23/09

to omne...@omnetpp.org

To be more specific: I am using an 802.11 network with IP4.

Regards,

-------- Original-Nachricht --------

Betreff:	[Omnetpp-l] Broadcast in INETMANET for Omnet 4 fixed?
Datum:	Fri, 23 Oct 2009 11:44:41 +0200
Von:	Peter Staab <pixs...@gmx.net>
Antwort an:	omn...@googlegroups.com
An:	omne...@omnetpp.org

Hello,

The inetmanet version for OMNet 3.3 had to be fixed to get broadcast
working [1].
Is the latest inetmanet version for OMNet 4 already fixed? If yes, how
can I broadcast e.g. a UDP packet? Sending to IPAddress::ALLONES_ADDRESS
does not work.

Regards,


[1] http://www7.informatik.uni-erlangen.de/~sommer/omnet/

Alfonso Ariza

unread,

Oct 23, 2009, 6:26:55 AM10/23/09

to omn...@googlegroups.com

The Ip code sends the broadcast packets but limit the numbers of hops to 1

Peter Staab

unread,

Oct 23, 2009, 6:37:55 AM10/23/09

to omn...@googlegroups.com

Hi,

Yes, that's clear. I mean, the problem is:
Host1 -- (Unicast UDP) --> Host2 works
Host1 -- (Broadcast UDP) --> Host2 does not work. So the hosts are in range.

Regards,

Alfonso Ariza schrieb:

Alfonso Ariza

unread,

Oct 23, 2009, 6:50:11 AM10/23/09

to omn...@googlegroups.com

Ok. I suppose where the problem is. The IP broadcast mechanism needs the output interface. If the interface is not indicated the IP code deletes the packet.

Peter Staab

unread,

Oct 23, 2009, 10:49:19 AM10/23/09

to omn...@googlegroups.com

Can you give me a hint how to "set" the output interface for the broadcast mechanism?

Alfonso Ariza schrieb:

Alfonso Ariza

unread,

Oct 23, 2009, 11:43:00 AM10/23/09

to omn...@googlegroups.com

In UDPControlInfo you must indicate the interface. The method is setInterfaceId(). The application can't send a broadcast packet

Peter Staab

unread,

Oct 23, 2009, 11:56:37 AM10/23/09

to omn...@googlegroups.com

I have tried this but without success.
The interface is "wlan" and its id is "1".

Alfonso Ariza schrieb:

Alfonso Ariza

unread,

Oct 23, 2009, 1:36:34 PM10/23/09

to omn...@googlegroups.com

It's not the index, the interface id , the first id is 100 (file InterfaceTable.cc, macro INTERFACEIDS_START)

The id should be 101 in your implementation.

Peter Staab

unread,

Oct 23, 2009, 2:01:02 PM10/23/09

to omn...@googlegroups.com

Thank you very much. Now it's working.
If there is an inetmanet wiki/faq somewhere, then I think this info should be added...

Alfonso Ariza schrieb:

Guillaume

unread,

Nov 11, 2009, 5:17:13 AM11/11/09

to omnetpp

Hi all,

Peter, can you send me the code you use, as I don't get my broadcast
application to work, even by following the advices in this thread.

I subclassed UDPBasic app and want to send a beacon packet. Here is my
relevant code:

void UDPChatApp::handleMessage(cMessage *msg)
{
// A timer has expired
if (msg->isSelfMessage())
{
// Processing depends on timer type
switch (msg->getKind())
{
case BEACON_TIMER:
// Check neighborhood, generate a beacon and send it
checkNeighborhood();
sendBeacon(createBeacon());
// Set timer for next beacon
scheduleAt(simTime() + (double) par("messageFreq"), msg);
break;
default:
opp_error("message (%s)%s is of unknown kind %s",
msg->getClassName(), msg->getName(), msg->getKind());
delete msg;
}

}
// A message has been received from another node

else
{
// process incoming packet
processPacket(PK(msg));
}
}

BeaconPacket* UDPChatApp::createBeacon()
{
char msgName[32];
sprintf(msgName, "UDPChatAppBeacon-%d", counter++);

BeaconPacket* payload = new BeaconPacket(msgName, BEACON);
payload->setByteLength(par("messageLength").longValue());
payload->setState(1);
payload->setTimestamp(simTime());
return payload;
}

void UDPChatApp::sendBeacon(BeaconPacket* msg)
{
//IPvXAddress destAddr = IPvXAddress("192.168.0.1");
IPvXAddress destAddr = IPAddress::ALLONES_ADDRESS;
UDPControlInfo* controlInfo = check_and_cast<UDPControlInfo*>(msg-
>getControlInfo());
controlInfo->setInterfaceId(101);

sendToUDP(msg, localPort, destAddr, destPort);
numSent++;
}

When I do that, I have a check and cast error telling me that msg-
>getControlInfo() in the sendBeacon() function is a NULL pointer. When
I change to unicast address, of course everything works.

Please give me a hand as this is driving me nuts!

Thanks in advance,

-Guillaume

On Oct 23, 7:01 pm, Peter Staab <pixst...@gmx.net> wrote:
> Thank you very much. Now it's working.
> If there is an inetmanet wiki/faq somewhere, then I think this info
> should be added...
>
> Alfonso Ariza schrieb:
>
> > It's not the index, the interface id , the first id is 100 (file
> > InterfaceTable.cc, macro INTERFACEIDS_START)
>
> > The id should be 101 in your implementation.
>

> > *From:* Peter Staab <mailto:pixst...@gmx.net>
> > *Sent:* Friday, October 23, 2009 5:56 PM
> > *To:* omn...@googlegroups.com <mailto:omn...@googlegroups.com>
> > *Subject:* Re: [Fwd: [Omnetpp-l] Broadcast in INETMANET for Omnet 4

> > fixed?]
>
> > I have tried this but without success.
> > The interface is "wlan" and its id is "1".
>
> > Alfonso Ariza schrieb:
>
> >> In UDPControlInfo you must indicate the interface. The method is
> >> setInterfaceId(). The application can't send a broadcast packet
>

> >> *From:* Peter Staab <mailto:pixst...@gmx.net>
> >> *Sent:* Friday, October 23, 2009 4:49 PM
> >> *To:* omn...@googlegroups.com <mailto:omn...@googlegroups.com>
> >> *Subject:* Re: [Fwd: [Omnetpp-l] Broadcast in INETMANET for Omnet 4

> >> fixed?]
>
> >> Can you give me a hint how to "set" the output interface for the
> >> broadcast mechanism?
>
> >> Alfonso Ariza schrieb:
>
> >>> Ok. I suppose where the problem is. The IP broadcast mechanism needs
> >>> the output interface. If the interface is not indicated the IP code
> >>> deletes the packet.
>

> >>> *From:* Peter Staab <mailto:pixst...@gmx.net>
> >>> *Sent:* Friday, October 23, 2009 12:37 PM
> >>> *To:* omn...@googlegroups.com <mailto:omn...@googlegroups.com>
> >>> *Subject:* Re: [Fwd: [Omnetpp-l] Broadcast in INETMANET for Omnet 4

> >>> fixed?]
>
> >>> Hi,
>
> >>> Yes, that's clear. I mean, the problem is:
> >>> Host1 -- (Unicast UDP) --> Host2 works
> >>> Host1 -- (Broadcast UDP) --> Host2 does not work. So the hosts are
> >>> in range.
>
> >>> Regards,
>
> >>> Alfonso Ariza schrieb:
>
> >>>> The Ip code sends the broadcast packets but limit the numbers of
> >>>> hops to 1
>

> >>>> *From:* Peter Staab <mailto:pixst...@gmx.net>
> >>>> *Sent:* Friday, October 23, 2009 12:06 PM
> >>>> *To:* omnetp...@omnetpp.org <mailto:omnetp...@omnetpp.org>
> >>>> *Subject:* [Fwd: [Omnetpp-l] Broadcast in INETMANET for Omnet 4 fixed?]

>
> >>>> To be more specific: I am using an 802.11 network with IP4.
>
> >>>> Regards,
>
> >>>> -------- Original-Nachricht --------
> >>>> Betreff: [Omnetpp-l] Broadcast in INETMANET for Omnet 4 fixed?
> >>>> Datum: Fri, 23 Oct 2009 11:44:41 +0200

> >>>> Von: Peter Staab <pixst...@gmx.net>
> >>>> Antwort an: omn...@googlegroups.com
> >>>> An: omnetp...@omnetpp.org

Peter Staab

unread,

Nov 11, 2009, 6:00:28 AM11/11/09

to omn...@googlegroups.com

Hi,

Please place the following method into your class:

void MyClass::sendToUDP(cPacket *msg, int srcPort, const IPvXAddress& destAddr, int destPort)
{
    // send message to UDP, with the appropriate control info attached
    msg->setKind(UDP_C_DATA);

    UDPControlInfo *ctrl = new UDPControlInfo();
    ctrl->setSrcPort(srcPort);
    ctrl->setDestAddr(destAddr);
    ctrl->setDestPort(destPort);
    ctrl->setInterfaceId(101);

    msg->setControlInfo(ctrl);

    EV << "Sending packet: ";
    printPacket(msg);

    send(msg, "udpOut");
}

That should do it.

Guillaume schrieb:

Charlie

unread,

Nov 24, 2009, 7:24:32 AM11/24/09

to omnetpp

Hi.

I am working in something that I need BROADCAST. I have OMNET++ 4 and
the last inet-sommer version. How can I solve this problem? (sorry,
but I haven't understood this mails list).

Regards.

On 23 oct, 11:06, Peter Staab <pixst...@gmx.net> wrote:
> To be more specific: I am using an 802.11 network with IP4.
>
> Regards,
>
> -------- Original-Nachricht --------
> Betreff: [Omnetpp-l] Broadcast in INETMANET for Omnet 4 fixed?
> Datum: Fri, 23 Oct 2009 11:44:41 +0200

> Von: Peter Staab <pixst...@gmx.net>
> Antwort an: omn...@googlegroups.com
> An: omnetp...@omnetpp.org
>

Peter Staab

unread,

Nov 24, 2009, 7:28:14 AM11/24/09

to omn...@googlegroups.com

Hi,

If you are using Omnet 3.x then you must patch inetmanet with [1].
Else you must modify each UDP packet's control info this way:
ctrl->setInterfaceId(101);
where "ctrl" is of type UDPControlInfo.

Regards,

[1]http://www7.informatik.uni-erlangen.de/~sommer/omnet/

Charlie schrieb:

--

You received this message because you are subscribed to the Google Groups "omnetpp" group.
To post to this group, send email to omn...@googlegroups.com.
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omnetpp?hl=en.

Charlie

unread,

Nov 24, 2009, 11:47:14 AM11/24/09

to omnetpp

Thanks.

I'll try it!!

Regards.

Alfonso Ariza

unread,

Nov 24, 2009, 12:21:52 PM11/24/09

to omn...@googlegroups.com

Inetmanet support the limited broadcast, this is the reason because you must
indicate what is the interface where the broadcast packet must be send

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, November 24, 2009 5:47 PM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Charlie

unread,

Nov 26, 2009, 7:00:58 AM11/26/09

to omnetpp

Hi.

I have done everything that you told me. When I send a packet, the ARP
layer sends a message to know who is 255.255.255.255 direction and
when the others receive the ARP Request they say: "IP address
255.255.255.255 not recognized, dropping ARP packet". Do you know why
this is happening?

Thanks and regards.

On 24 nov, 18:21, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> Inetmanet support the limitedbroad cast, this is the reason because you must
> indicate what is the interface where thebroadcastpacket must be send
>
> --------------------------------------------------
> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Tuesday, November 24, 2009 5:47 PM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]

>
> > Thanks.
>
> > I'll try it!!
>
> > Regards.
>
> > On 24 nov, 13:28, Peter Staab <pixst...@gmx.net> wrote:
> >> Hi,
>
> >> If you are using Omnet 3.x then you must patch inetmanet with [1].
> >> Else you must modify each UDP packet's control info this way:
> >> ctrl->setInterfaceId(101);
> >> where "ctrl" is of type UDPControlInfo.
>
> >> Regards,
>
> >> [1]http://www7.informatik.uni-erlangen.de/~sommer/omnet/
>
> >> Charlie schrieb:
>
> >> > Hi.
>

> >> > I am working in something that I needBROADCAST. I have OMNET++ 4 and

> >> > the last inet-sommer version. How can I solve this problem? (sorry,
> >> > but I haven't understood this mails list).
>
> >> > Regards.
>
> >> > On 23 oct, 11:06, Peter Staab <pixst...@gmx.net> wrote:
>
> >> >> To be more specific: I am using an 802.11 network with IP4.
>
> >> >> Regards,
>
> >> >> -------- Original-Nachricht --------

> >> >> Betreff: [Omnetpp-l]Broadcastin INETMANET for Omnet 4 fixed?

> >> >> Datum: Fri, 23 Oct 2009 11:44:41 +0200
> >> >> Von: Peter Staab <pixst...@gmx.net>
> >> >> Antwort an: omn...@googlegroups.com
> >> >> An: omnetp...@omnetpp.org
>
> >> >> Hello,
>
> >> >> The inetmanet version for OMNet 3.3 had to be fixed to getbroadcast
> >> >> working [1].
> >> >> Is the latest inetmanet version for OMNet 4 already fixed? If yes, how

> >> >> can Ibroadcaste.g. a UDP packet? Sending to

Alfonso Ariza

unread,

Nov 26, 2009, 7:24:42 AM11/26/09

to omn...@googlegroups.com

In inetmanet?
The packets with address IPAddress::ALLONES_ADDRESS are sent by the ARP to
the network, it doesn't send a Arp packet to other nodes and the other nodes
don't answer

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Thursday, November 26, 2009 1:00 PM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Message has been deleted

Charlie

unread,

Nov 26, 2009, 8:01:54 AM11/26/09

to omnetpp

Maybe, can it be because I'm using DYMO routing protocol?

On 26 nov, 13:24, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> In inetmanet?
> The packets with address IPAddress::ALLONES_ADDRESS are sent by the ARP to
> the network, it doesn't send a Arp packet to other nodes and the other nodes
> don't answer
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Thursday, November 26, 2009 1:00 PM
> To: "omnetpp" <omn...@googlegroups.com>

Alfonso Ariza

unread,

Nov 26, 2009, 10:42:33 AM11/26/09

to omn...@googlegroups.com

No, the broadcast is independent of the routing mechanism
--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Thursday, November 26, 2009 2:01 PM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Charlie

unread,

Nov 27, 2009, 4:08:11 AM11/27/09

to omnetpp

I type you all that it appears me in the screen from I send the UDP
packet to the first host drops the packet:

** Event #55 T=40 scenario.host[0].sendingSignature
(SendingSignature, id=140), on selfmsg `sendTimer' (cMessage, id=101)
Sending packet: (SignedMsg) (99 bytes)
<unspec> :5555 --> 255.255.255.255:5555
X = 707429722658001420376168397060274978687491711591.
Y = 1016494856058831609021684853563590114806406477202.
Mensaje = Hola Mundo!!.
** Event #56 T=40 scenario.manager (TraCIScenarioManager, id=3), on
selfmsg `step' (cMessage, id=0)
Triggering TraCI server simulation advance to t=40
Writing TraCI message of 11 bytes
Reading TraCI message of 307 bytes
module 0 moving to 4327,5374
nextPosition 4327 5374 6e9efe94-1c70-4bbd-8a8d-1a6ad697b03b 5.50524
2.42738 5.56
module 1 moving to 4339,5389
nextPosition 4339 5389 6e9efe94-1c70-4bbd-8a8d-1a6ad697b03b 5.49452
2.42738 5.56
module 2 moving to 4353,5404
nextPosition 4353 5404 6e9efe94-1c70-4bbd-8a8d-1a6ad697b03b 5.55956
2.42738 5.56
module 3 moving to 4366,5420
nextPosition 4366 5420 6e9efe94-1c70-4bbd-8a8d-1a6ad697b03b 5.55876
2.42738 5.56
** Event #57 T=40 scenario.host[0].udp (UDP, id=135), on `
{}' (SignedMsg, id=135)
Sending app packet over IPv4.
** Event #58 T=40 scenario.host[0].networkLayer.ip (IP, id=141), on `
{}' (UDPPacket, id=136)
** Event #59 T=40.00001 scenario.host[0].networkLayer.ip (IP,
id=141), on selfmsg `end-service' (cMessage, id=91)
onOutboundDataPacket destAddr == myAddr (167772290)
Routing datagram `' with dest=255.255.255.255: using manually
specified output interface wlan
output interface is wlan, next-hop address: <unspec>
** Event #60 T=40.00001 scenario.host[0].networkLayer.arp (ARP,
id=142), on `{}' (IPDatagram, id=137)
Packet (IPDatagram) arrived from higher layer, no next-hop address,
using destination address 255.255.255.255 (proxy ARP)
Starting ARP resolution for 255.255.255.255
** Event #61 T=40.00001 scenario.host[0].wlan.mac (Mac80211,
id=146), on `arpREQ' (ARPPacket, id=138)
packet (ARPPacket)arpREQ received from higher layer, dest=FF-FF-FF-FF-
FF-FF, encapsulated
beginning new contention cycle
trying to send without backoff...
state IDLE --> CONTEND
** Event #62 T=40.00006 scenario.host[0].wlan.mac (Mac80211,
id=146), on selfmsg `contention' (cMessage, id=94)
processing self message with type = CONTENTION
end contention period
sending down (Mac80211Pkt)arpREQ
state CONTEND --> BUSY
** Event #63 T=40.00006 scenario.host[0].wlan.snrEval (SnrEval80211,
id=148), on `arpREQ' (Mac80211Pkt, id=141)
bits without header: 496, bits header: 192
sending, changing RadioState to TRANSMIT
** Notification at T=40.00006 to scenario.host[0].wlan.mac: RADIO-
STATE TRANSMIT, channel #0, -1e-06Mbps
** Radio state update in Mac80211: TRANSMIT, channel #0, -1e-06Mbps
(at T=40.00006)
** Event #64 T=40.000060064031 scenario.host[1].wlan.snrEval
(SnrEval80211, id=167), on `arpREQ' (AirFrame, id=144)
receiving frame arpREQ
publish new RadioState:RECV
** Notification at T=40.000060064031 to scenario.host[1].wlan.mac:
RADIO-STATE RECV, channel #0, -1e-06Mbps
** Radio state update in Mac80211: RECV, channel #0, -1e-06Mbps (at
T=40.000060064031)
** Event #65 T=40.000060132329 scenario.host[2].wlan.snrEval
(SnrEval80211, id=186), on `arpREQ' (AirFrame, id=145)
receiving frame arpREQ
publish new RadioState:RECV
** Notification at T=40.000060132329 to scenario.host[2].wlan.mac:
RADIO-STATE RECV, channel #0, -1e-06Mbps
** Radio state update in Mac80211: RECV, channel #0, -1e-06Mbps (at
T=40.000060132329)
** Event #66 T=40.000060201025 scenario.host[3].wlan.snrEval
(SnrEval80211, id=205), on `arpREQ' (AirFrame, id=146)
receiving frame arpREQ
publish new RadioState:RECV
** Notification at T=40.000060201025 to scenario.host[3].wlan.mac:
RADIO-STATE RECV, channel #0, -1e-06Mbps
** Radio state update in Mac80211: RECV, channel #0, -1e-06Mbps (at
T=40.000060201025)
** Event #67 T=40.000297090909 scenario.host[0].wlan.mac (Mac80211,
id=146), on selfmsg `transmission' (cMessage, id=95)
processing self message with type = END_TRANSMISSION
transmission of ACK/BROADCAST is over
beginning new contention cycle
state BUSY --> IDLE
** Event #68 T=40.000297090909 scenario.host[0].wlan.snrEval
(SnrEval80211, id=148), on selfmsg `{}' (cMessage, id=143)
transmission over, switch to idle mode (state:IDLE)
** Notification at T=40.000297090909 to scenario.host[0].wlan.mac:
RADIO-STATE IDLE, channel #0, -1e-06Mbps
** Radio state update in Mac80211: IDLE, channel #0, -1e-06Mbps (at
T=40.000297090909)
** Event #69 T=40.00029715494 scenario.host[1].wlan.snrEval
(SnrEval80211, id=167), on selfmsg `{}' (TransmComplete, id=147)
reception of frame over, preparing to send packet to upper layer
packet sent to the decider
new RadioState is IDLE
** Notification at T=40.00029715494 to scenario.host[1].wlan.mac:
RADIO-STATE IDLE, channel #0, -1e-06Mbps
** Radio state update in Mac80211: IDLE, channel #0, -1e-06Mbps (at
T=40.00029715494)
** Event #70 T=40.00029715494 scenario.host[1].wlan.decider
(Decider80211, id=166), on `arpREQ' (AirFrame, id=144)
packet (Mac80211Pkt)arpREQ () snrMin=72070.1
berHeader: 0 berMPDU: 0
packet was received correctly, it is now handed to upper layer...
** Event #71 T=40.00029715494 scenario.host[1].wlan.mac (Mac80211,
id=165), on `arpREQ' (Mac80211Pkt, id=150)
frame (Mac80211Pkt)arpREQ received, kind = BROADCAST
handle broadcast
sending up (ARPPacket)arpREQ
** Event #72 T=40.00029715494 scenario.host[1].networkLayer.ip (IP,
id=160), on `arpREQ' (ARPPacket, id=151)
** Event #73 T=40.000297223238 scenario.host[2].wlan.snrEval
(SnrEval80211, id=186), on selfmsg `{}' (TransmComplete, id=148)
reception of frame over, preparing to send packet to upper layer
packet sent to the decider
new RadioState is IDLE
** Notification at T=40.000297223238 to scenario.host[2].wlan.mac:
RADIO-STATE IDLE, channel #0, -1e-06Mbps
** Radio state update in Mac80211: IDLE, channel #0, -1e-06Mbps (at
T=40.000297223238)
** Event #74 T=40.000297223238 scenario.host[2].wlan.decider
(Decider80211, id=185), on `arpREQ' (AirFrame, id=145)
packet (Mac80211Pkt)arpREQ () snrMin=18144.8
berHeader: 0 berMPDU: 0
packet was received correctly, it is now handed to upper layer...
** Event #75 T=40.000297223238 scenario.host[2].wlan.mac (Mac80211,
id=184), on `arpREQ' (Mac80211Pkt, id=152)
frame (Mac80211Pkt)arpREQ received, kind = BROADCAST
handle broadcast
sending up (ARPPacket)arpREQ
** Event #76 T=40.000297223238 scenario.host[2].networkLayer.ip (IP,
id=179), on `arpREQ' (ARPPacket, id=153)
** Event #77 T=40.000297291934 scenario.host[3].wlan.snrEval
(SnrEval80211, id=205), on selfmsg `{}' (TransmComplete, id=149)
reception of frame over, preparing to send packet to upper layer
packet sent to the decider
new RadioState is IDLE
** Notification at T=40.000297291934 to scenario.host[3].wlan.mac:
RADIO-STATE IDLE, channel #0, -1e-06Mbps
** Radio state update in Mac80211: IDLE, channel #0, -1e-06Mbps (at
T=40.000297291934)
** Event #78 T=40.000297291934 scenario.host[3].wlan.decider
(Decider80211, id=204), on `arpREQ' (AirFrame, id=146)
packet (Mac80211Pkt)arpREQ () snrMin=8198.31
berHeader: 0 berMPDU: 0
packet was received correctly, it is now handed to upper layer...
** Event #79 T=40.000297291934 scenario.host[3].wlan.mac (Mac80211,
id=203), on `arpREQ' (Mac80211Pkt, id=141)
frame (Mac80211Pkt)arpREQ received, kind = BROADCAST
handle broadcast
sending up (ARPPacket)arpREQ
** Event #80 T=40.000297291934 scenario.host[3].networkLayer.ip (IP,
id=198), on `arpREQ' (ARPPacket, id=138)
** Event #81 T=40.00030715494 scenario.host[1].networkLayer.ip (IP,
id=160), on selfmsg `end-service' (cMessage, id=102)
** Event #82 T=40.00030715494 scenario.host[1].networkLayer.arp
(ARP, id=161), on `arpREQ' (ARPPacket, id=151)
ARP packet (ARPPacket)arpREQ arrived:
ARP_REQ src=10.0.0.130 / 0A-AA-00-00-00-0D dest=255.255.255.255 /
00-00-00-00-00-00

IP address 255.255.255.255 not recognized, dropping ARP packet

Regards.

On 26 nov, 16:42, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> No, thebroadcastis independent of the routing mechanism
> --------------------------------------------------
> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Thursday, November 26, 2009 2:01 PM
> To: "omnetpp" <omn...@googlegroups.com>

Alfonso Ariza

unread,

Nov 27, 2009, 4:29:05 AM11/27/09

to omn...@googlegroups.com

The IP.cc code doesn't read correctly the broadcast address. How are you
setting the broadcast address? Whit IPAddress::ALLONES_ADDRESS?

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Friday, November 27, 2009 10:08 AM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Charlie

unread,

Nov 27, 2009, 4:39:51 AM11/27/09

to omnetpp

Yes, I use IPAddress::ALLONES_ADDRESS. Y type you my c++ code (the
sending functions):

void SendingSignature::sendPacket()
{
SignedMsg *payload = createPacket();
//IPvXAddress destAddr = chooseDestAddr();

IPvXAddress destAddr = IPAddress::ALLONES_ADDRESS;

sendToUDP(payload, localPort, destAddr, destPort);

numSent++;
}

//funcion para el envio por Broadcast!!
void SendingSignature::sendToUDP(SignedMsg *msg, int srcPort, const

IPvXAddress& destAddr, int destPort)
{
// send message to UDP, with the appropriate control info attached
msg->setKind(UDP_C_DATA);

UDPControlInfo *ctrl = new UDPControlInfo();
ctrl->setSrcPort(srcPort);
ctrl->setDestAddr(destAddr);
ctrl->setDestPort(destPort);
ctrl->setInterfaceId(101);

msg->setControlInfo(ctrl);

EV << "Sending packet: ";
printPacket(msg);

const ECP::Point& q = msg->getP();
EV << "X = " << q.x << endl;
EV << "Y = " << q.y << endl;
EV << "Mensaje = " << msg->getMsg() << endl;
//EV << "Firma = " << hex << msg->getSignature() << dec << endl;

send(msg, "udpOut");

}

void SendingSignature::handleMessage(cMessage *msg)
{
if (msg->isSelfMessage())
{
// send, then reschedule next sending
sendPacket();
scheduleAt(simTime()+(double)par("messageFreq"), msg);

}
else
{
// process incoming packet

processPacket(check_and_cast<SignedMsg *>(msg));
}

if (ev.isGUI())
{
char buf[40];
sprintf(buf, "rcvd: %d pks\nsent: %d pks", numReceived,
numSent);
getDisplayString().setTagArg("t",0,buf);
}
}

I'm grateful for your rapid answers!

Regards.

On 27 nov, 10:29, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> The IP.cc code doesn't read correctly thebroadcastaddress. How are you

> setting thebroadcastaddress? Whit IPAddress::ALLONES_ADDRESS?
>
> --------------------------------------------------
> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Friday, November 27, 2009 10:08 AM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
>

> > transmission of ACK/BROADCASTis over

> ...
>
> leer más »

Message has been deleted

Alfonso Ariza

unread,

Nov 27, 2009, 11:07:13 AM11/27/09

to omn...@googlegroups.com

Can you execute the debug? put a break point in the method IP::routePacket

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Friday, November 27, 2009 10:39 AM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

>> leer m�s �

Charlie

unread,

Nov 30, 2009, 5:56:21 AM11/30/09

to omnetpp

I've put a break point in IP::routePacket. The value of destAddr is:

{addr = 4294967295, static UNSPECIFIED_ADDRESS = {addr = 0, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = {addr = 2130706433, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = {addr = 4278190080, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = {addr = 4294967295, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = <same as static member of an
already seen type>, static ALL_HOSTS_MCAST = {addr = 3758096385,
static UNSPECIFIED_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_ADDRESS = <same as static member of an already
seen type>, static LOOPBACK_NETMASK = <same as static member of an
already seen type>, static ALLONES_ADDRESS = <same as static member of
an already seen type>, static ALL_HOSTS_MCAST = <same as static member
of an already seen type>, static ALL_ROUTERS_MCAST = {addr =
3758096386, static UNSPECIFIED_ADDRESS = <same as static member of an
already seen type>, static LOOPBACK_ADDRESS = <same as static member
of an already seen type>, static LOOPBACK_NETMASK = <same as static
member of an already seen type>, static ALLONES_ADDRESS = <same as
static member of an already seen type>, static ALL_HOSTS_MCAST = <same
as static member of an already seen type>, static ALL_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_DVMRP_ROUTERS_MCAST = {addr = 3758096388, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = <same as static member of an
already seen type>, static ALL_HOSTS_MCAST = <same as static member of
an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = {addr = 3758096389, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = <same as static member of an
already seen type>, static ALL_HOSTS_MCAST = <same as static member of
an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = {addr = 3758096390,
static UNSPECIFIED_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_ADDRESS = <same as static member of an already
seen type>, static LOOPBACK_NETMASK = <same as static member of an
already seen type>, static ALLONES_ADDRESS = <same as static member of
an already seen type>, static ALL_HOSTS_MCAST = <same as static member
of an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static
member of an already seen type>}}, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_OSPF_ROUTERS_MCAST = <same as static
member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_DVMRP_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_OSPF_ROUTERS_MCAST = <same
as static member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_ROUTERS_MCAST = <same as static member
of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST = <same as
static member of an already seen type>, static ALL_OSPF_ROUTERS_MCAST
= <same as static member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_HOSTS_MCAST = <same as static member
of an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static
member of an already seen type>}, static ALLONES_ADDRESS = <same as
static member of an already seen type>, static ALL_HOSTS_MCAST = <same
as static member of an already seen type>, static ALL_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_DVMRP_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_ROUTERS_MCAST = <same as static member of an
already seen type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same
as static member of an already seen type>}, static LOOPBACK_NETMASK =
<same as static member of an already seen type>, static
ALLONES_ADDRESS = <same as static member of an already seen type>,
static ALL_HOSTS_MCAST = <same as static member of an already seen
type>, static ALL_ROUTERS_MCAST = <same as static member of an already
seen type>, static ALL_DVMRP_ROUTERS_MCAST = <same as static member of
an already seen type>, static ALL_OSPF_ROUTERS_MCAST = <same as static
member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static LOOPBACK_ADDRESS = <same as static member
of an already seen type>, static LOOPBACK_NETMASK = <same as static
member of an already seen type>, static ALLONES_ADDRESS = <same as
static member of an already seen type>, static ALL_HOSTS_MCAST = <same
as static member of an already seen type>, static ALL_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_DVMRP_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_ROUTERS_MCAST = <same as static member of an
already seen type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same
as static member of an already seen type>}

And the value of nextHopAddr is:

{addr = 4294967295, static UNSPECIFIED_ADDRESS = {addr = 0, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = {addr = 2130706433, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = {addr = 4278190080, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = {addr = 4294967295, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = <same as static member of an
already seen type>, static ALL_HOSTS_MCAST = {addr = 3758096385,
static UNSPECIFIED_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_ADDRESS = <same as static member of an already
seen type>, static LOOPBACK_NETMASK = <same as static member of an
already seen type>, static ALLONES_ADDRESS = <same as static member of
an already seen type>, static ALL_HOSTS_MCAST = <same as static member
of an already seen type>, static ALL_ROUTERS_MCAST = {addr =
3758096386, static UNSPECIFIED_ADDRESS = <same as static member of an
already seen type>, static LOOPBACK_ADDRESS = <same as static member
of an already seen type>, static LOOPBACK_NETMASK = <same as static
member of an already seen type>, static ALLONES_ADDRESS = <same as
static member of an already seen type>, static ALL_HOSTS_MCAST = <same
as static member of an already seen type>, static ALL_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_DVMRP_ROUTERS_MCAST = {addr = 3758096388, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = <same as static member of an
already seen type>, static ALL_HOSTS_MCAST = <same as static member of
an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = {addr = 3758096389, static
UNSPECIFIED_ADDRESS = <same as static member of an already seen type>,
static LOOPBACK_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_NETMASK = <same as static member of an already
seen type>, static ALLONES_ADDRESS = <same as static member of an
already seen type>, static ALL_HOSTS_MCAST = <same as static member of
an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = {addr = 3758096390,
static UNSPECIFIED_ADDRESS = <same as static member of an already seen
type>, static LOOPBACK_ADDRESS = <same as static member of an already
seen type>, static LOOPBACK_NETMASK = <same as static member of an
already seen type>, static ALLONES_ADDRESS = <same as static member of
an already seen type>, static ALL_HOSTS_MCAST = <same as static member
of an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static
member of an already seen type>}}, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_OSPF_ROUTERS_MCAST = <same as static
member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_DVMRP_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_OSPF_ROUTERS_MCAST = <same
as static member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_ROUTERS_MCAST = <same as static member
of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST = <same as
static member of an already seen type>, static ALL_OSPF_ROUTERS_MCAST
= <same as static member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static ALL_HOSTS_MCAST = <same as static member
of an already seen type>, static ALL_ROUTERS_MCAST = <same as static
member of an already seen type>, static ALL_DVMRP_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_OSPF_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static
member of an already seen type>}, static ALLONES_ADDRESS = <same as
static member of an already seen type>, static ALL_HOSTS_MCAST = <same
as static member of an already seen type>, static ALL_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_DVMRP_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_ROUTERS_MCAST = <same as static member of an
already seen type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same
as static member of an already seen type>}, static LOOPBACK_NETMASK =
<same as static member of an already seen type>, static
ALLONES_ADDRESS = <same as static member of an already seen type>,
static ALL_HOSTS_MCAST = <same as static member of an already seen
type>, static ALL_ROUTERS_MCAST = <same as static member of an already
seen type>, static ALL_DVMRP_ROUTERS_MCAST = <same as static member of
an already seen type>, static ALL_OSPF_ROUTERS_MCAST = <same as static
member of an already seen type>, static
ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same as static member of an
already seen type>}, static LOOPBACK_ADDRESS = <same as static member
of an already seen type>, static LOOPBACK_NETMASK = <same as static
member of an already seen type>, static ALLONES_ADDRESS = <same as
static member of an already seen type>, static ALL_HOSTS_MCAST = <same
as static member of an already seen type>, static ALL_ROUTERS_MCAST =
<same as static member of an already seen type>, static
ALL_DVMRP_ROUTERS_MCAST = <same as static member of an already seen
type>, static ALL_OSPF_ROUTERS_MCAST = <same as static member of an
already seen type>, static ALL_OSPF_DESIGNATED_ROUTERS_MCAST = <same
as static member of an already seen type>}

I don't know if it's this you want that I see.

Regards.

On 27 nov, 17:07, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> Can you execute the debug? put a break point in the method IP::routePacket
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Friday, November 27, 2009 10:39 AM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
>

> ...
>
> leer más »

Alfonso Ariza

unread,

Nov 30, 2009, 11:20:10 AM11/30/09

to omn...@googlegroups.com

La direcci�n es correcta.

the code that is necessary to check is this

if (destAddr == IPAddress::ALLONES_ADDRESS ||
rt->isLocalBroadcastAddress(destAddr))
{
// check if local
if (!fromHL)
{
EV << "limited broadcast recived \n";
if (datagram->getSrcAddress().isUnspecified())
datagram->setSrcAddress(destAddr); // allows two apps on
the same host to communicate
numLocalDeliver++;
reassembleAndDeliver(datagram);
}
else
{ // send limited broadcast packet
if (destIE!=NULL)
fragmentAndSend(datagram, destIE,
IPAddress::ALLONES_ADDRESS);
else
{
numDropped++;
delete datagram;
}
}
return;
}

The is packet sent with the method fragmentAndSend(datagram, destIE,
IPAddress::ALLONES_ADDRESS);?

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Monday, November 30, 2009 11:56 AM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Charlie

unread,

Nov 30, 2009, 12:17:58 PM11/30/09

to omnetpp

For some reason this code part had missed. I'm going to download the
inetmanet and try it again.

Thanks of all. I'm very grateful for your help!

Regards.

> From: "Charlie" <pgpenprue...@gmail.com>

> ...
>
> leer más »

Alfonso Ariza

unread,

Nov 30, 2009, 12:35:25 PM11/30/09

to omn...@googlegroups.com

This code is in inetmanet, not in inet-framework

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Monday, November 30, 2009 6:17 PM

Charlie

unread,

Dec 1, 2009, 4:41:53 AM12/1/09

to omnetpp

I've installed inetmanet, but now, How can I put DYMO routing protocol
in Car.ned? I 've added ManetRouting module in Car.ned and in the
omnetp.ini **.manetRouting.manetmanager.routingProtocol = "DYMOFAU"
but doesn't work!

Thanks and regards.

On 30 nov, 18:35, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> This code is in inetmanet, not in inet-framework
>
> --------------------------------------------------

> ...
>
> leer más »

Alfonso Ariza

unread,

Dec 1, 2009, 5:06:20 AM12/1/09

to omn...@googlegroups.com

Please more information.
What is the event trace?
The Dymo module is loading?
What node are you using?

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, December 01, 2009 10:41 AM

Message has been deleted

Charlie

unread,

Dec 1, 2009, 5:37:38 AM12/1/09

to omnetpp

I'm using the Car.ned from traci. At this.ned I've added ManetRouting
module. When I run the omnet.ini, the only thing that the screen shows
about DYMO is the next sentence:
active Ad-hoc routing protocol : DYMOFAU dynamic : 1

But the cars doesn't have IP address!
If you want, I can send you to you mail my .ned files and my
omnet.ini.

Thanks.

On 1 dic, 11:06, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> Please more information.
> What is the event trace?
> The Dymo module is loading?
> What node are you using?
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Tuesday, December 01, 2009 10:41 AM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]

>
> > I've installed inetmanet, but now, How can I put DYMO routing protocol
> > in Car.ned? I 've added ManetRouting module in Car.ned and in the
> > omnetp.ini **.manetRouting.manetmanager.routingProtocol = "DYMOFAU"
> > but doesn't work!
>
> > Thanks and regards.
>
> > On 30 nov, 18:35, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> >> This code is in inetmanet, not in inet-framework
>
> >> --------------------------------------------------
> >> From: "Charlie" <pgpenprue...@gmail.com>
> >> Sent: Monday, November 30, 2009 6:17 PM
> >> To: "omnetpp" <omn...@googlegroups.com>

> >> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]

>
> >> > For some reason this code part had missed. I'm going to download the
> >> > inetmanet and try it again.
>
> >> > Thanks of all. I'm very grateful for your help!
>
> >> > Regards.
>
> >> > On 30 nov, 17:20, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> >> >> La direcci n es correcta.
>
> >> >> the code that is necessary to check is this
>
> >> >> if (destAddr == IPAddress::ALLONES_ADDRESS ||
> >> >> rt->isLocalBroadcastAddress(destAddr))
> >> >> {
> >> >> // check if local
> >> >> if (!fromHL)
> >> >> {

> >> >> EV << "limitedbroadcastrecived \n";

> >> >> if (datagram->getSrcAddress().isUnspecified())
> >> >> datagram->setSrcAddress(destAddr); // allows two apps
> >> >> on
> >> >> the same host to communicate
> >> >> numLocalDeliver++;
> >> >> reassembleAndDeliver(datagram);
> >> >> }
> >> >> else
> >> >> { // send limitedbroadcastpacket
> >> >> if (destIE!=NULL)
> >> >> fragmentAndSend(datagram, destIE,
> >> >> IPAddress::ALLONES_ADDRESS);
> >> >> else
> >> >> {
> >> >> numDropped++;
> >> >> delete datagram;
> >> >> }
> >> >> }
> >> >> return;
> >> >> }
>
> >> >> The is packet sent with the method fragmentAndSend(datagram, destIE,
> >> >> IPAddress::ALLONES_ADDRESS);?
>
> >> >> --------------------------------------------------
> >> >> From: "Charlie" <pgpenprue...@gmail.com>
> >> >> Sent: Monday, November 30, 2009 11:56 AM
> >> >> To: "omnetpp" <omn...@googlegroups.com>

> >> >> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]

> ...
>
> leer más »

Alfonso Ariza

unread,

Dec 1, 2009, 5:41:08 AM12/1/09

to omn...@googlegroups.com

The IP address is asignated by the FlatNetworkConfigurator or by the routing
files, not by the routing protocol

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, December 01, 2009 11:37 AM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Charlie

unread,

Dec 1, 2009, 5:52:35 AM12/1/09

to omnetpp

But the FlatNetworkConfigurator is only executed at the beginning of
the simulation, and the cars aren't at the beginning, they appear
later. Before I installed inetmanet, I used this Dymo from the
application layer ( http://www7.informatik.uni-erlangen.de/~sommer/omnet/dymo/
) and this assigned IP address.

On 1 dic, 11:41, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> The IP address is asignated by the FlatNetworkConfigurator or by the routing
> files, not by the routing protocol
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Tuesday, December 01, 2009 11:37 AM
> To: "omnetpp" <omn...@googlegroups.com>

> ...
>
> leer más »

Alfonso Ariza

unread,

Dec 1, 2009, 7:42:35 AM12/1/09

to omn...@googlegroups.com

The Dymo port in inetmanet doesn't assign IP address, it should be necessary
to modify the code of ManetManager and to add this functionality or to use
routing files and to configure the interfaces with these files

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, December 01, 2009 11:52 AM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Alfonso Ariza

unread,

Dec 1, 2009, 11:52:33 AM12/1/09

to omn...@googlegroups.com

I have uploaded a modification of ManetManager that can autoassign the
ipaddress

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, December 01, 2009 11:52 AM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Message has been deleted

Charlie

unread,

Dec 1, 2009, 12:16:26 PM12/1/09

to omnetpp

Thank you very much!!!!!!!!

I'm very grateful for your help!!

Thank you very much!

On 1 dic, 17:52, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> I have uploaded a modification of ManetManager that can autoassign the
> ipaddress
>
> --------------------------------------------------

> ...
>
> leer más »

Message has been deleted

Charlie

unread,

Dec 2, 2009, 5:27:27 AM12/2/09

to omnetpp

Hi.

I've found a problem witn the auto assignation. When I run the
omnet.ini, it shows me an error: "ManetManager needs
AUTOASSIGN_ADDRESS_BASE to be set to 0.0.0.0".

Then I've changed this line in the ManetManager.cc:
if (AUTOASSIGN_ADDRESS_BASE.getInt() != 0)

for this:
if (AUTOASSIGN_ADDRESS_BASE.getInt() == 0)

and now, it works fine.

Regards.

On 1 dic, 17:52, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

> I have uploaded a modification of ManetManager that can autoassign the
> ipaddress
>
> --------------------------------------------------

> ...
>
> leer más »

Alfonso Ariza

unread,

Dec 2, 2009, 10:48:35 AM12/2/09

to omn...@googlegroups.com

Ok, I will fix

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Wednesday, December 02, 2009 11:26 AM

To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

> Hi.
>
> I've found a problem witn the auto assignation. When I run the
> omnet.ini, it shows me an error: "ManetManager needs
> AUTOASSIGN_ADDRESS_BASE to be set to 0.0.0.0".
>
> Then I've changed this line in the ManetManager.cc:
> if (AUTOASSIGN_ADDRESS_BASE.getInt() != 0)
>
> for this:
> if (AUTOASSIGN_ADDRESS_BASE.getInt() == 0)
>

> and now, it's work fine.

>
> Regards.
>
> On 1 dic, 17:52, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

>> I have uploaded a modification of ManetManager that can autoassign the
>> ipaddress
>>
>> --------------------------------------------------

Charlie

unread,

Dec 9, 2009, 7:31:36 AM12/9/09

to omnetpp

Hi Alfonso!

Can I use broadcast with 2 hops?

Regards.

On 2 dic, 16:48, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> Ok, I will fix
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Wednesday, December 02, 2009 11:26 AM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
>

> > Hi.
>
> > I've found a problem witn the auto assignation. When I run the
> > omnet.ini, it shows me an error: "ManetManager needs
> > AUTOASSIGN_ADDRESS_BASE to be set to 0.0.0.0".
>
> > Then I've changed this line in the ManetManager.cc:
> > if (AUTOASSIGN_ADDRESS_BASE.getInt() != 0)
>
> > for this:
> > if (AUTOASSIGN_ADDRESS_BASE.getInt() == 0)
>
> > and now, it's work fine.
>
> > Regards.
>
> > On 1 dic, 17:52, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> >> I have uploaded a modification of ManetManager that can autoassign the
> >> ipaddress
>
> >> --------------------------------------------------
> >> From: "Charlie" <pgpenprue...@gmail.com>
> >> Sent: Tuesday, December 01, 2009 11:52 AM
> >> To: "omnetpp" <omn...@googlegroups.com>

> ...
>
> leer más »

Alfonso Ariza

unread,

Dec 9, 2009, 10:50:39 AM12/9/09

to omn...@googlegroups.com

It's necessary that a module receives and re-broadcasts the packet. The
routing protocols work of this form, they send a broadcast packet to 1 hop,
the neighbor nodes receive the packet and the routing module re-sends the
packet.

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Wednesday, December 09, 2009 1:31 PM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Christoph Mayer

unread,

Dec 9, 2009, 11:22:12 AM12/9/09

to omn...@googlegroups.com

Hi,

we just discovered that the linklayer/PPP.cc code in the INET framework
has a destructor with the following code:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
PPP::~PPP()
{
// kludgy way to check that nb is not deleted yet
if (nb && nb == NotificationBoardAccess().getIfExists())
nb->unsubscribe(this, NF_SUBSCRIBERLIST_CHANGED);
cancelAndDelete(endTransmissionEvent);
}
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Shouldn't this code be in a PPP::finalize method rather than in the
destructor? The NotificationBoardAccess().getIfExists()) function uses
simultation.getContext for finding a submodule. The context returned
here will not be the same context of the actual PPP module.

Subscription is done in the PPP::initialize function, there you find:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
nb = NotificationBoardAccess().get();
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

In this call, the context is set to the actual PPP module, as the
initialize function is called by OMNeT++, but in the destructor code,
the context is not the PPP module. This will result in the that the if
never is true.

Can someone validate that this is a bug and that the code should be
placed in a PPP::finalize method?

Thanks,
Chris
--
Dipl.-Inform. Christoph P. Mayer
Institute of Telematics, University of Karlsruhe (TH)
Zirkel 2, 76128 Karlsruhe, Germany
Phone: +49 721 608 6415, Email: ma...@tm.uka.de
Web: http://www.tm.uka.de/~mayer/

Alfonso Ariza schrieb:

Message has been deleted

Charlie

unread,

Dec 22, 2009, 6:29:40 AM12/22/09

to omnetpp

Then, I have to modify the manet routing module (in my case,
DYMO_FAU), don't I?

Thanks

On 9 dic, 16:50, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> It's necessary that a module receives and re-broadcasts the packet. The
> routing protocols work of this form, they send abroadcastpacket to 1hop,
> the neighbor nodes receive the packet and the routing module re-sends the
> packet.
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Wednesday, December 09, 2009 1:31 PM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
>

> > Hi Alfonso!
>
> > Can I usebroadcastwith 2 hops?

> ...
>
> leer más »

Alfonso Ariza

unread,

Dec 22, 2009, 6:54:44 AM12/22/09

to omn...@googlegroups.com

what do you want? a broadcast to 2 hops for any packet? for dymo packet?

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, December 22, 2009 12:29 PM
To: "omnetpp" <omn...@googlegroups.com>
Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

Charlie

unread,

Dec 22, 2009, 7:37:16 AM12/22/09

to omnetpp

a broadcast to 2 hops for UDP packets from my UDP Application.

On 22 dic, 12:54, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> what do you want? a broadcast to 2 hops for any packet? for dymo packet?
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

Alfonso Ariza

unread,

Dec 22, 2009, 9:25:31 AM12/22/09

to omn...@googlegroups.com

In this case the situation is different. It's necessary to create a module
that resends the broadcast packet. In my opinion should be your application
module that after receive the packet re-sent the packet to the network. The
reactive routing protocol works of this form, the module receive the packet,
process the packet and if the TTL is enough, re-sent the packet

--------------------------------------------------
From: "Charlie" <pgpenp...@gmail.com>
Sent: Tuesday, December 22, 2009 1:37 PM

Charlie

unread,

Dec 23, 2009, 5:34:22 AM12/23/09

to omnetpp

Thanks Alfonso!

On 22 dic, 15:25, "Alfonso Ariza" <aariza...@hotmail.com> wrote:
> In this case the situation is different. It's necessary to create a module

> that resends thebroadcastpacket. In my opinion should be your application

> module that after receive the packet re-sent the packet to the network. The
> reactive routing protocol works of this form, the module receive the packet,
> process the packet and if the TTL is enough, re-sent the packet
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Tuesday, December 22, 2009 1:37 PM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
>

> > abroadcastto 2 hops for UDP packets from my UDP Application.

>
> > On 22 dic, 12:54, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

> >> what do you want? abroadcastto 2 hops for any packet? for dymo packet?

>
> >> --------------------------------------------------
> >> From: "Charlie" <pgpenprue...@gmail.com>
> >> Sent: Tuesday, December 22, 2009 12:29 PM
> >> To: "omnetpp" <omn...@googlegroups.com>

Message has been deleted

Charlie

unread,

Dec 24, 2009, 5:31:07 AM12/24/09

to omnetpp

I've done it like you said me. My udp application re-sends the
broadcast packet after receiving this packet. But I re-send it in a
random short time (less than one second) after receiving the packet
because unless it collides with other broadcast packet from
another host. So the collision probability decreases.

Thanks and regards.

On 22 dic, 15:25, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

> In this case the situation is different. It's necessary to create a module

> that resends thebroadcastpacket. In my opinion should be your application

> module that after receive the packet re-sent the packet to the network. The
> reactive routing protocol works of this form, the module receive the packet,
> process the packet and if the TTL is enough, re-sent the packet
>
> --------------------------------------------------

> From: "Charlie" <pgpenprue...@gmail.com>

> Sent: Tuesday, December 22, 2009 1:37 PM
> To: "omnetpp" <omn...@googlegroups.com>

> Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
>

> > abroadcastto 2 hops for UDP packets from my UDP Application.

>
> > On 22 dic, 12:54, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

> >> what do you want? abroadcastto 2 hops for any packet? for dymo packet?

>
> >> --------------------------------------------------
> >> From: "Charlie" <pgpenprue...@gmail.com>
> >> Sent: Tuesday, December 22, 2009 12:29 PM
> >> To: "omnetpp" <omn...@googlegroups.com>

Alfonso Ariza Quintana

unread,

Dec 24, 2009, 2:00:24 PM12/24/09

to omn...@googlegroups.com

if you are using wifi (CDMA) the random delay can be smaller that a second, I have tested delays in the ranges of 0-0.05 and 0-0.005 seconds with success

> Date: Thu, 24 Dec 2009 02:28:18 -0800

> Subject: [Omnetpp-l] Re: Broadcast in INETMANET for Omnet 4 fixed?]

> From: pgpenp...@gmail.com
> To: omn...@googlegroups.com
>
> I've done it like you said me. My udp application re-send the
> broadcast packet after receive this packet. But I re-send it in a
> random short time (less than one second) after receive the packet
> because unless it would collide with other broadcast packet from

> another host. So the collision probability decreases.
>
> Thanks and regards.
>
> On 22 dic, 15:25, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

> > In this case the situation is different. It's necessary to create a module

> > that resends thebroadcastpacket. In my opinion should be your application

> > module that after receive the packet re-sent the packet to the network. The
> > reactive routing protocol works of this form, the module receive the packet,
> > process the packet and if the TTL is enough, re-sent the packet
> >
> > --------------------------------------------------

> > From: "Charlie" <pgpenprue...@gmail.com>

> > Sent: Tuesday, December 22, 2009 1:37 PM
> > To: "omnetpp" <omn...@googlegroups.com>

> > Subject: [Omnetpp-l] Re:Broadcastin INETMANET for Omnet 4 fixed?]
> >

> > > abroadcastto 2 hops for UDP packets from my UDP Application.

> >
> > > On 22 dic, 12:54, "Alfonso Ariza" <aariza...@hotmail.com> wrote:

> > >> what do you want? abroadcastto 2 hops for any packet? for dymo packet?

> >
> > >> --------------------------------------------------
> > >> From: "Charlie" <pgpenprue...@gmail.com>
> > >> Sent: Tuesday, December 22, 2009 12:29 PM
> > >> To: "omnetpp" <omn...@googlegroups.com>

¡Windows Phone ya está aquí! Mucho más que un teléfono. ¡Hazte con uno!

ferra adelinna

unread,

May 20, 2017, 1:54:02 AM5/20/17

to OMNeT++ Users

hello mr. alfonso, i have vehicle simulation in veins lte, but i want only using lte network. so what is the suitable application for broadcast message to the vehicle as the UE.

thankyou very much

Reply all

Reply to author

Forward