Hello again,
As part of my Ph.D. research, I am building DS-Lite topology with the help
of VPP hopefully.
My DS-Lite topology in a nutshell (as every normal ds-lite) consists of 4
machines: -
· Sender: IPv4 only machine, sends traffic to the receiver, the
traffic passes at first through B4 router.
· B4 router: receive IPv4 packet, performs encapsulation, then sends
it as IP4 in IPv6 datagram.
· AFTR router: receive the encapsulated packets, decapsulate it and
forward the IPv4 packet to the internal NAT interface, where NAT44 function
to be performed before forwarding the IPv4 packet to the receiver.
· Receiver: normal IPv4 only machine.
So, the idea to be able to ping (ICMP v4) from Sender to receiver while
having IPv6 infrastructure in the middle
I have attached a picture of my topology.
VPP software is supposed to be installed on B4 & AFTR routers, which I did.
Note: Normally B4 & AFTR routers are not directly connected, this is just
for testing purposes.
All interfaces are configured through *“/etc/sysconfig/network-scripts*/”
folder
I have configured the tunnel endpoints on both sides (B4 and AFTR) with
commands below: -
In B4, I added the following: -
*[root@B4 ~]#vppctl*
*vpp# dslite set b4-tunnel-endpoint-address 2001:db8:0:1::2*
*vpp# show dslite b4-tunnel-endpoint-address*
*2001:db8:0:1::2 *
In AFTR, I added the followings: -
*[root@AFTR ~]#vppctl*
*vpp# dslite set aftr-tunnel-endpoint-address 2001:db8:0:1::1*
*vpp# show dslite aftr-tunnel-endpoint-address*
* 2001:db8:0:1::1*
*vpp# dslite add pool address 198.51.100.2 - 198.51.100.10*
*vpp# show dslite pool*
*DS-Lite pool:*
*198.51.100.2*
*198.51.100.3*
*198.51.100.4*
*198.51.100.5*
*198.51.100.6*
*198.51.100.7*
*198.51.100.8*
*198.51.100.9*
*198.51.100.10*
*vpp#*
I am not sure about the “pool” configuration, but this is how I thought it
should be configured.
The thing is, I read the documentation here: -
https://wiki.fd.io/view/VPP/NAT#DS-Lite
However, I am still missing something because the below command shows no
output: -
*vpp# show dslite sessions *
“startup.conf” file is also attached, it is the same for both B4 & AFTR
machines.
Do I need to add API stuff in “startup.conf” ?
To be more honest, I looked at this API config example Below: -
define dslite_add_del_pool_addr_range {
u32 client_index;
u32 context;
u8 start_addr[4];
u8 end_addr[4];
u8 is_add;
};
I couldn’t make sense of it, since I haven’t dealt with API before.
Note: all of my machines are CentOS 7
Any input is highly appreciated.
Regards
Ameen
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
}
plugins {
plugin dslite_plugin.so { enable }
## Adjusting the plugin path depending on where the VPP plugins are
path /usr/lib/vpp_plugins
## Disable all plugins by default and then selectively enable specific
plugins
#plugin default { disable }
plugin dpdk_plugin.so { enable }
plugin acl_plugin.so { enable }
## Enable all plugins by default and then selectively disable specific
plugins
# plugin dpdk_plugin.so { disable }
# plugin acl_plugin.so { disable }
}
nat { endpoint-dependent }
dslite { ce }
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20490): https://lists.fd.io/g/vpp-dev/message/20490
Mute This Topic: https://lists.fd.io/mt/87045923/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-