Gargoyle Forum

Hi everyone, just joined the forum.
I've recently installed 1.8.1 on a TL-WA850RE. I tried 1.9.1 but feel 1.8.1 is more stable (for instance I seemed to get random client disconnects with 1.9.1).
Little question:
In Gateway mode, I've got the LAN side of the router configured 192.168.2.1.
If I tracert from a LAN client (DHCP) outside the LAN I see:
1 <1 ms <1 ms 1 ms Gargoyle.lan [192.168.2.1]
Where is "Gargoyle.lan" configured? I can see nothing in the Admin console to set this.
I can WinSCP & PuTTY into the router so can easily modify any files in there.
Many thanks & Seasons Greetings
Marty

Router identification page under System.

Hi lantis, thanks for your reply.

Yes, I've seen that, which defaults to "lan" and so that's where that bit comes from. It was the gargoyle bit I was interested in.

I've tried changing the entry to (say) pudding.lan but then tracert gives gargoyle.pudding.lan.

So - any idea where the "gargoyle" part comes from?

Cheers
Martin

If you check your /etc/hosts file, do you now have 2 entries for the routers ip?

If yes, i believe this is where the issue comes from, and it has been fixed in a later version.

Hi Lantis,

Thanks for the suggestion - there is nothing in my hosts file which would account for this.

I'm pretty sure 'gargoyle' is getting appended at the router.

Sorry if i was unclear, and perhaps i'm misunderstanding your response.
I was referring to /etc/hosts on the Gargoyle Router.
Can you confirm that is what you were answering?

Hi Lantis,

yes, I misunderstood you, I looked at the hosts file on my own pc.

I've checked the hosts file on the router and you are quite correct - I've modified the file and changed the entry from 'Gargoyle' to 'Router' and tracert now reports:
1 <1 ms <1 ms <1 ms Router.lan [192.168.2.1]

Splendid - thanks for your help and interest.

Happy New Year to you and yours,
Marty

ps: for anyone interested, a reboot of the router was necessary for the change to become effective.

Ok great.

Well the good news is this behaviour will be fixed in the next version. The code is already live.

Thanks for following up on the solution