"
Hi,
that's the same box (router and cable modem). In bridge mode it's just assigning a public ip address directly to my opnsense wan interface. In router mode you would get a private ip and the box would act as a router with NAT. Restarted this box multiple times, and waited at least an hour between beacuse somestimes i takes an hour to work again (especially when MAC changes). Just to make clear: No hardware change on my end, the mac address of the WAN interface is the same it's been before and no piece of hardware got changed. Just installed 2.5.11 an rebooted the VM (running on TrueNAS Scale 24.04).
Eventually i got it solved with calling the ISP, they completely resetted/reconfigured the box and then it started working again. Still weired because it exactly happended when rebooting after installing 2.5.11, running this setup for 1 1/2 years and never had this when doing updates (and i did almost each when it came out).
Kind regards
Jan
that's the same box (router and cable modem). In bridge mode it's just assigning a public ip address directly to my opnsense wan interface. In router mode you would get a private ip and the box would act as a router with NAT. Restarted this box multiple times, and waited at least an hour between beacuse somestimes i takes an hour to work again (especially when MAC changes). Just to make clear: No hardware change on my end, the mac address of the WAN interface is the same it's been before and no piece of hardware got changed. Just installed 2.5.11 an rebooted the VM (running on TrueNAS Scale 24.04).
Eventually i got it solved with calling the ISP, they completely resetted/reconfigured the box and then it started working again. Still weired because it exactly happended when rebooting after installing 2.5.11, running this setup for 1 1/2 years and never had this when doing updates (and i did almost each when it came out).
Kind regards
Jan
