This is the third part of the series Container Networking. I will explain a little bit about the docker container networking in this blog post. I followed the steps mentioned in this to install docker on Ubuntu. Post docker install, you can see the docker0 device in the list ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
11: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:cf:b4:c1:a8 brd ff:ff:ff:ff:ff:ff Let’s create a busybox container. docker run --name bb -dt busybox docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED              STATUS              PORTS    NAMES
02429964e449   busybox   "sh"      About a minute ago   Up About a minute             bb In the device list, you see the veth7b01920@if16 interface is created with the master as docker0. ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
11: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:cf:b4:c1:a8 brd ff:ff:ff:ff:ff:ff
17: veth7b01920@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default 
    link/ether e2:15:50:88:11:03 brd ff:ff:ff:ff:ff:ff link-netnsid 2 Let’s check the network namespace. ip netns list And you won’t see any network namespaces…How come??? This is because: ip netns list command looks up network namespaces file in the 
/var/run/netns directory.

However, the Docker daemon doesn’t create a reference of
the network namespace file in the /var/run/netns directory
after the creation. Therefore, ip netns ls cannot resolve the
network namespace file

Ref: https://www.baeldung.com/linux/docker-network-namespace-invisible If you want ip netns list to show the namespace name docker has created, then follow the below steps export container_name=bb
container_pid=$(sudo docker inspect -f '' $container_name)
echo $container_pid

sudo touch /var/run/netns/$container_name
sudo mount -o bind /proc/$container_pid/ns/net /var/run/netns/$container_name Now, you can see the namespace name. ip netns list
bb (id: 0) sudo ip netns exec bb ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
16: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0 The following diagram will help you visualize it better. With this, I’m signing off. I hope this blog series helps to de-clutter container networking. This is the third part of the series Container Networking . I will explain a little bit about the docker container networking in this blog post. Container Networking I followed the steps mentioned in this to install docker on Ubuntu. this Post docker install, you can see the docker0 device in the list docker0 ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
11: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:cf:b4:c1:a8 brd ff:ff:ff:ff:ff:ff ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
11: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:cf:b4:c1:a8 brd ff:ff:ff:ff:ff:ff Let’s create a busybox container. docker run --name bb -dt busybox docker run --name bb -dt busybox docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED              STATUS              PORTS    NAMES
02429964e449   busybox   "sh"      About a minute ago   Up About a minute             bb docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED              STATUS              PORTS    NAMES
02429964e449   busybox   "sh"      About a minute ago   Up About a minute             bb In the device list, you see the veth7b01920@if16 interface is created with the master as docker0. veth7b01920@if16 ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
11: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:cf:b4:c1:a8 brd ff:ff:ff:ff:ff:ff
17: veth7b01920@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default 
    link/ether e2:15:50:88:11:03 brd ff:ff:ff:ff:ff:ff link-netnsid 2 ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
11: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:cf:b4:c1:a8 brd ff:ff:ff:ff:ff:ff
17: veth7b01920@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default 
    link/ether e2:15:50:88:11:03 brd ff:ff:ff:ff:ff:ff link-netnsid 2 Let’s check the network namespace. ip netns list ip netns list And you won’t see any network namespaces…How come??? This is because: ip netns list command looks up network namespaces file in the 
/var/run/netns directory.

However, the Docker daemon doesn’t create a reference of
the network namespace file in the /var/run/netns directory
after the creation. Therefore, ip netns ls cannot resolve the
network namespace file

Ref: https://www.baeldung.com/linux/docker-network-namespace-invisible ip netns list command looks up network namespaces file in the 
/var/run/netns directory.

However, the Docker daemon doesn’t create a reference of
the network namespace file in the /var/run/netns directory
after the creation. Therefore, ip netns ls cannot resolve the
network namespace file

Ref: https://www.baeldung.com/linux/docker-network-namespace-invisible If you want ip netns list to show the namespace name docker has created, then follow the below steps ip netns list export container_name=bb
container_pid=$(sudo docker inspect -f '' $container_name)
echo $container_pid

sudo touch /var/run/netns/$container_name
sudo mount -o bind /proc/$container_pid/ns/net /var/run/netns/$container_name export container_name=bb
container_pid=$(sudo docker inspect -f '' $container_name)
echo $container_pid

sudo touch /var/run/netns/$container_name
sudo mount -o bind /proc/$container_pid/ns/net /var/run/netns/$container_name Now, you can see the namespace name. ip netns list
bb (id: 0) ip netns list
bb (id: 0) sudo ip netns exec bb ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
16: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0 sudo ip netns exec bb ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
16: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0 The following diagram will help you visualize it better. With this, I’m signing off. I hope this blog series helps to de-clutter container networking.

A Guide to Container Networking: Part III - Docker Container Networking

This is the second part of the series Container Networking. I will cover Network Namespaces and Linux Bridges in this blog post. Linux Namespaces wiki says Namespaces are a feature of the Linux kernel that partition kernel resources 
such that one set of processes sees one set of resources, while another set 
of processes sees a different set of resources. So, the process isolation is provided using namespaces and cgroups. This allows each process to see its personal view of the system (files, process, network interfaces, hostname). Another excerpt from the wiki. ince kernel version 5.6, there are 8 kinds of namespaces. 
Network namespaces virtualize the network stack. On creation, a network 
namespace contains only a loopback interface. Each network interface 
(physical or virtual) is present in exactly 1 namespace and can be moved 
between namespaces. ip-netns utility helps to create network namespaces. Let’s see how. Network Namespaces Demo Create a network namespaces. sudo ip netns add ns1 List them. ip netns list
ns1 Only the loopback interface is available in ns1 namespace. sudo ip netns exec ns1 ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 The following diagram helps to visualize the setup. For brevity, I will not list lo and enp0s3 interfaces in the rest of the diagrams. Now, let’s create a veth pair. sudo ip link add vethX type veth peer name vethY
sudo ip link set vethX up
sudo ip link set vethY up Attach one end of the veth pair to ns1 namespace. sudo ip link set vethX netns ns1 This ensures processes in the default/root namespace cannot see vethX interface. ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
18: vethY@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5a:bc:4d:7e:76:b1 brd ff:ff:ff:ff:ff:ff link-netns ns1 And processes in ns1 namespace could not see vethY interface. sudo ip netns exec ns1 ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
19: vethX@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5e:4b:13:90:7d:63 brd ff:ff:ff:ff:ff:ff link-netnsid 0 In a similar fashion, we can create another namespace. Create a new veth pair. And then attach one end of veth pair to a namespace. udo ip netns add ns2
sudo ip link add vethP type veth peer name vethQ
sudo ip link set vethP up
sudo ip link set vethQ up
sudo ip link set vethP netns ns2 Now, the last part is to connect these two namespaces with a Bridge. A bridge connects two LAN segments together. We will create a new bridge and attach vethY and vethQ to this bridge. sudo ip link add name br0 type bridge
sudo ip link set dev br0 up
sudo ip link set vethY master br0
sudo ip link set vethQ master br0 As we have looked in the last blog post, any packet on bridge br0 is seen on all the veths we have created. You can try it for yourself. Now, by this time, you might have started imagining how a container achieves network isolation using Virtual Ethernet, Bridge, and Linux Namespaces. We will take a look at the docker container in the next blog post. Before you jump to the next article, let’s clean up the setup. sudo ip link del br0
sudo ip link del vethY
sudo ip link del vethQ
sudo ip netns del ns1
sudo ip netns del ns2 This is the second part of the series Container Networking . I will cover Network Namespaces and Linux Bridges in this blog post. Container Networking Linux Namespaces wiki says wiki Namespaces are a feature of the Linux kernel that partition kernel resources 
such that one set of processes sees one set of resources, while another set 
of processes sees a different set of resources. Namespaces are a feature of the Linux kernel that partition kernel resources 
such that one set of processes sees one set of resources, while another set 
of processes sees a different set of resources. So, the process isolation is provided using namespaces and cgroups. This allows each process to see its personal view of the system (files, process, network interfaces, hostname). Another excerpt from the wiki . wiki ince kernel version 5.6, there are 8 kinds of namespaces. 
Network namespaces virtualize the network stack. On creation, a network 
namespace contains only a loopback interface. Each network interface 
(physical or virtual) is present in exactly 1 namespace and can be moved 
between namespaces. ince kernel version 5.6, there are 8 kinds of namespaces. 
Network namespaces virtualize the network stack. On creation, a network 
namespace contains only a loopback interface. Each network interface 
(physical or virtual) is present in exactly 1 namespace and can be moved 
between namespaces. ip-netns utility helps to create network namespaces. Let’s see how. ip-netns Network Namespaces Demo Create a network namespaces. sudo ip netns add ns1 sudo ip netns add ns1 List them. ip netns list
ns1 ip netns list
ns1 Only the loopback interface is available in ns1 namespace. ns1 sudo ip netns exec ns1 ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 sudo ip netns exec ns1 ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 The following diagram helps to visualize the setup. For brevity, I will not list lo and enp0s3 interfaces in the rest of the diagrams. lo enp0s3 Now, let’s create a veth pair. veth sudo ip link add vethX type veth peer name vethY
sudo ip link set vethX up
sudo ip link set vethY up sudo ip link add vethX type veth peer name vethY
sudo ip link set vethX up
sudo ip link set vethY up Attach one end of the veth pair to ns1 namespace. veth ns1 sudo ip link set vethX netns ns1 sudo ip link set vethX netns ns1 This ensures processes in the default/root namespace cannot see vethX interface. vethX ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
18: vethY@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5a:bc:4d:7e:76:b1 brd ff:ff:ff:ff:ff:ff link-netns ns1 ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 02:fd:4d:34:55:76 brd ff:ff:ff:ff:ff:ff
18: vethY@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5a:bc:4d:7e:76:b1 brd ff:ff:ff:ff:ff:ff link-netns ns1 And processes in ns1 namespace could not see vethY interface. ns1 vethY sudo ip netns exec ns1 ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
19: vethX@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5e:4b:13:90:7d:63 brd ff:ff:ff:ff:ff:ff link-netnsid 0 sudo ip netns exec ns1 ip link
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
19: vethX@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5e:4b:13:90:7d:63 brd ff:ff:ff:ff:ff:ff link-netnsid 0 In a similar fashion, we can create another namespace. Create a new veth pair. And then attach one end of veth pair to a namespace. veth veth udo ip netns add ns2
sudo ip link add vethP type veth peer name vethQ
sudo ip link set vethP up
sudo ip link set vethQ up
sudo ip link set vethP netns ns2 udo ip netns add ns2
sudo ip link add vethP type veth peer name vethQ
sudo ip link set vethP up
sudo ip link set vethQ up
sudo ip link set vethP netns ns2 Now, the last part is to connect these two namespaces with a Bridge. A bridge connects two LAN segments together. We will create a new bridge and attach vethY and vethQ to this bridge. vethY vethQ sudo ip link add name br0 type bridge
sudo ip link set dev br0 up
sudo ip link set vethY master br0
sudo ip link set vethQ master br0 sudo ip link add name br0 type bridge
sudo ip link set dev br0 up
sudo ip link set vethY master br0
sudo ip link set vethQ master br0 As we have looked in the last blog post , any packet on bridge br0 is seen on all the veths we have created. You can try it for yourself. last blog post br0 veths Now, by this time, you might have started imagining how a container achieves network isolation using Virtual Ethernet, Bridge, and Linux Namespaces. We will take a look at the docker container in the next blog post . next blog post Before you jump to the next article, let’s clean up the setup. sudo ip link del br0
sudo ip link del vethY
sudo ip link del vethQ
sudo ip netns del ns1
sudo ip netns del ns2 sudo ip link del br0
sudo ip link del vethY
sudo ip link del vethQ
sudo ip netns del ns1
sudo ip netns del ns2

A Guide to Container Networking: Part II - Network Namespaces and Linux Bridges

Container Networking Guide: Part I

How Digital Platforms Undo Paperwork In Real Estate

How to Effectively Evaluate Your RAG + LLM Applications

কীভাবে কার্যকরভাবে আপনার RAG + LLM অ্যাপ্লিকেশনগুলিকে মূল্যায়ন করবেন

So bewerten Sie Ihre RAG- und LLM-Anwendungen effektiv

Cómo evaluar eficazmente sus solicitudes RAG + LLM

Comment évaluer efficacement vos candidatures RAG + LLM

अपने आरएजी + एलएलएम अनुप्रयोगों का प्रभावी ढंग से मूल्यांकन कैसे करें

RAG + LLM アプリケーションを効果的に評価する方法

RAG + LLM 지원서를 효과적으로 평가하는 방법

Como avaliar efetivamente suas inscrições RAG + LLM

Как эффективно оценить ваши заявки на RAG + LLM

RAG + LLM Başvurularınızı Etkin Bir Şekilde Nasıl Değerlendirebilirsiniz?

Cách đánh giá hiệu quả các ứng dụng RAG + LLM của bạn

如何有效评估您的 RAG + LLM 申请

Problem Residential proxies have a lot of useful applications, such as web scraping, online research, bypassing geo-restrictions and anonymous browsing. But, they can be expensive, with some charging more than $100 a month for access to over 10 GB of data. Last year, when I was travelling to India and other parts of Southeast Asia, I wanted a reliable way which would let me access content on various subscription services like Netflix and Amazon Prime without geo-restrictions. I wanted to do this while Not having to pay more than $100 per month for VPN/residential proxy service. Also, Netflix would occasionally block me when using VPN. Not paying an additional amount for a static IP for my home internet connection back in the US. Solution I discovered a solution by creating my own residential proxy on my home desktop in the US. By setting up a peer-to-peer(P2P) VPN and connecting my laptop and desktop to it, I was able to route the traffic of my laptop in India to my desktop in the US, which then forwarded these requests to www/public internet before returning the response from my home network. All this without having to go through the hassle of setting up connection forwarding configuration in my home router. What is a P2P VPN Peer-to-peer(P2P) is an architecture model for VPNs used to create a secure shared environment for users. A P2P based VPN differs from the standard hub-and-spoke model by not routing all traffic through a central server, avoiding congestion. This improves security and allows for more efficient scaling by adding nodes without overburdening the network. Additionally, connections in a P2P VPN utilize the quickest path, reducing delays. There a multiple open-source, freemium and paid P2P VPN solutions available. Tinc is one of popular open-source VPN. How does the network setup look? The network stack consists of the following components: Desktop at home (US) My laptop (Outside US) P2P vpn daemon running on both machine via same account Http proxy server running on the desktop The diagram below depicts the flow of information to retrieve a public webpage from my laptop outside of the US. I wanted a P2P VPN which is easy to setup and requires near-zero config. I ended up using tailscale. The steps below are mostly generic for any VPN but you may find this most suitable if using tailscale. Steps taken to setup this network : Setting up the vpn client on desktop and laptop Download and install VPN client on desktop and laptop. If using a zero-config VPN, register your account with vpn and sign-in on both the machines with the same account : Setting up a forward http proxy server on desktop You can use any open source proxy server. I used https://github.com/abhinavsingh/proxy.py as it was easy to set up. I ran it within a docker container. The docker image for this proxy is available on docker hub.  To run it within a docker container you can execute this command docker run -it -p 8899:8899 --rm abhinavsingh/proxy.py:latest In the command above, the proxy server is listening on port 8899. This will be useful when we specify the url of proxy server in the applications within the laptop : After installing and signing into your VPN account, lets figure out the ip address of the desktop which will be used by the laptop to forward its http requests . Identify the ip address of desktop in the VPN network For this, you can list the ip addresses for all the network interfaces on the desktop. Then identify the ip address for an interface whose name starts with the name of your VPN client, for my case, it starts with “tailscale”. I used the command on my linux machine’s terminal to identify the ip address ip $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
….
4: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 100.113.xxx.xx/32 scope global tailscale0
       valid_lft forever preferred_lft forever
 … Here I was able to find the ip address of desktop within my local tailscale network in the network interface : tailscale0 100.113.xxx.xx Using the address of proxy server on laptop to access public web: Now that we know the ip address of desktop (let's call it ) and the port number for the http proxy server on desktop (let’s call it ), we can forward all the network traffic from laptop via proxy address . $ip_desktop $proxy_port http://$ip_desktop:$proxy_port For example you can send a curl request to example.com from laptop via desktop like curl --proxy "http://$ip_desktop:$proxy_port" "https://example.com" Using the proxy server The above instructions demonstrate how to create a free residential proxy server while travelling using a spare computer at home. Now you can use this proxy address on your personal laptop in any of the following ways: Within your application code inside the http client libraries of your web framework/language (requests in python, fetch in javascript etc) For all the web requests from your laptop. This way you can forward any kind http request via desktop’s proxy server. In ubuntu you can do this by following these steps https://help.ubuntu.com/stable/ubuntu-help/net-proxy.html.en Just in your browser. Although Chrome and Firefox don’t provide a native way to setup exclusive http proxy settings for them, you can do this via extensions like https://github.com/foxyproxy/firefox-extension I chose 2. and forwarded all the http requests from my laptop to desktop. I used this setup for more than two months without any noticeable downtime. Conclusion In this article we went over how to setup a personal residential proxy using P2P VPN Two or more personal computers Depending on the choice of the VPN, the whole setup can be done without any additional cost, assuming you already own multiple computers. Using this residential proxy you can then access the internet anonymously without any geo-restrictions due to your current physical location.

How to Create a Personal Residential Proxy to Bypass Geo Restrictions

জিও সীমাবদ্ধতা বাইপাস করার জন্য কীভাবে একটি ব্যক্তিগত আবাসিক প্রক্সি তৈরি করবেন

So erstellen Sie einen persönlichen Wohn-Proxy, um geografische Beschränkungen zu umgehen

Cómo crear un proxy residencial personal para eludir las restricciones geográficas

Comment créer un proxy résidentiel personnel pour contourner les restrictions géographiques

भू-प्रतिबंधों को बायपास करने के लिए व्यक्तिगत आवासीय प्रॉक्सी कैसे बनाएं

地理的制限を回避するための個人用の住宅用プロキシを作成する方法

지리적 제한을 우회하기 위해 개인 주거용 프록시를 만드는 방법

Como criar um proxy residencial pessoal para contornar as restrições geográficas

Coğrafi Kısıtlamaları Aşmak için Kişisel Konut Proxy'si Nasıl Oluşturulur

Cách tạo Proxy dân cư cá nhân để vượt qua các hạn chế về địa lý

如何创建个人住宅代理来绕过地理限制

Use Beta Distribution and Thompson Sampling to Beat The Multi-armed Bandit at the Casino

David Clinton is the author of Linux, AWS, Docker, and security courses on Pluralsight, and technology books, including Manning’s Linux in Action , Learn Amazon Web Services in a Month of Lunches , and a hybrid course called Linux in Motion that’s made up of more than two hours of video and around 40% of the text of Linux in Action. : As of November 7, 2018, there’s an that could allow a user on the guest full access to the host machine. Until further notice, do NOT use VirtualBox with the default network settings. . NOTE unpatched zero-day vulnerability in VirtualBox Details are available here In the meantime, feel free to enjoy the original article: Of course you’re getting your money’s worth. VirtualBox is free, isn’t it? Ok, so then why not double the return on your investment? Why not find out how much more you can accomplish as a VirtualBox power user? Oracle’s VirtualBox is easy to install, easy to use, and gives you the ability to run virtual versions of just about any modern operating system from within any other modern operating system. Windows 10 on Ubuntu Linux? I’ve done it myself. FreeBSD on CentOS Linux? Sure, why not? You can, of course, do similar stuff with the free VMware Player tool and, on Windows 8 and up, with Hyper-V. But this article is about VirtualBox. I’d been using VirtualBox for years, but it wasn’t until I needed to pull together a number of physical machines sitting around the house to use as nodes in a that things got complicated. After all, manually creating and launching VMs would require spending some serious time in front of each PC, babysitting OS installations and configurations. And that, in turn, would mean climbing stairs and sitting on the truly awful chairs in my kids’ rooms. Don’t tell them I said this, but I haven’t a clue why they put up with them. Docker swarm mode network It turns out that SSH connectivity between my (Linux) PCs and some very basic knowledge of the command line shell were all it took to return me to my lazy sysadmin happiness. It was liberating, and you could probably use some liberation of your own. vboxmanage But before going there, I’ll talk a bit about the way VirtualBox works and the kinds of things you can do with it. Feel free to skip ahead if that doesn’t sound interesting. What’s my angle in all this? While engaging in research for my various and , I often build test environments that include machines running odd combinations of operating systems. For some purposes — especially when I need to work at the operating system kernel level — VirtualBox has repeatedly proven to be the fastest and most effective tool I’ve got. I’m not sure I’d ever want to use a resource-greedy VirtualBox virtual machine to run permanent services, but for test and development related cases, it’s absolutely king of the hill. books Pluralsight video courses That’s me. But is my experience useful for normal users? In the sense that, once in a while at least, everyone needs to check out new technologies, then absolutely. But I guess I am a bit unusual in that I very rarely move to production. I’m always testing. Working with VirtualBox Besides letting you try out entirely new operating systems without having to dig through the garage for unused (but usable) hardware components, VirtualBox is also a terrific sandbox. So even if you don’t really care what OS you’re running, but you’re not too keen on risking the health and welfare of your main workstation on some experimental software configuration, VirtualBox can help. This will also work if the experimental software configuration is your own. Which is to say that VirtualBox can be used as a tool for safely testing the way your own development projects handle within multiple OS environments. And don’t forget that VirtualBox is very widely used as a provider for the Vagrant configuration automation system. As I briefly wrote in my , VirtualBox is a type-2 hypervisor. And so it is. But it’s a hypervisor with such a light footprint that, feature-for-feature, it can sometimes compete with container technologies like Docker and LXC/LXD. That opens VirtualBox up to a fairly wide range of uses. But since the overlap can get complicated, here (because you can never have too many spreadsheets) is a visual technology vs. technology comparison: Linux Server Virtualization article An unscientific feature/use-case matrix for virtualization technologies Getting Stuff Done Enough talk already. Let’s get to work. The VirtualBox GUI is all very pretty, but it’ll really slow you down when you’re firing up VMs on multiple network hosts. So here are some tools that will make things happen — both locally or through a remote connection — from the command line. Install VirtualBox. Here’s how it’s done on Ubuntu or Debian, at any rate: $ sudo apt install virtualbox Now it is possible to remotely create a new VM from scratch using commands like these: vboxmanage list ostypesvboxmanage createhd --filename Ubuntu64.vdi --size 16384VBoxManage createvm --name Ubuntu64 --ostype “Ubuntu_64” --register …But displaying the actual installation interface on a remote screen can sometimes be more trouble than it’s worth. Instead, let’s assume that you’ve already got a “golden-image” VirtualBox VM on your local workstation. You’ll want to use to see what‘s there. vboxmanage list vms Here’s what it looked like on my workstation: $ vboxmanage list vms“Ubuntu-16.04-template” {c00d3b2b-6c77–4919–85e2–6f6f28c63d56}“Ubuntu14-template” {43e2f9d4–8aa1–4db4-aa59–33b202df32ed}“centos-7-template” {e2613f6d-1d0d-489c-8d9f-21a36b2ed6e7}“Kali-Linux-template” {b7a3aea2–0cfb-4763–9ca9–096f587b2b20}“Kali-Linux-openvas” {1ec41fdd-bf14–4025–9e9e-ee7272acf87f}“docker-project” {2387a5ab-a65e-4a1d-8e2c-25ee81bc7203}“Ubuntu-16-lxd” {62bb89f8–7b45–4df6-a8ea-3d4265dfcc2f} Note, by the way, how I keep clean “template” copies of individual operating systems and then create cloned copies whenever I need to do some actual work. Believe me, this can really speed up your time-to-launch over having to go through the whole installation routine each time. You can create clones from the GUI, or using like this (where “Kali-Linux-template” is the name of an existing VM and “newkali” is the name we’d like to give to the clone): clonevm $ vboxmanage clonevm Kali-Linux-template --name newkali Check out the argument details on the . clonevm VirtualBox documentation page here Here, however, I’m going to show you how to export an existing VM to a .OVA file that you can simply copy to your remote machines and then import into their instances of VirtualBox. The export operation couldn’t be simpler: you enter the name of the VM you want to export (docker-project, in my case), to specify an output filename, and the filename itself with the appropriate file extension. -o $ vboxmanage export docker-project -o docker.ova0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100%Successfully exported 1 machine(s). The file will be saved to your current directory. You can display the details of the file you’ve just created: $ ls -lh | grep docker-rw — — — — 1 root root 2.1G Jun 4 17:01 docker.ova One way or another, you’ll need to copy the .OVA file to your other PCs. Here’s how the file transfer might work between Linux/MAC OS machines using scp: $ scp docker.ova username@192.168.0.34:/home/username Naturally, you’ll have to make sure you’ve got enough free disk space to both save the .OVA file itself (which can be quite large) create the new VM. and Now log in to your remote machine and, from the directory containing the file you’ve just transferred, import it into VirtualBox: $ vboxmanage import docker.ova0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100%Interpreting /home/dad/docker.ova…OK.Disks:vmdisk2 36945920000 -1 docker-disk1.vmdk -1–1 http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized Virtual system 0:0: Suggested OS type: "Ubuntu_64"(change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)1: Suggested VM name "docker-project"(change with "--vsys 0 --vmname <name>")2: Number of CPUs: 1(change with "--vsys 0 --cpus <n>")3: Guest memory: 2048 MB(change with "--vsys 0 --memory <MB>")4: Sound card (appliance expects "", can change on import)(disable with "--vsys 0 --unit 4 --ignore")5: USB controller(disable with "--vsys 0 --unit 5 --ignore")6: Network adapter: orig Bridged, config 3, extra slot=0;type=Bridged7: CD-ROM(disable with "--vsys 0 --unit 7 --ignore")8: IDE controller, type PIIX4(disable with "--vsys 0 --unit 8 --ignore")9: IDE controller, type PIIX4(disable with "--vsys 0 --unit 9 --ignore")10: SATA controller, type AHCI(disable with "--vsys 0 --unit 10 --ignore")11: Hard disk image: source image=docker-disk1.vmdk, target path=/home/dad/VirtualBox VMs/docker-project/docker-disk1.vmdk, controller=10;channel=0(change target path with "--vsys 0 --unit 11 --disk path";disable with "--vsys 0 --unit 11 --ignore")0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%Successfully imported the appliance. You’ll want to confirm that everything worked by running : list vms $ vboxmanage list vms“docker-project” {30ec7f7d-912b-40a9–8cc1-f9283f4edc61} You can connect your VM to a network using . But, before you can do that, you’ll need to know how your host machine refers to the appropriate network interface. On a Linux machine, you can get that using . In this case, the second interface that’s displayed (“eth0” — that’s “eth” followed by a zero…not the letter o) is the NIC through which that machine gets its internet access, so it’s the connection we’re after. vboxmanage modifyvm ip addr $ ip addr1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000link/ether 94🇩🇪80:c5:1e:2d brd ff:ff:ff:ff:ff:ffinet 192.168.1.13/24 brd 192.168.1.255 scope global dynamic eth0valid_lft 59857sec preferred_lft 59857secinet6 fe80::e1c3:f8a2:9f8d:4375/64 scope linkvalid_lft forever preferred_lft forever eth0: One way to move your VM’s (virtual) network card onto the eth0 interface by way of a bridge adapter is through the command. In this case, “docker-project” points to the VM name, and eth0 is the target of the new bridge, connecting your VM’s internal network interface with the host’s eth0. modifyvm $ vboxmanage modifyvm “docker-project” --bridgeadapter1 eth0 Now you’re ready to fire up the VM. The “type headless” argument tells VirtualBox to run the VM as a server without a GUI. $ vboxmanage startvm “docker-project” type --headlessWaiting for VM “docker-project” to power on…VM “docker-project” has been successfully started. Curious about what’s going on with your new VM? Try : showvminfo $ vboxmanage showvminfo docker-project You may need to run a network search program like nmap to get your VM’s IP address. With that piece of information, you’ll be ready to get to work. Log in to your new VM using the same credentials you used on the source VM from which it was copied. Shutting down a VM once you’re done with it is as simple as running the command: poweroff $ VBoxManage controlvm “docker-project” poweroff0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100% Happy virtualizing! a hybrid course called that’s made up of more than two hours of video and around 40% of the text of Linux in Action_._ David Clinton is the author of Linux, AWS, Docker, and security courses on Pluralsight, and technology books, including Manning’s Linux in Action , Learn Amazon Web Services in a Month of Lunches , and Linux in Motion

VirtualBox: Are You Getting Your Money’s Worth?

There is no harder feeling than identifying the best tools to get something done and not being able to explore it efficiently. Over the years, there have been different Artificial Intelligence and Generative AI tools similar to ChatGPT but none of the free tools matched the complexity of ChatGPT chat features. While the tool may be frowned upon by certain professionals, it is of no doubt highly beneficial and recommended for anyone who can use it effectively. These tools can be used to generate written content such as blog articles, emails, landing page copies and visuals for illustration purposes. In this article, I will share hacks on how great prompt engineering can help anyone get the best from Generative AI tools like ChatGPT, Midjourney and DALL-E. was launched in November 2022 by OpenAI, leveraging OpenAI’s GPT-3.5 language models. The tool has gained viral attention from leading experts across the world and recorded over one million users in less than a month after the launch. There are several screenshots and testimonials from users on the internet on how helpful the tool has been from professionals to university students, bloggers and influencers. ChatGPT Prompt engineering is a popular technical concept that explains the relationship between input (prompts) and outputs (results) for Generative AI models. Simply put, the quality and relevance of results that can be derived from Generative AI like ChatGPT are highly dependent on the quality and contextual mapping of the prompts or requests. Being able to craft great prompts can help get helpful responses from and ensure the NLP models understand the request and can equally provide relevant and accurate responses. ChatGPT Here are the top five tips for writing quality request prompts for NLP models. This is of course the most important and highly untapped hack. Ensure you build conversations and provide enough context, just as you would when chatting with a human. Don’t just get into the prompts without building some background information to aid further decisions. Start by engaging the chatbot with some information about the field or request type, ask questions to validate assumptions, and then begin by asking questions in batches. Build a conversation: : Do away with complex sentence structure or Shakespearean vocabulary when typing request prompts. Make your prompts straightforward and as simple as possible. ChatGPT is designed to process and respond to simple requests, making it easier for you and the tool. Keep it short and simple (KISS) : Ensure your prompt is specific and includes what ChatGPT should and not do. For example, instead of saying “ ”, you can try “ ”. This will further help the model understand the objectives for the prompt and provide favourable responses. Specify requests Tell me how to distribute my article Tell me how to distribute my article online assuming I don’t have a Twitter account : Engage with the bot politely and respectfully as it is designed to mimic human conversations. Ensure to use proper grammar and punctuation to help the model understands what you are asking. Proper grammar and politeness : There is no better way to further enhance the quality of responses for ChatGPT than providing additional feedback to the team. Feel free to click on the thumbs icon (thumbs up preferably) and share some more information on what would the ideal answer have been. Give rating and feedback Prompt engineering is being able to communicate clearly what a Generative AI should do and the only limit is the inability to express the exact briefs clearly. This can further help creatives, engineers, product managers and consultants generate great briefs to avoid wasting time and second-guessing. If done right, it can also help maintain consistent brand guidelines and get out-of-the-world inspiration or ideas. I strongly believe following the above-listed tips and using specific, clear, and contextual request prompts, you can get the best responses from ChatGPT for a wide range of enquiries for your personal and professional endeavours. Here are some examples of prompts and requests for different types of enquiries: : Engineering “What is the formula for calculating the volume of a cylinder?” “Can you explain how a hydraulic system works?” “What is the principle behind the operation of a steam turbine?” Medical enquiries: “What are the symptoms of the flu?” “How can I treat a sprained ankle at home?” “What are the risks of taking aspirin during pregnancy?” Education: “Can you explain the process of photosynthesis?” “What is the significance of the Declaration of Independence?” “How do I solve this math problem: 2x + 3y = 12?” Entertainment: “Tell me a joke about a penguin.” “Can you recommend a good book to read about drums?” “What are some interesting facts about the Great Wall of China?” Conclusively, there will be more demands for “ ” in a few years given the rise of generative AI tools such as ChatGPT, Midjourney and DALL-E. In my next article, I will give in-depth examples of the terminologies for writing prompts using request mapping categories from fields/industries, formats, perspectives, limitations and boosters. Prompt Engineers Also published . here

Prompt Engineering for ChatGPT and Generative AI

Let’s all agree: the pandemic has reshaped the global supply chain. Multiple lockdowns paired with temporary trade restrictions and workforce shortages unveiled vulnerabilities in supply chains that were previously unseen. The drastic change of the landscape forced supply chain executives to up their strategic management game. To do so, some of them have turned to innovative technologies, with supply chain AI leading the race. In fact, while it is a standard practice for enterprises to hold up their digital transformation projects in times of economic uncertainty, the COVID-19 crisis did not stop supply chain decision-makers from turning to . that 92% of the surveyed senior-level executives carried on with their investments. The reasoning? A positive value of AI in the supply chain. artificial intelligence solutions providers A study suggests Below, we look at how artificial intelligence helps supply chains run effectively, investigate the outcomes AI in the supply chain can yield, and share tips on jumping on the digital supply chain bandwagon in a risk-free manner. AI in the supply chain: how it helps hit strategic management targets At the beginning of 2021, Ernst and Young surveyed 200 senior-level supply chain executives to reveal their top priorities for the next 12 to 36 months. Here is what they found: The number one strategic target for supply chain decision-makers is increasing supply chain efficiency The second objective they look to achieve is to gain better visibility into their supply chains Other targets that top off the global supply chain agendas are boosting resilience and optimizing supply chain management costs Artificial intelligence is becoming essential to bringing these strategic transformations to life. As a matter of fact, 95% of the highest-performing organizations . see AI as a cornerstone of their supply chain success Here’s a more detailed look at the use cases of AI in the supply chain that help achieve the targets mentioned above. Use cases of AI in supply chain management that increase operational efficiency Demand forecasting Understanding the sources of demand has never been more challenging. With customer expectations changing quickly and getting more diverse, businesses now rely on AI-powered supply chain tools to glean more demand-related insights — and tune their production strategies accordingly. Integrating available data about each process within the supply chain (even real-time information) and running this data through AI algorithms can help businesses establish a unified view of demand and make more thoughtful decisions. The data for analysis can be gathered from internal sources, such as orders and sales, or external sources, for example, macroeconomic factors, brand sentiment, and the number of COVID-19 cases. As a result of such planning, AI is capable to return a detailed report of potential consumption volumes, broken down by customer and location levels. And with the detailed demand data on hand, businesses can optimize their production volumes, reduce inventory levels, store more goods closer to their customers, and cut down on unnecessary shipments. Laying out best delivery routes Leveraging AI in supply chain management can also help design better delivery routes and optimize fleet utilization. Considering such criteria as supplier and manufacturing sites, storage locations, potential wear and tear of machinery, and fuel usage, AI-based supply chain solutions come up with an optimal route and provide for a speedier flow of items along the supply chain. Last-mile deliveries and driverless cars Driverless cars and last-mile delivery robots (that rely on AI, too) have a chance to transform supply chains by decreasing dependence on human drivers and optimizing delivery routes. Still, according to BCG, merely 10% of trucks will likely operate autonomously by 2030. Delivery drones and bots, in turn, have already won significant popularity. They are increasingly being used to deliver at shorter distances or to places where the ground transfer is not safe, reliable, or sustainable. Hybrid solutions combining delivery vans and drones have recently emerged, too. Amazon, for example, works on a system whereby vans deliver items close to their destination and then send out an AI-controlled drone for the final drop-off. Use cases of AI in supply chain management that provide for better visibility Inventory management Adopting AI in supply chain management can help uncover the performance of inventory across various channels and sellers and identify anomalies, like delays or low inventory levels. With detailed inventory data, enterprises can adjust their inventory strategies to operate more efficiently. Order management AI-powered supply chain platforms facilitate order management and help bring together multiple supply chain players involved in the process. For example, an ITRex helped develop can predict order shipment costs based on up to 60 parameters, process customer requests to eliminate duplicate orders and suggest better carrier matching options, and track shipments from dispatch to delivery. AI-based cargo management platform Use cases of AI in supply chain management that increase resilience Predictive analytics for risk management The pandemic has pushed risk management to the top of every corporate agenda. McKinsey reports that 59% of businesses have adopted a new approach to supply chain risk management over the past year. One typical example of how applying AI in the supply chain advances risk management is optimizing supplier evaluation, flagging suppliers as low-, medium-, or high-risk. For that, an AI solution could weigh out such metrics as the impact on revenues a business is likely to face if a particular source is lost, the time it would take a specific supplier to recover from a disruption, the availability of alternative sources, and other data. Another way of leveraging AI for the supply chain is predicting supply chain disruptions. Feeding off historical operational data, AI could help identify and correct operational inefficiencies in real time, providing an in-depth look into the supply chain performance, opportunities, and risks. Doing so proactively allows supply chain executives to operate at lower costs without sacrificing efficiency. In fact, according to McKinsey, organizations that have adopted AI report a 44% reduction in operating expenses. Digital twins Expanding the reliance on artificial intelligence in the supply chain even further,, businesses can create so-called digital twins — virtual simulations of all corporate assets, warehouses, routes, and materials and product flows. Digital twins help design more resilient and effective supply chains and allow testing out the supply chain performance and foreseeing risks. AI in the supply chain: five real-world examples Let’s look at the examples of companies that have already adopted AI for supply chain management. Amazon The ecommerce giant uses AI-based predictive analytics to power its supply chain and predict demand for products before purchasing and stocking its warehouses. The company says predictive analytics has become a backbone for its supply chain strategy. AI-powered demand forecasting “kicks off the supply chain” and helps the company determine which products, and how much of each, to buy. UPS The company uses AI to manage the flow of packages. The company’s staff gets a bird’s eye view of the number of packages in the delivery network, the expected peaks in the volume of goods en route, as well as potential disruptions. The AI-based supply chain solution relies on historical and real-time information, including weather and traffic data, to devise the fastest and safest ways to deliver packages. DHL The company employs an AI-based tool for predicting air freight delays. The solution analyzes 58 data points and predicts delays or speed-ups a week in advance. The tool also indicates the reasons why the changes to the itinerary might occur. FedEx The delivery service uses Roxo — a robot that relies on AI to automate last-mile deliveries. The robot is designed to be used in a three-to-five-mile radius of storage facilities. It has helped the company satisfy the needs of its customers better and improve its performance benchmarks. Echo Global Logistics The transportation management company builds on AI to ship goods quickly, securely, and cost-effectively. The areas where the company employs AI are manifold — from optimizing the procurement of transportation to carrier management to intelligent shipment tracking. Embarking on an AI-driven supply chain transformation journey About 60% of projects dealing with AI in supply chain management are either delivered late or over budget. We have laid out an AI adoption roadmap to help you overcome AI implementation challenges and ease your supply chain transformation journeys. Step 1. Formulate a business case and think over the strategic aspects of AI adoption Only a third of companies ushering in AI-driven transformation performs a diagnostic audit before rolling out the technology. To make sure you are not missing out on the opportunities of AI, we recommend kicking off your digitization project by identifying and prioritizing the possibilities for value creation across all supply chain segments — from procurement to manufacturing to shipping. With an all-rounded assessment carried out, define the supply chain digitization strategy, and make sure it reflects the findings. It makes sense to start with digitizing one segment of the supply chain that shows the highest value-creation potential to drive ROI faster. And once the base solution is rolled out, you could evolve further, both vertically, expanding the list of available features, and horizontally, extending the capabilities of AI to other supply chain segments. Step 2. Look for an optimal vendor to bring your solution to life Due to the complexity and the multifaceted nature of the supply chains, all of your expectations could hardly be met by a single vendor. So, don’t be afraid to examine what the supply chain technology market has to offer and integrate the optimum offerings into a solution that addresses your specific needs. Another piece of advice is going for a vendor-agnostic integrator, so you prevent technology and solution lock-in. Step 3. Oversee the development and integration of the solution According to McKinsey, only 15% of businesses involved in supply chain management report feeling like their objectives are in line with those of their vendors. To prevent that and ensure a smooth roll-out, map the development process to the initial supply chain digitization strategy and keep in mind the key value you intend to tap into. Prioritizing the value-creation opportunities and dividing the development process into increments according to the set priorities might help navigate end-to-end AI implementation. Step 4. Ensure the solution’s smooth adoption and scale the implemented capabilities Powering a supply chain with AI is a complex endeavor that is more than just rolling out the technology. Digitizing a supply chain also requires comprehensive change management and reskilling. So, before you jump on the AI bandwagon, we recommend laying out a change management plan to help you handle the skills gap and the cultural shift. Start with explaining the value of AI to the employees and educate them on how to embrace the new ways of working. On a final note Over the past years, artificial intelligence has become a vital element of a resilient supply chain. AI-based supply chain management tools are helping organizations speed up the flow of materials and finished products, cut down operational costs, and effectively navigate through changes. If you are looking to tap into the transformative power of AI and digitize your supply chain for better visibility, resilience, and responsiveness, . Their AI experts will answer your questions and help navigate the transformation process with little to no risks. drop ITRex a line

AI is a Cornerstone of a Resilient supply Chain. Here’s Proof

Stories, News & Mentions about NOQ

Categories

Trending Topics

Stories, News & Mentions about NOQ

Noq’s Stories on HackerNoon

Categories

Trending Topics