Can No Longer Login to TEG Home IP

[jboy210]

I have a Ubiquiti WiFi network and I gave up and connected a nearby Ethernet cable.

How to route ethernet along the outside wall to gateway

I have a spare ethernet cable close to the Tesla Gateway, but unsure what is the best way to connect to it. The gateway is outdoors, so I am worried about how to weather proof the entire thing for rain. Would it be okay to just punch out a hole on the bottom of the gateway and run the ethernet...

teslamotorsclub.com

Also, I thought the AT&T 3G cellular was supposed to stop working at the end of February 2022. My Gateway still says Cellular is connected.

Agree. Hardwire is the way to go. And for me, if my Ethernet-based network goes away the access point a few feet above the TEG would also be dead.

I believe you told me to dump Wifi, and I am glad I did.

 

[BGbreeder]

Informal poll here:
I'm curious how many of you have static(reserved) network addresses for your gateways on your private network(s). I would also be curious how many of you have your gateways on an isolated subnet (Tesla only / IOT / Guest / ...).

 

[jrweiss98020]

I reserved both the WiFi and Ethernet addresses. Still on my main network.

 

[schettj]

Informal poll here:
I'm curious how many of you have static(reserved) network addresses for your gateways on your private network(s). I would also be curious how many of you have your gateways on an isolated subnet (Tesla only / IOT / Guest / ...).

Reserved on wifi, not isolated, no issues with connectivity

 

[taphil]

Static, not isolated, on wifi AIMesh system, never had a problem.

 

[crackers8199]

we just had our powerwall install finished today, and i'm seeing something similar to this...but strangely enough, only on some computers on the network. none of my macs can get to the TEG, but home assistant and my cell phone can.

DHCP, on its own SSID (but i haven't isolated it yet)

 

[skepticcyclist]

Interesting...
Just out of curiosity I tried to see if I can login today. It worked with no issues. I haven't changed a thing since I was having issues

 

[ptdusn]

Interesting...
Just out of curiosity I tried to see if I can login today. It worked with no issues. I haven't changed a thing since I was having issues

Did you get the new update? Mine just updated yesterday.

 

[crackers8199]

Did you get the new update? Mine just updated yesterday.

mine was just installed yesterday (or at least they just finished yesterday), so i would imagine it has the latest updates. what version are you on?

 

[crackers8199]

Interesting...
Just out of curiosity I tried to see if I can login today. It worked with no issues. I haven't changed a thing since I was having issues

i can't even get the page to load, let alone try to log in...

 

[ptdusn]

mine was just installed yesterday (or at least they just finished yesterday), so i would imagine it has the latest updates. what version are you on?

22.1.1 b0ec2432

 

[skepticcyclist]

Did you get the new update? Mine just updated yesterday.

No. Still on 22.1.1

 

[crackers8199]

I'm on 22.1.2.

 

[crackers8199]

is there a fix for this yet? I still can't log in on the home network side, and every time I do updates on my homelab server and reboot I need to go back into the TEG wifi network, and tell it to connect to the same network again to get my home assistant install to be able to see it again...

 

[skepticcyclist]

I am on 22.9.1 now and I am still able to log in

 

[crackers8199]

I am on 22.9.1 now and I am still able to log in

i'm on 22.9.1 now and still UNABLE to log in.

 

[Billme]

What is the home IP network that you are using? I could not reach my gateway because my home network was 10.1.1.0, and there appears to be no way to change the netmask from the default 255.255.0.0 to the one I’m using. I ended up creating a static route to the 192.168.91.0 network using the DCHP address of my gateway, and this worked around the problem. This probably isn’t your problem, but it might be useful for others.

 

[crackers8199]

What is the home IP network that you are using? I could not reach my gateway because my home network was 10.1.1.0, and there appears to be no way to change the netmask from the default 255.255.0.0 to the one I’m using. I ended up creating a static route to the 192.168.91.0 network using the DCHP address of my gateway, and this worked around the problem. This probably isn’t your problem, but it might be useful for others.

192.168.88.0/24

edit: that being said, you are awesome. decided to give this a shot, and it worked for me too.

in case anyone has a pfsense router and is curious how to do this: the TEG on my home network got DHCP 192.168.88.152. i had to add that as a gateway, then a static route to 192.168.91.0/24 via that gateway...

boom. i can now access the TEG at 192.168.91.1 (AND 192.168.88.152 as well, for that matter).

thank you, so much. i did order a wireless bridge and i'm still probably going to hardwire it via ethernet at some point, but this'll work for now.

 

[crackers8199]

check that, accessing via IP on my network is hit or miss still...but via 192.168.91.1 has worked consistently. that's good enough for now until i get it connected via ethernet.

 

[jboy210]

check that, accessing via IP on my network is hit or miss still...but via 192.168.91.1 has worked consistently. that's good enough for now until i get it connected via ethernet.

Ethernet only is the way to go. 2-4 months since turning off wifi and have not had any issues connection. With Wifi enabled and ethernet connected had issues ever 2-3 days.