You are here

Powerbeam just gets 169... address.

2 posts / 0 new
Last post
k0tan
k0tan's picture
Powerbeam just gets 169... address.

Just this week stopped getting this powerbeam ui to come up. Worked fine for years. Win10 firefox. Now gets the autoconfig 169... addy but several reboots of node don't help. When Mesh.local is working the attached pdf shows what ipconfig should have. Not getting past the autoconfig ip. Grrrrrrrr. Help?


Ethernet adapter Ethernet 4:

   Connection-specific DNS Suffix  . : local.mesh
   Description . . . . . . . . . . . : ASIX USB to Gigabit Ethernet Family Adapter #2
   Physical Address. . . . . . . . . : 00-24-9B-2D-54-CE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e2a9:a82a:d7ab:fdec%30(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.237.198(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 1258300571
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-94-F3-3E-00-23-15-0B-54-B0
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
   Connection-specific DNS Suffix Search List :
                                       local.mesh
File Attachment: 
K7EOK
I don't understand.  Your
I don't understand.  Your post gives a IPv4 address 169.x.x.x but your attachment shows a mesh address.  Which is it?

If you're connecting the powerbeam to an existing network, which network has the router that controlls DHCP?  If you're troubleshooting the powerbeam should be directly connected to your computer and the computer not on another network (at least not on the same network card).

Ed
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer