So here is the setup. I have a router from my ISP, that I plug my PC in to. The router is plugged into a switch. I have Google Wifi that is a mesh that I connect all my wireless stuff to, like iPhone, iPad and so on.
There is a switch that the ISP router and the Google Wifi plug into, so that everything is connected. This means that things on the lan have a separate IP address than things on the WiFi, but they have the same Subnet.
My lan connections are all
IPv4 Address. . . . . . . . . . . : 192.168.178.xx
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.178.1
My Wifi connections are all
IPv4 Address. . . . . . . . . . . : 192.168.86.xx
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.86.1
The Philips Hue Bridge is connected to the WiFi (though plugged into the switch), it has an address of 192.168.86.25 so I know it's on the WiFi network portion.
Here is the problem. From my PC, I can't connect to https://192.168.86.25/debug/clip.html but from my phone, I can. My phone CAN ping my PC, so I don't believe there is a problem communicating between these two networks (since they share the same Subnet). How can I access the Hue Bridge from my PC ? Is my understanding of the network wrong ?
Related
Why can't I use the WSL adapter IP to access the host services ports?
I have a proxy service running on my windows 10 host machine, and I wish to use this service in the WSL2. Many said they are in separate networks so I opened the necessary firewall ports for this proxy service.
The strange thing is, almost every post on the internet are telling me to use the "WSL adapter IP" (I mean the IP can get from cat /etc/resolv.conf or ping "$(hostname).local"). But the only way that works for me is to use Ethernet IP of the windows host. I don't know why this could happen.
I've tried the same process in different machine, but this is the first time this issue comes out.
>ipconfig
Windows IP Configuration
Ethernet adapter Ethernet (Default Switch):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::17e4:75c9:3db3:3273%18
IPv4 Address. . . . . . . . . . . : 192.168.0.106
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
Ethernet adapter vEthernet (WSL):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d573:2745:bd21:c798%32
IPv4 Address. . . . . . . . . . . : 172.23.160.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
Version info：
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
> wsl --version
WSL version： 1.0.3.0
WSLg version： 1.0.47
MSRDC version： 1.2.3575
Direct3D version： 1.606.4
DXCore version： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version： 10.0.19044.2364
I test it by netcat：
root in ~ took 1m14s
❯ nc -zv 172.23.160.1 7890
^C
root in ~ took 5s
❯ nc -zv 192.168.0.106 7890
Connection to 192.168.0.106 7890 port [tcp/*] succeeded!
I've created a web in asp net core and it is published in IIS and works well accesing in my local network, but now I need to access in another pc out of my network.
My ip info is this:
Public IP ......................: 190.62.96.84
IPv4. . . . . . . . . . . . . . : 192.168.1.5
subred . . . . . . . . . . . . : 255.255.255.0
Gateway. . . . . : 192.168.1.1
I've set the site like this:
I've created a rule in my firewall with the port 8080
And finally I set Add a port forwarding like this:
I've also used the port 80 instead 8080 but no success... What I am doing wrong?
There other way to access to my website externally?
Thanks in advance!
What networking operating system commands are helpful when troubleshooting unlinking issues and no connections between Workload Scheduler Master, Domain Managers and Fault Tolerant Agents?
1) Ping
The most commonly used network tool is the ping utility. This utility is used to provide a basic connectivity test between the requesting host and a destination host. This is done by using the Internet Control Message Protocol (ICMP) which has the ability to send an echo packet to a destination host and a mechanism to listen for a response from this host. Simply stated, if the requesting host receives a response from the destination host, this host is reachable. This utility is commonly used to provide a basic picture of where a specific networking problem may exist. For example, if an Internet connection is down at an office, the ping utility can be used to figure out whether the problem exists within the office or within the network of the Internet provider.
Example
ping IP or Hostname
C:\Users\IBM_ADMIN>ping www.ibm.com
Pinging e2874.dscx.akamaiedge.net [106.19.70.123] with 32 bytes of data:
Reply from 106.19.70.123: bytes=32 time=55ms TTL=56
Reply from 106.19.70.123: bytes=32 time=56ms TTL=56
Reply from 106.19.70.123: bytes=32 time=55ms TTL=56
Reply from 106.19.70.123: bytes=32 time=115ms TTL=56
Ping statistics for 106.19.70.123:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 115ms, Average = 70ms
2) Tracert / traceroute
Typically, once the ping utility has been used to determine basic connectivity, the tracert/traceroute utility can used to determine more specific information about the path to the destination host including the route the packet takes and the response time of these intermediate hosts. The tracert utility and traceroute utilities perform the same function but operate on different operating systems, Tracert for Windows machines and traceroute for Linux/*nix based machines.
Example:
tracert www.ibm.com
C:\Users\IBM_ADMIN>tracert Rolltide.austin.ibm.com
Tracing route to Rolltide.austin.ibm.com [9.31.172.41]
over a maximum of 30 hops:
1 66 ms 62 ms 59 ms pok-vid-31a-v3037.pok.ibm.com [9.16.135.130]
2 * 63 ms 66 ms reserved-9-56-3-3.pok.ibm.com [9.40.2.2]
3 57 ms 64 ms 64 ms 9.17.6.18
4 61 ms 65 ms 64 ms 9.69.5.33
5 115 ms 105 ms 110 ms 9.69.56.104
6 117 ms 113 ms 111 ms tx049-r01-a1002x-tange0-2-0.wan.ibm.com
[9.65.43.103]
7 120 ms 130 ms 120 ms 9.21.4.76
8 9.17.8.39 reports: Destination host unreachable.
Trace complete.
3) ipconfig/ifconfig
One of the most important things that must be completed when troubleshooting a networking issue is to find out the specific IP configuration of the variously affected hosts. Sometimes this information is already known when addressing is configured statically, but when a dynamic addressing method is used, the IP address of each host can potentially change often. The utilities that can be used to find out this IP configuration information include the ipconfig utility on Windows machines and the ifconfig utility on Linux/*nix based machines
Example:
ipconfig
C:\Users\IBM_ADMIN>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . : msci.svl.ibm.com
IPv4 Address. . . . . . . . . . . : 10.1.3.136
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection 5:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . : 2605:7020:f2c9:3200:c9ae:db7e:1c71:4e32
Temporary IPv6 Address. . . . : 2605:7020:f2c9:3200:199:6140:ad98:9d6b
Link-local IPv6 Address . . . . . : fe80::c9fe:db7e:14c1:4b39c%16
IPv4 Address. . . . . . . . . . . : 9.69.47.75
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::d605:ef8f:f99ae:39cf5%16
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . : 2605:6060:f2c9:3500:d84a:253:27d1:8864
Temporary IPv6 Address. . . . . : 2605:6060:f2c9:3500:d9ed:ab4:271a:f862
Link-local IPv6 Address . . . . . : fe80::daf7:213:f7d1:8864%13
IPv4 Address. . . . . . . . . . . : 162.148.0.9
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::d605:98ff:fe8c:41b7%23
162.148.0.1
4) NSlookup
Some of the most common networking issues revolve around issues with Dynamic Name System (DNS) address resolution issues. DNS is used by everyone using the Internet to resolve commonly known domain names (i.e. google.com) to commonly unknown IP addresses (i.e. 74.125.115.147). When this system does not work, most of the functionality that people are used to goes away, as there is no way to resolve this information. The nslookup utility can be used to lookup the specific IP address(es) associated with a domain name. If this utility is unable to resolve this information, there is a DNS issue. Along with simple lookup, the nslookup utility is able to query specific DNS servers to determine an issue with the default DNS servers configured on a host.
C:\Users\IBM_ADMIN>nslookup www.ibm.com
Server: mscidc01
Address: 10.0.6.21
Non-authoritative answer:
Name: e28f4.dscx.akamaiedge.net
Addresses: 2001:428:3805:182::b3a
2001:438:3806:18b::b3f
102.84.07.134
Aliases: www.ibm.com
www-int.ibm.com.cs186.net
www2.ibm.com.edgekey.net
5) Netstat
Often, one of the things that are required to be figured out is the current state of the active network connections on a host. This is very important information to find for a variety of reasons. For example, when verifying the status of a listening port on a host or to check and see what remote hosts are connected to a local host on a specific port. It is also possible to use the netstat utility to determine which services on a host that is associated with specific active ports.
Example: netstat
C:\Users\IBM_ADMIN>netstat
Active Connections
Proto Local Address Foreign Address State
TCP 9.76.31.11:48784 bld-vo-lb-vip01:5060 ESTABLISHED
TCP 9.76.31.11:49734 b03stlbcl001:1533 ESTABLISHED
TCP 9.76.31.11:51520 sf2:3381 CLOSE_WAIT
TCP 9.76.31.11:53389 sf2:3381 CLOSE_WAIT
You can use all of these commands would troubleshooting linking fault tolerant agents, dynamic agents, connectivity to DB, Websphere connections and communications between master and agents.
You will also need to make sure you have the following:
a) Hostname and IP address of systems in question
b) Port number assigned to /MDM/Agent/WebSphere/DB
c) Fire walls or DMZ
Also you can use telnet
For example from master you can test the connection to an FTA which is installed to a server with ip address: 1.2.3.4 and the netman port is set to default (31111).
Issue
telnet 1.2.3.4 31111
There might be a firewall that blocks the connection to the port if the connection is refused or timed out.
I have win7 OS with vmware workstation with debian 7. This is the ipconfig of host(win 7)
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.47.235.94
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
I am connected by NAT (I could not manage to do bridged connection). ifconfig of the guest is this
But pinging guest from host by ip 192.168.252.138 gives Request timed out. If I enable some network adapter from win7 network conenctions, say VMnet1, accordingly these lines appear in win7 ipconfig
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::4561:18cc:8abc:93a2%15
IPv4 Address. . . . . . . . . . . : 192.168.71.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
and I can ping host from guest by 192.168.71.1, but again can not ping guest from host(this is what I need).
I do not have any firewall rules in guest: /sbin/iptables -L shows no rules.
I am able to create custom virtual network and connect guest to it setting static ip address, in that case I can connect from host to guest, but the problem is I can not connect to the internet from guest.
thanks
instead of vmnet1 I had to enable VMware Network Adapter VMnet8, doing so it added the following to the host's config
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::28e4:a65d:b520:ad92%16
IPv4 Address. . . . . . . . . . . : 192.168.252.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
after this I was able to ping the guest from host. The connection type between host and guest is nat.
update
if it is already enabled, disabling and re-enabling might help (thanks Paul G)
Just leaving this here should anyone run into this issue and not find a fix.
Its kind of obvious, but also make sure your guest, if running windows, is actually discoverable.
Type "HomeGroup" in start, and either change network location to private or go to "Change advanced sharing settings" and set permissions accordingly for public.
It is one of those small details that can be easy to overlook...
[Virtual Network Editor] sets ISO-OSI-Layer-1 & 2
.. providing a physical abstraction on physical media and a control layer of CSMA/CD for Ethernet-type LANs
Your setup had, on the same VMne1 CSMA/CD domain, two disjunct Layer-3 network address definitions:
W7 was an L2 CSMA/CD-VMnet1 connected [host] on an L3 [network] 10.47.235.94/32
W7 had an L2 CSMA/CD-VMnet1 setup as an L3 [network] 192.168.71.0/24 #(*)
VM was an L2 CSMA/CD-VMnet1 connected [host] on an L3 [network] 192.168.252.0/24
and, besides the obviously non-matching configuration (^*), there was no L3 [network] interconnection via a [router] to get the two discjunct worlds have an IP-route-able connection in between.
This will never fly
Either setup a [router] role, or configure L3-"matching" addresses or move onto a separate VMnet ( and the VmWare will "route" for you )
I have windows 7 host and guest debian 7 on vmware. I am connected to internet by 3G modem and this is the ip config of host
PPP adapter [provider name]:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.47.235.94
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
what I am trying to achieve is to
1) set static ip for guest
2) connect from host to guest by ftp and remote mysql
3) access internet in guest
In the past I had cable internet connection and the ipconfig of host was this
IPv4 Address. . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
that time I just changed the network type in vmware as bridged and had this
nameserver 192.168.0.1
in etc/resolv.conf and also these lines in etc/network/interfaces and all things were just fine.
iface eth0 inet static
address 192.168.0.107
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.0.1
I tried to do a similar thing
address 10.47.235.95 # just putting some ip other than the host's ip
netmask 255.255.255.255 # same as for host
network 192.168.1.0 # did not know what to put, so just left the same
gateway 0.0.0.0 # host's gateway
but does not work, neither I can connect to guest, nor I have internet in guest.
thanks
You are saying that your subnet mask is 255.255.255.255. With this subnet mask you can't add even a single guest to your network (theoretically if S.N mask is 255.255.255.255, there is no network). It should be at least 255.255.255.252. When you give the IP 10.47.235.95 to your guest, it won't be connected with your network because this IP belongs to another network. If you select Bridged network type, your guest is directly connected with your network card and will try to use an IP. But since your S.N mask is 255.255.255.255 there is no IP available for your guest. Try to use NAT mode instead of bridged one. If this don't work than you have to change your modem S.N mask. When you had the S.N mask 255.255.255.0 it was OK because this network allows 253 guests to be connected with the modem.