Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - L

#1
Quote from: frakkin64 on December 20, 2024, 03:51:17 PMI assume this is happening before the WAN IP is assigned, have you tried dropping the lease on the DHCP server in the modem to 10 minutes (same as IP passthrough lease time)?

It is indeed happening before the WAN IP is assigned, and I honestly haven't tried this yet, and it will probably fix the problem well enough. I'll set it up and report back if the issue ever persists longer than 10 minutes.

I think I am anticipating switching ISPs in the foreseeable future, so I may ultimately not pursue bypassing the ONT for the time being.
#2
Quote from: Aerowinder on December 20, 2024, 12:01:23 AMBeing on GPON is actually better...
Thanks for the insight, I'll take a deeper look and get back to you later if any issues arise.
#3
Quote from: Aerowinder on December 19, 2024, 08:48:24 PMBypass is the way. Anything else is a waste of effort. If you are interested, I and probably hundreds of others here can assist. I literally did this 2 weeks ago.
I heard about this but I'm not certain it's the approach I want to take (no doubt if this had been available years ago when I was originally building my network I would have done it). Firstly, I don't think I'm on XGS-PON, I'm not sure how much of a hassle it would be to get that changed but it doesn't sound super fun since I really don't need more than 1Gbps. Secondly, my router is a thin client with an Intel PCIe NIC so I don't have an SFP+ port and can't add one, so if I did decide to go this route what would you recommend for converting the WAS-110 with SFP+ to RJ45?
#4
I am having an issue where if my AT&T BGW320-500 modem reboots sometimes my router WAN will be given a private IP. The modem is in IP passthrough mode to my router. My modem's IP is 192.168.100.254 and this is the IP the router is sometimes given initially after a reboot, as opposed to my public IP. This breaks external connections to my network, but it is fixable by restarting the WAN interface on the router. I have tried using Reject Leases with 192.168.100.254 as the IP, but then the router is never able to get a public IP either. This appears to be the same issue referenced in this post: https://forum.opnsense.org/index.php?topic=37408.0.

This message appears in the logs when Reject Leases is used:
/interfaces.php: The command '/sbin/dhclient -c '/var/etc/dhclient_wan.conf' -p '/var/run/dhclient.ix0.pid' 'ix0'' returned exit code '15', the output was 'dhclient 71871 - - dhclient-script: Reason PREINIT on ix0 executing DHCPREQUEST on ix0 to 255.255.255.255 port 67 DHCPACK from 192.168.100.254 rejected. DHCPREQUEST on ix0 to 255.255.255.255 port 67 DHCPACK from 192.168.100.254 rejected. DHCPREQUEST on ix0 to 255.255.255.255 port 67 DHCPACK from 192.168.100.254 rejected. DHCPREQUEST on ix0 to 255.255.255.255 port 67 DHCPACK from 192.168.100.254 rejected. DHCPREQUEST on ix0 to 255.255.255.255 port 67 DHCPACK from 192.168.100.254 rejected. DHCPDISCOVER on ix0 to 255.255.255.255 port 67 interval 2 DHCPOFFER from 192.168.100.254 rejected. DHCPDISCOVER on ix0 to 255.255.255.255 port 67 interval 2 DHCPOFFER from 192.168.100.254 rejected. DHCPDISCOVER on ix0 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 192.168.100.254 rejected. DHCPDISCOVER on ix0 to 255.255.255.255 port 67 interval 7 DHCPOFFER from 192.168.100.254 rejected. DHCPDISCOVER on ix0 to 255.255.255.255 port 67 interval 14 DHCPOFFER from 192.168.100.254 rejected.
Is this an expected issue or is there a bug? Do I need to find another way to solve this problem? I think I could potentially monitor the WAN interface IP and restart it every minute or so if it's not a public IP.