Bug 2999

Summary:	user doc uses nonexistent GetEpcIpv4NetworkAddress method of PointToPointEpcHelper
Product:	ns-3	Reporter:	Manuel Requena <manuel.requena>
Component:	lte	Assignee:	Manuel Requena <manuel.requena>
Status:	CONFIRMED ---
Severity:	normal	CC:	ns-bugs, tomh, www.ppc007logs
Priority:	P3
Version:	ns-3-dev
Hardware:	All
OS:	All

Description Manuel Requena 2018-10-18 13:21:09 UTC

Parth Pratim reports in the ns-developers list an issue with the lte documentation.
https://mailman.isi.edu/pipermail/ns-developers/2018-October/014574.html

Comment 1 Parth Pratim Chatterjee 2018-10-19 02:50:51 UTC

Can GetUeDefaultGatewayAddress () function be used instead to add a network route from the remote host to the PGW ?

Something Like:

remoteHostStaticRouting->AddNetworkRouteTo (epcHelper->GetUeDefaultGatewayAddress (), Ipv4Mask ("255.255.0.0"), 1);

Comment 2 Manuel Requena 2018-10-19 10:34:14 UTC

Currently, we set this route in the remote host using a hardcoded network.
See lena-simple-epc.cc: 

remoteHostStaticRouting->AddNetworkRouteTo (Ipv4Address ("7.0.0.0"), Ipv4Mask ("255.0.0.0"), 1);

This network is set in the constructor of the PointToPointEpcHelper. The PGW gets one IP address from this network in the PointToPointEpcHelper and the UEs get one IP address from this network in the simulation program with:

ueIpIface = epcHelper->AssignUeIpv4Address (NetDeviceContainer (ueLteDevs));

Comment 3 Parth Pratim Chatterjee 2018-10-19 10:45:09 UTC

Okay, that looks good. 

So this means in the current implementation we would have to define it explicitly just as it is done in lena-simple-epc.cc?