Problem:
I would like to configure my A6 AC1200 Wireless MU-MIMO Router to connect to the phone’s hotspot and I think the proxy setting is causing an issue that I don’t know how to resolve.
Router:
Hardware Version: V6
Firmware Version: V2 - 210226
Background:
I’m temporally in a rural area where only dial-up access is available. So, I’m using an app on my smartphone called NetShare which works by connecting my computer to the smartphone but it requires me to set a proxy in Windows 10 to 192.168.49.1 on port 8282, but MS Outlook will not connect to a server and I would like to share the connection with others. My current download speed is 138 MBPS when connected to the mobile network with the app on 4G.
I was able to get the router to work on the mobile-phone provider’s hotspot but they throttle it. I think the proxy settings are the main differences between the app and provider's hotspot.
Data from ipconf while connect to the smartphone app:
IPv4 Address. . . . . . . . . . . : 192.168.49.251(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.49.1
DHCP Server . . . . . . . . . . . : 192.168.49.1
DNS Servers . . . . . . . . . . . : 192.168.49.1
Data from netstat while connect to the smartphone app:
TCP 192.168.49.251:55282 192.168.49.1:8282 ESTABLISHED
TCP 192.168.49.251:55341 192.168.49.1:8282 TIME_WAIT
Attempted Router Settings:
- Advanced / Network / Lan/ IP Address
192.168.49.1
- System tools / System Parameters
Select Enable 5GHZ
Select Survey
Select the correct wireless network and enter the password
- Status / Wireless / 5GHZ
Make sure it shows "Run"
- Network / DHCP Server
Select Disable (I was not sure about this but I think the app will allow multiple users so it must give ip’s)
- Wireless / Wireless Settings
Select Smart Connect at the top
- Network Name (SSID): <Enter a name>
Password: <enter a password>
Network / IPTV/VLAN (Enable the ports on the back of the router)
Enable IPTV/VLAN
Mode: Bridge
Lan 1 to 4: Select Internet.
I also attempted to connect the computer to the phone's hotspot and then share the computer's connection with the router but I also could not get that to work.
How can I share the phone’s Internet connection with the router?
Thanks!
Related
TL;DR
It seems I'm constantly running into networking problems when using WSL2 and Docker Desktop for Windows.
Normally, I can access a port started from a WSL2 instance ("distribution" in WSL2-speak) from inside Docker containers, by finding the IP address of the WSL2 instance, and referencing to that IP address from inside the containers. But today that doesn't work for some reason. I'm getting used to rebooting when I run into WSL2+DockerDesktop problems, but now I'd like to finally understand what is actually wrong.
I'm pretty sure that when I reboot in a moment, all will be fine and dandy.
Do you have an idea on how to debug something this?
I also have a corporate Forticlient VPN that could be messing this up. But I have no choice in that matter... ;-(
Details
I find the IP with:
WSL2:» ip -br a
lo UNKNOWN 127.0.0.1/8 ::1/128
bond0 DOWN
dummy0 DOWN
sit0#NONE DOWN
eth0 UP 172.26.183.209/20 fe80::215:5dff:fef9:cc5c/64
So the WSL2 machine's IP address is 172.26.183.209.
So now that I have a web server listening on port 8080 in a process my WSL2, it can be accessed with http://172.26.183.209:8080, as confirmed by nmap and curl from WSL2:
WSL2#~» nmap -Pn -p 8080 172.26.183.209
Starting Nmap 7.80 ( https://nmap.org ) at 2020-12-23 16:15 CET
Nmap scan report for ubuntu-wsl2 (172.26.183.209)
Host is up (0.000045s latency).
PORT STATE SERVICE
8080/tcp open http-proxy
Nmap done: 1 IP address (1 host up) scanned in 0.02 seconds
WSL2#~» curl http://172.26.183.209:8080 > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
From inside a container, however:
[root#0467b7ef17e7 /]# nmap -Pn -p 8080 172.26.183.209
Starting Nmap 7.70 ( https://nmap.org ) at 2020-12-23 15:12 UTC
Nmap done: 1 IP address (0 hosts up) scanned in 0.43 seconds
[root#0467b7ef17e7 /]# curl http://172.26.183.209:8080
curl: (7) Failed to connect to 172.26.183.209 port 8080: No route to host
It also works from inside the docker-desktop WSL2 container:
WSL2#~» wsl.exe -d docker-desktop wget http://172.26.183.209:8080
Connecting to 172.26.183.209:8080 (172.26.183.209:8080)
Connecting to host.docker.internal:8180 (192.168.0.202:8180)
index.html 100% |********************************| 7308 0:00:00 ETA
Just not from inside the containers. Until I reboot. AAAARRRRRHHHHHHHHHHHHHHHH :-)
One hint - something that doesn't make sense to me - is this from inside a container:
[root#0467b7ef17e7 /]# ping 172.26.183.209
PING 172.26.183.209 (172.26.183.209) 56(84) bytes of data.
From 172.26.0.2 icmp_seq=1 Destination Host Unreachable
From 172.26.0.2 icmp_seq=2 Destination Host Unreachable
From 172.26.0.2 icmp_seq=3 Destination Host Unreachable
^C
--- 172.26.183.209 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 202ms
pipe 4
What is 172.26.0.2? Hmm...
Networking setup:
(I've modified Ethernet 3's IP address since it's in the corporate network)
WSL2#~» ip -br a
lo UNKNOWN 127.0.0.1/8 ::1/128
bond0 DOWN
dummy0 DOWN
sit0#NONE DOWN
eth0 UP 172.26.183.209/20 fe80::215:5dff:fef9:cc5c/64
WSL2#~» ipconfig.exe
Windows IP Configuration
Ethernet adapter Ethernet 3:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::405f:b7d2:70b4:b405%19
IPv4 Address. . . . . . . . . . . : 10.14.11.17
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.14.11.18
Ethernet adapter Ethernet 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::7cd1:5641:ac65:7004%15
IPv4 Address. . . . . . . . . . . : 192.168.0.202
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::f06d:9785:cff5:2ad0%6
IPv4 Address. . . . . . . . . . . : 192.168.225.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Wireless LAN adapter Wi-Fi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Local Area Connection* 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::c507:3c2b:62d:7270%39
IPv4 Address. . . . . . . . . . . : 172.26.176.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
WSL2#~» route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 172.26.176.1 0.0.0.0 UG 0 0 0 eth0
172.26.176.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0
I had a similar issue where the IP address for WSL2 conflicted with the 172.17.0.0/16 address space which Docker uses internally. In my case, in WSL2:
$ hostname -I
172.17.112.35
The fix was to change the address space Docker uses to a different one which also doesn't conflict with my local network. In the settings in Docker Desktop, set "bip": "192.168.200.1/24" on the Docker Engine configuration page.
Credit: https://www.beyondjava.net/docker-wsl-network
Restarting your PC or WSL "fixes" this issue temporarily because the IP assigned to WSL happens to not conflict with addresses used by Docker.
Have you tried just restarting the container and not the whole machine? It sounds like it's the container losing track of its network configuration. A lot of things with containers are written at startup and never updated or not consistently updated.
I'm still looking for a solution, but I found a quicker workaround: just restart WSL2. From a cmd window, enter:
wsl --shutdown
Docker will complain about having stopped unexpectedly, and then will give you another message when you restart it, but that's not harmful.
I have an environment which consist of 3 application, 2 running in Windows and 1 running in Debian OS. For testing purpose, I already build the environment in only 1 PC (running Windows 10) with VirtualBox VM (for running Debian OS).
Below is detail network configuration:
Host PC (using 2 VirtualBox Host Only Adapter):
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::ec0c:3c16:4f85:1a5e%12
IPv4 Address. . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.14
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.21
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.24
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.25
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.26
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.31
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.32
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.34
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.1.123
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VirtualBox Host-Only Network #2:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5d7:813f:a9a:865d%16
IPv4 Address. . . . . . . . . . . : 192.168.1.122
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . :
VirtualBox VM network configuration:
/etc/network/interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet static
address 192.168.1.120
netmask 255.255.255.0
gateway 192.168.1.1
auto eth2
allow-hotplug eth2
iface eth2 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
auto eth2:0
iface eth2:0 inet static
address 192.168.1.20
netmask 255.255.255.0
auto eth2:1
iface eth2:1 inet static
address 192.168.1.30
netmask 255.255.255.0
Ifconfig output:
eth0 Link encap:Ethernet HWaddr 08:00:27:a8:08:8b
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
...
eth1 Link encap:Ethernet HWaddr 08:00:27:41:27:73
inet addr:192.168.1.120 Bcast:192.168.1.255 Mask:255.255.255.0
...
eth2 Link encap:Ethernet HWaddr 08:00:27:0d:6b:54
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
...
eth2:0 Link encap:Ethernet HWaddr 08:00:27:0d:6b:54
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
...
eth2:1 Link encap:Ethernet HWaddr 08:00:27:0d:6b:54
inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0
...
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
...
Below is some flow of network interaction in current environment:
App1 run in VM and create multiple socket server:
-Listening on IP 192.168.1.10, 192.168.1.20, 192.168.1.30 port 1448
-Listening on IP 192.168.1.120 port 1449
App2 run in Host machine and create multiple connection:
-create socket server in 192.168.1.123 port 1448
-connect to socket server in VM: 192.168.1.10 port 1448 (using binding ip = 192.168.1.11)
-connect to socket server in VM: 192.168.1.20 port 1448 (using binding ip=192.168.1.12)
...
-connect to socket server in VM: 192.168.1.120 port 1449
App3 run in Host machine and create multiple connection:
-connect to socket server 192.168.1.123 port 1448 (App2)
-connect to socket server 192.168.1.120 port 1449 (App1)
The environment is working OK now, but after read about Docker, I plan to replace VirtualBox VM with using Docker for reduce memory usage.
I successed build up an Debian image, setup library, etc...
However, I don't know how to setup network in Docker for having similar function with above VirtualBox VM configuration. Some dificult points:
Can we create network interface similar like 'Ethernet adapter VirtualBox Host-Only Network' using Docker?
In case we cannot create such that network interface, it is OK to remain these 2 VirtualBox Host Only Adapter in environment. But i'm not sure how to "connect" these network interface into Docker container?
It seem impossible to assign static IP address for docker container, is this correct?
(This doesn't help: Assign static IP to Docker container)
It seem also impossible to assign multiple IP address to docker container, is it correct?
So it seem very dificult to build up above environment using Docker.
If anyone have solution that still able to build the environment using Docker, please help point out some direction.
Thank you very much!
The first three questions you asked are solved with macvlan network. You'll have containers directly attached to your network, just like VM's. Here's an example:
version: "2.1"
services:
nginx1:
image: nginx
networks:
network_1:
ipv4_address: 10.1.1.115
nginx2:
image: nginx
networks:
network_1:
ipv4_address: 10.1.1.116
networks:
network_1:
driver: macvlan
driver_opts:
parent: enp52s0 # Your network interface name
ipam:
driver: default
config:
- subnet: 10.1.1.0/24
gateway: 10.1.1.1
In this example I declared a macvlan network named network_1, which attached to the enp52s0 network interface. The two nginx containers use that network and each advertises its own static IP.
Now if you want to assign more than one IP per container things begin to get messy. To assign an additional address you need an additional network, with its own IP range, its own parent network interface, and its own gateway. That is literally another network. Or you can think of some hack, maybe using a proxy container that'll listen on another IP and forward traffic into desired container but it's kinda 'meh'. I'd say that VM overhead does not worth all that trouble unless you are open to redesign connectivity of your application.
In the docker documentation there are articles about "user defined" network bridges, the link can be found here. I think you'll have to create those according to your network architecture and once they are made then you can specify when creating a docker container that it should use one of the user-defined bridges that you created.
As you are using multiple applications and would like to put this in multiple docker containers I would also suggest to look into "docker-compose". With this you can create a YML manifest that will spin up multiple docker containers with their defined configs, networks, specific ports, ... all at once so you can launch/shutdown the whole environment at once.
An example and even more information on ip addresses of docker images can be found in this article.
Have created an dotnet core application and when run the command:
docker-compose up
everything goes well but I don't understand what does the below line mean:
Now listening on: http://[::]:80
Dockerfile content is:
FROM microsoft/aspnetcore:2.0
ARG source
WORKDIR /app
EXPOSE 80
COPY ${source:-obj/Docker/publish} .
ENTRYPOINT ["dotnet", "SampleCoreApp.dll"]
docker-compose file is:
version: '3'
services:
samplecoreapp:
image: samplecoreapp
build:
context: ./SampleCoreApp
dockerfile: Dockerfile
Why is that I'm not seeing the IP address?
If i have a 3 VMs and if I want to run this application on VM2 then how can I deploy this docker container to VM2?
Now listening on: http://[::]:80
means: your application is telling you that it is listening on TCP port 80 on all IPv6 addresses it owns.
[::] is the short-hand notation for the IPv6 address 0000:0000:0000:0000:0000:0000:0000:0000 within an URL. Note that :: is not a valid IPv6 address, but often is used as an alias for "all my IPv6 addresses".
Similarly, a web server that listens on TCP port 80 of all its IPv4 addresses usually reports that it is listening on http://0.0.0.0:80. In your case, it seems to be expecting IPv6 traffic instead. However, many applications are dual stack and listen to both, IPv4 and IPv6.
I recently tried to portforward port 80 on my local IP, but as the tutorial said, it should be open on my external IP, which it's not. But it is open on my local ip thought.
I have portforwarded port 80, range 80 UDP and TCP on my local IP: 192.168.1.170
This is the tutorial i followed: https://www.youtube.com/watch?v=RZTYqTGqtjI
I portforwarded my IP in the router settings.
https://image.ibb.co/hGW4fm/Sk_rmbild_345.png
https://image.ibb.co/exWFmR/Sk_rmbild_344.png
IF THE suggested METHOD DOESN'T WORK FOR YOU , DO THIS :-
GOTO -> SECURITY TAB -> REMOTE MANAGEMENT
Enable the Remote Management (or enter 255.255.255.255 in the field) .
This will enable the you to access your LAN from WAN.
For the record :-
Internal Port is the PORT on which the device in your LAN is serving .
External Port is the port which the user enters in the browser . exp :- 127.184.184.19:8080 .
Here 8080 is the external port . And if a device in your LAN runs a http web server at port 80 , then the internal port would be 22.
If the Above methods don't work , then your ISP might be using Carrier NAT which means you would have a different PUBLIC and WAP ip address .
In this case , you should use the WAN ip address shown in your router configuration page to access your LAN from internet. s
Kindly Try to open same URL from different Internet Connection other than LAN
I am new to #Solace. I am trying to configure Solace VMR (evaluation version) on my machine (Windows 10).
I have a problem while configuring the network, I am unable to configure the bridge though I configure host only to start my VMR but unable to connect it from the machine.
Any help to start the configuration would be great help.
This is likely to be a problem with the setup of the host only network.
Here are some steps to help identify/solve.
Identify the IP address of the VMR.
On boot, the VMR should display it's IP address on the hyper-visor's console. In the example below, the IP address that was allocated to the VMR from the host only network is 192.168.17.128.
Execute ipconfig on the windows 10 host to verify whether or not there is a IP address configured for the host only network interface.
Here's an example of VirtualBox's interface for host only networks.
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::e9e4:351e:c03b:e417%21
IPv4 Address. . . . . . . . . . . : 192.168.56.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Here's an example of VMWare's interface for host only networks. It is usually named VMnet1.
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a0ea:e4ce:d2e9:3c4%24
IPv4 Address. . . . . . . . . . . : 192.168.17.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ensure that the interface(s) for host only adapters have valid IP addresses assigned to them.
Execute a tracert on the windows 10 host to find out the network path to the VMR.
The tracert results should look similar to the following, and is expected to take only 1 hop.
tracert 192.168.17.128
Tracing route to 192.168.17.128 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.17.128
Trace complete.