What happened to Teg 1.45.1
fkhera opened this issue · 7 comments
fkhera commented
Hello:
It seems as of update 1.45 TEG is not reachable on REST, did this happen to you guys?
spoonwzd commented
Nooo don't tell me that :(
I'm still on 1.44.2
BJReplay commented
I'd seen reports of that over at TMC. Commentary suggested that the
gateway picked up a new IP where it was allocated a reserved DHCP lease,
and that it was suspected it had picked up a new MAC address. Might be
worth checking your router to see if it has picked up a new IP.
1.45.1 is out, and reportedly fixed that problem.
Don't quote if if I haven't got that entirely right - quoting from memory.
So if you can find your gateway, perhaps try getting it to check for an
update.
I skipped from 1.43.1 to 1.45.1 without a problem.
…On Fri, 20 Mar 2020 at 06:48, spoonwzd ***@***.***> wrote:
Nooo don't tell me that :(
I'm still on 1.44.2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJB3YI4E6YS7IN5TYFD3SS3RIJZILANCNFSM4LPOI43A>
.
fkhera commented
I think its actually my IP changed.
On Thu, Mar 19, 2020 at 3:21 PM Bernard Sheppard <notifications@github.com>
wrote:
… I'd seen reports of that over at TMC. Commentary suggested that the
gateway picked up a new IP where it was allocated a reserved DHCP lease,
and that it was suspected it had picked up a new MAC address. Might be
worth checking your router to see if it has picked up a new IP.
1.45.1 is out, and reportedly fixed that problem.
Don't quote if if I haven't got that entirely right - quoting from memory.
So if you can find your gateway, perhaps try getting it to check for an
update.
I skipped from 1.43.1 to 1.45.1 without a problem.
On Fri, 20 Mar 2020 at 06:48, spoonwzd ***@***.***> wrote:
> Nooo don't tell me that :(
>
> I'm still on 1.44.2
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#28 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AJB3YI4E6YS7IN5TYFD3SS3RIJZILANCNFSM4LPOI43A
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABU4JYF7AWIN4TV2E3ONWV3RIKLG3ANCNFSM4LPOI43A>
.
spoonwzd commented
Phew!
frood88 commented
Specifically, the last two or so version updates have resulted in the TEG’s MAC address changing, which automatically results in an IP change when DHCP in use, and especially so when an IP reservation is mapped to the MAC address.
BJReplay commented
To the extent that this is a valid data point, I didn't see a change in IP
address jumping from 1.44.x to 1.45.1 - which might mean 1.45.1 incudes the
fix for this issue.
…On Fri, 20 Mar 2020 at 10:40, frood88 ***@***.***> wrote:
Specifically, the last two or so version updates have resulted in the
TEG’s MAC address changing, which automatically results in an IP change
when DHCP in use, and especially so when an IP reservation is mapped to the
MAC address.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJB3YI7O4R4E5S274F4RRSTRIKUQJANCNFSM4LPOI43A>
.
piersdd commented
I can confirm, on 1.45.1, I have a new MAC address and IP address, AND the old/original statically mapped IP address still works.