Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to change Modem IP and DHCP DNS server #1170

Open
seanwlk opened this issue Jun 1, 2023 · 4 comments
Open

Unable to change Modem IP and DHCP DNS server #1170

seanwlk opened this issue Jun 1, 2023 · 4 comments

Comments

@seanwlk
Copy link

seanwlk commented Jun 1, 2023

Hi, recently Telecom moved my setup and i was using SFP port directly in the modem, now because it was never taken off in years it basically melted inside because of the heat and when i moved, the technicains were not able to recover the serial number in order to connect the GPON. They gave me a PON adapter which is a ZTE F601 that for whatever reason decided that the default 192.168.1.1 IP was his. I accessed the admin panel of the thinghy and there is no way to change the IP so at the time of the installation i dont even remember how, i handled to change the Modem IP in the Local Network card to 192.168.1.5.

Now, i was messing with PiHole and the query logs were bothering me since the client was always showing up as the modem itself since i configured the DNS for the modem to the PiHole docker container running on my NAS so i went and tried changing the DNS for the DHCP config and was not able to do it because as shown in the first image below there is some sort of conflic with the gateway IP which i dont see any reason to be since the gateway has 192.168.100.1. Next thing i did was clicking the reset network button and almost punched my monitor because i instantly remembered the PON duplicate IP problem.
In some way i handled to access the modem UI via wifi and dumped the backup tar.gz and went editing the /etc/config/network file to replace all that was 192.168.1.1 to 192.168.1.5 and changed the DHCP dns server in /etc/config/dhcp to 192.168.1.15 (PiHole instance) all booted but i had no internet access. Had to restore back with the zip.

What i find weird is this interface config in /etc/config/network , that gateway looks wrong to me since it's supposed to be 192.168.100.1 to WAN

config interface 'wan'
	option demand '0'
	option password 'alicenewag'
	option macaddr 'REDACTED'
	option reqopts '1 3 6 15 33 42 51 121 249'
	option keepalive_adaptive '0'
	option dns_metric '0'
	option ifname 'waneth4'
	option netmask '255.255.255.0'
	option ipaddr '192.168.1.1'
	option gateway '192.168.1.100'
	option proto 'pppoe'

Any suggestion? My final goal is to be able to freely modify the DHCP setting and chaging the modem IP back to what it was (i wish i remembered how i did it the first time because it took me half a day that time too)

Device Model/Firmware: DGA4132 - AGTHP_2.0.0
GUI Version: 9.6.65-89342d7b

Please go to Cards >> GUI Settings >> Debug Report and press the Generate button.
Attach the debug file here: DebugHelper2023-06-01-2237.tar.gz

Description of problem, HOW TO REPRODUCE, Media/Photos:
image
192.168.1.15 is what i want to put but it does not let me because the validation fails for the modem IP which is in the first input box of the form in the modal
image

@bandit400
Copy link

Try these steps:
(1) move "DHCP Start address" from 192.168.1.2 to 192.168.1.32 and click Save
(2) move "ModeM IP Address" from 192.168.1.1 to 192.168.1.5 and click Save
(3) move "DNS server" from 192.168.1.1 to 192.168.1.15 and click Save

@seanwlk
Copy link
Author

seanwlk commented Jun 4, 2023

Try these steps: (1) move "DHCP Start address" from 192.168.1.2 to 192.168.1.32 and click Save (2) move "ModeM IP Address" from 192.168.1.1 to 192.168.1.5 and click Save (3) move "DNS server" from 192.168.1.1 to 192.168.1.15 and click Save

Does not work, i tried moving the DHCP pool address already in whatever way. I cannot save the form and it always points me to the modem IP error i showed above.

@bandit400
Copy link

bandit400 commented Jun 4, 2023

It is not correct that in WAN you have an IP address of the same class as in LAN. The generic WAN section of a network is as shown below (but is for VDSL connection, not for WAN/ETH4):

config interface 'wan' option auto '1' option proto 'pppoe' option demand '0' option ipv6 '0' option peerdns '1' option reqopts '1 3 6 15 26 33 42 51 121 249' option keepalive_adaptive '0' option dns_metric '0' option ifname 'ptm0' list dns '8.8.8.8' list dns '8.8.4.4' option username 'username' option password 'password'

@seanwlk
Copy link
Author

seanwlk commented Jun 4, 2023

Problem is that i did not set that. It kinda was left like that after the FTTH conenction i had with SFP port to the one i was force to with the WAN connection to port 4 with a PON.
Any way to fix without full reset? i have plenty of customizations running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants