1
24.7 Production Series / Re: Able to get online but not access UI suddenly
« on: August 13, 2024, 08:58:19 pm »
Might be IP conflict? i had similar issue to IP conflicts, double check your DHCP server settings.
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.
Pages: [1]
2
24.7 Production Series / Re: 24.7 CPU Temps
« on: August 13, 2024, 08:48:28 pm »
I still think the discrepancy in temps readings make no sense lol.
Isn't the temps supposed to be read directly from the sensor on the CPU?im not that BSD nerd. but i never faced such issue in windows or linux Ahh.
plus 10-15c differences sounds way too much of a difference,furthermore the external(which act as heat sink) body of my N5105 doesnt even feel that hot to indicted that CPU is really in the 50c.
https://i.imgur.com/W5UCYKo.mp4
Isn't the temps supposed to be read directly from the sensor on the CPU?im not that BSD nerd. but i never faced such issue in windows or linux Ahh.
plus 10-15c differences sounds way too much of a difference,furthermore the external(which act as heat sink) body of my N5105 doesnt even feel that hot to indicted that CPU is really in the 50c.
https://i.imgur.com/W5UCYKo.mp4
Code: [Select]
root@OPNsense:~ # sysctl -a | grep temperature
hw.acpi.thermal.tz0.temperature: 47.1C
dev.cpu.3.temperature: 46.0C
dev.cpu.2.temperature: 46.0C
dev.cpu.1.temperature: 45.0C
dev.cpu.0.temperature: 45.0C
root@OPNsense:~ # sysctl -a | grep temperature
hw.acpi.thermal.tz0.temperature: 47.1C
dev.cpu.3.temperature: 48.0C
dev.cpu.2.temperature: 47.0C
dev.cpu.1.temperature: 46.0C
dev.cpu.0.temperature: 45.0C
root@OPNsense:~ # sysctl -a | grep temperature
hw.acpi.thermal.tz0.temperature: 47.1C
dev.cpu.3.temperature: 47.0C
dev.cpu.2.temperature: 46.0C
dev.cpu.1.temperature: 45.0C
dev.cpu.0.temperature: 47.0C
root@OPNsense:~ # sysctl -a | grep temperature
hw.acpi.thermal.tz0.temperature: 47.1C
dev.cpu.3.temperature: 49.0C
dev.cpu.2.temperature: 48.0C
dev.cpu.1.temperature: 47.0C
dev.cpu.0.temperature: 46.0C
root@OPNsense:~ #
root@OPNsense:~ # sysctl -a | grep temperature
hw.acpi.thermal.tz0.temperature: 47.1C
dev.cpu.3.temperature: 48.0C
dev.cpu.2.temperature: 46.0C
dev.cpu.1.temperature: 46.0C
dev.cpu.0.temperature: 46.0C
3
General Discussion / Re: Selective routing for vlan through VPN - No Internet (Wireguard)
« on: August 11, 2024, 08:46:18 pm »
FIXED The damn issue, after 6 hours of testing.
1- first i turend off KEA DHCP and went back to ISC DHCP (not sure if it was related)
2- had to change the rule of nat dns port forwarding and turn off ( Destination / Invert).
Then everything worked nicely.
1- first i turend off KEA DHCP and went back to ISC DHCP (not sure if it was related)
2- had to change the rule of nat dns port forwarding and turn off ( Destination / Invert).
Then everything worked nicely.
4
24.7 Production Series / Re: Cpu core temps not correct - intel n5105.
« on: August 11, 2024, 08:40:12 pm »
which ones wrong? the htop ones? i dont think so. as i was testing proxmox previously and temps were around 35-39c in idle. So id say the widget showing the wrong temps somehow.
5
General Discussion / Selective routing for vlan through VPN - No Internet (Wireguard) - FIXED
« on: August 09, 2024, 08:01:14 pm »
Hey Guys,
I have been trying to wrap my head around this issue, where im trying route only vlan20 through VPN.
Below steps i took:
1-created vlan20 network -> turned on DHCP
2- setup WG client (Windscribe) as per the config file. -> connected with handshake
3-created wiregard interface
4-created WG gateway
5-Created nat outbound rule for the WG.
6-Created vlan20 rule to use WG gateway and created port forward nat rule to forward all dns quires to opnsense.
unbound already been restarted several times BTW and its listening to all interfaces..
Same setup working fine on pfsense but not opnsene for some reason? i have been trying to get it to work without any success :'(
any help would be appreciated.
I have been trying to wrap my head around this issue, where im trying route only vlan20 through VPN.
Below steps i took:
1-created vlan20 network -> turned on DHCP
2- setup WG client (Windscribe) as per the config file. -> connected with handshake
3-created wiregard interface
4-created WG gateway
5-Created nat outbound rule for the WG.
6-Created vlan20 rule to use WG gateway and created port forward nat rule to forward all dns quires to opnsense.
unbound already been restarted several times BTW and its listening to all interfaces..
Same setup working fine on pfsense but not opnsene for some reason? i have been trying to get it to work without any success :'(
any help would be appreciated.
6
24.7 Production Series / Cpu core temps not correct - intel n5105.
« on: August 09, 2024, 06:52:30 pm »
Hey guys,
I noticed in the latest build, there's a big variation in CPU core temps between the widget and the actual temps of Htop? what gives? is it bug in the widget?
I noticed in the latest build, there's a big variation in CPU core temps between the widget and the actual temps of Htop? what gives? is it bug in the widget?
7
Documentation and Translation / Re: AdGuard Home setup guide
« on: April 18, 2024, 11:02:52 pm »
Hey Guys,
I just want to to double check,,
Is it ok to bind 0.0.0.0 interface instead of choosing local ip address?
I faced some issue with binding only local lan & 127.0.0.1 & ::1, where out of nowhere it stopped forwarding DNS to clients (even after adding firewall rule), so i changed the listening interfaces to 0.0.0.0 and i noticed it started working again and AGH seems now resolving ipv6 clients requests not just ipv4.
edit: NVM AGH stopped receiving DNS requests again, had to add router ip as DNS servers in opnsense setting to get it to work!! i dont even know if thats the right solution tbh..
I just want to to double check,,
Is it ok to bind 0.0.0.0 interface instead of choosing local ip address?
I faced some issue with binding only local lan & 127.0.0.1 & ::1, where out of nowhere it stopped forwarding DNS to clients (even after adding firewall rule), so i changed the listening interfaces to 0.0.0.0 and i noticed it started working again and AGH seems now resolving ipv6 clients requests not just ipv4.
edit: NVM AGH stopped receiving DNS requests again, had to add router ip as DNS servers in opnsense setting to get it to work!! i dont even know if thats the right solution tbh..
Pages: [1]