search

Ansuel / tch-nginx-gui

Modified file to apply to a stock technicolor GUI
GNU General Public License v3.0
344 stars 52 forks source link

TG800VAC DHCP Wan Not Connecting #534

Closed Townie-au closed 5 years ago

Townie-au commented 5 years ago

Hi I have a couple of issues with GUI 8.11.49. Ive been talking kevdagoat. I installed by usin WinSCP method.

I have static internet connection VDSL. I have a home server with dhcp/dns servers and have a different subnet to the default setting. Ive found that I can get the internet to connect if I choose fixed ip put all the details in, close the window, then open the window again, switch to dhcp and then back to static and close. Then it will connect, providing I only use the default router address. Also after awhile the internet drops out and I need to do the above again. I have in the xdsl section "No direct path found" on several driver items.

Townie-au commented 5 years ago

I'm going load 16.3 with gui 8.11.49 into bank 2 and 17.2 with the latest gui_dev into bank 1 and compare the config files. I noticed I'm getting a lot of dnsmasq can't open listen port on 53 and when I check ngisk is using it. Also dhcp config says modem gateway address not my server 2012 dhcp and dns address. I notice not any comments. Have I outstayed my welcome? :(

FrancYescO commented 5 years ago

Validation missing for uci_wan_peerdns?

should be fixed in latest dev

I noticed I'm getting a lot of dnsmasq can't open listen port on 53 and when I check ngisk is using it.

nginx is using port 53? O.o

Also dhcp config says modem gateway address not my server 2012 dhcp and dns address.

So you don't use the modem dns "proxy" dns server but a custom dns server by your server? i think this should be easily changed by assigning a differente DNS to lan clients, while on the WAN side there is another func to not use the provided dns in the internet modal (on latest dev)

Townie-au commented 5 years ago

The latest release fixed the peerdns and nginx is no longer using port 53. However there is still dnsmasq: failed to create listening socket for port 53: Address already in use Thu Feb 28 23:11:50 2019 daemon.crit dnsmasq[4200]: FAILED to start up

When I check there is only dnsmasq using it, as it's supposed too. I'll get this 16.3 and 17.2 going and post what I find.

I use server 2012 r2 for local dns server and dhcp server. My dhcp points to itself for dns server and usually gives those details to the clients.

FrancYescO commented 5 years ago

Probably something about ipv4/v6 that is trying to bind port 53 2 times

From: Townie-au notifications@github.com Sent: Friday, March 8, 2019 10:53:21 PM To: Ansuel/tch-nginx-gui Cc: Francesco M; Comment Subject: Re: [Ansuel/tch-nginx-gui] TG800VAC DHCP Wan Not Connecting (#534)

The latest release fixed the peerdns and nginx is no longer using port 53. However there is still dnsmasq: failed to create listening socket for port 53: Address already in use When I check there is only dnsmasq using it, as it's supposed too. I'll get this 16.3 and 17.2 going and post what I find.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Ansuel/tch-nginx-gui/issues/534#issuecomment-471088744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEXNgSZA5hbcm0WGorDeYqaDt4MqNhZVks5vUtvRgaJpZM4bYlY7.

Townie-au commented 5 years ago

I set it up, and worked straight away on 16.3. I've been looking at the config files, that look the same. There's no port 53 blocked error. Thinking something to do dnsmasq and/or the dhcp scripts that control the request of ip address from wan and the lan, but you know over my head.

Townie-au commented 5 years ago

So on the latest gui dev with 16.3 the blocked dns port still persists, downgrading to the latest stable solves the problem. I set the wan spoof manually with the option macadd line. I also noticed even though set to dhcp the config was in atm mode. I had to change to adsl2 then back to dhcp and the internet connected.

Townie-au commented 5 years ago

Can I browse the config files in the passive bank via WinSCP?

FrancYescO commented 5 years ago

/overlay/nameofthepassivebank

Townie-au commented 5 years ago

Can I install gui on both banks?

Townie-au commented 5 years ago

It just says bank_1 and the files are the files in the active firmware. No bank_2 but gui confirms bank_2 has 17.2. Is there a way to extract the rbi file from 17.2?

FrancYescO commented 5 years ago

if no /overlay/bank_2 folder, means the bank_2 is just not configured/never booted

you should have enough space to install GUI on both banks if device is with more than 32mb of flash, remember that with bank check flag setted in gui>extra, bank_1 is always forced

kevdagoat commented 5 years ago

Ok to close?

kevdagoat commented 5 years ago

Advice: Stay with 16.3

Townie-au commented 5 years ago

Yep, sorry. I found for some reason even with stock rooted 17.2 dhcp doesn't work with my isp but 16.3 does. Nothing to do with GUI so yep close it kev

kevdagoat commented 5 years ago

You have to :)

I don’t have collaborator access :(

On 1 May 2019, at 6:47 pm, Townie-au notifications@github.com wrote:

Yep, sorry. I found for some reason even with stock rooted 17.2 dhcp doesn't work with my isp but 16.3 does. Nothing to do with GUI so yep close it kev

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.