Jeff Beckman <[email protected]> writes: > I feel like I might not get much sleep this week, this is driving me nuts. > I installed linux on a VM on my desktop (the one that has working MQTT > Explorer) and it worked. The default (oracle virtualbox) was to just > attach to my NAT, so it got an IP of 10.0.2.15 (which my desktop passes > through to 192.168.1.185?). Changing it to a bridge adapter, it picked up > a DHCP address of 192.168.1.218, and then it did not work.
Unless you really know what you are doing, it seems unlikely that having 10.0.2.15 and 192.168.1.85 on the same LAN is sensible. Generally each Ethernet, real or virtual, should have one prefix and at most one DHCP server. Once there is address confusion, i suspect routing confusion. My advice is to first completely straighten out your home LANs addressing plan. > Here's my full setup: Router is a stand-alone box running pfsense. I have > a server that runs freebsd doing virtualization (static, 192.168.1.30). > Home Assistant is a VM (static, 192.168.1.35). Weewx is a raspberry pi 2 > (static, 192.168.1.17). Desktop windows machine (DHCP, 192.168.1.185). > > I have another unrelated VM running on that free bsd machine for a > minecraft server (static, 192.168.1.36). Remoting in there gives the same > problems trying to publish a message. This machine's network setup is > almost identical to the Home Assistant machine and it is able to accept > connections on its minecraft port, 1935 or something. So where is 10/8? That's a bug, IMHO, and perhaps related, perhaps not. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/rmi5z3j9sjx.fsf%40s1.lexort.com.
signature.asc
Description: PGP signature
