Levente Mészáros

I'm just looking at the github web pages of the source file, so maybe I'm wrong but it seems that it's pretty straightforward to override the other variant in TwoRayGroundReflection.

Just look at the code how it's calculating the pathloss right now. You can do the same in the other (speed/frequency/distance) variant too because the physicalEnvironment field is assigned in...

Indeed, you're right, I missed that part. So, the reason for the other variant is that the dimensional model is capable of telling the power spectral density for all transmissions...

Do you think that this issue is fixed with the merge of your OSPF improvements into maser?

Let me rephrase what you are saying to make sure that I understand correctly. When a packet has a destination address that is assigned to a router's network interface (local...

This bug should be fixed by moving the osgEarth map from the visualizer into a standalone module where both the visualizer and the coordinate system module can access it.

Thank you for the clean description! The reason why the configurator adds those routes is that it doesn't know anything about the interface routes added somewhere else. So I think...

I merged your pull request. I understand what you are saying, but I would also the following. The network configurator should be able to provide a routing configuration that is...

Indeed, the NetworkConfiguratorBase class uses isLoopback() function throughout the code to avoid configuring loopback interfaces.

Which version (branch) are you using? Please take a look at the relevant files from the master branch at: https://github.com/inet-framework/inet/blob/master/src/inet/physicallayer/ieee80211/packetlevel/Ieee80211ScalarTransmitter.cc and at https://github.com/inet-framework/inet/blob/master/src/inet/physicallayer/ieee80211/mode/Ieee80211OFDMMode.h Also, it seems that you mix up...