Recent content by jarip

Actually it wasn't, turned out that the culprit was Suricata running on 192.168.4.1 interface. When turned off, client connected immediately with correct IP. Sorry about that, obviously I wasn't sure where the problem is. All good with 3006.102.4_beta at the moment, thank you.

Changed it in pfSense to 192.168.52.2 and rebooted 88U Pro. Dnsmasq error message is gone, but VLAN still not working. Looking at system log in pfSense, I see Apr 16 19:53:41 dhcpd 63542 DHCPDISCOVER from xx:xx:xx:xx:xx:xx via igc3: network 192.168.4.0/24: no free leases So it looks...

Not sure if this is a proper place to post this, but at least it is related to beta. This is my first trying to get guest VLAN to work with Netgate 6100 and RT-AX88U Pro, which was "dirty" updated from 3004.388.8_4 to 3006.102.4_beta1. In pfSense I configured VLAN interface 192.168.52.1/24 with...

I did not imply, that the weirdness was in the router.

Thanks, it's now back to normal. It's just seems weird, that it already was ok earlier after update...

Dirty update on RTAX88U Pro from 3004_388.6_2 to 3004_388.7_beta1 seemed to go well and GUI was as expected, but hours later when connected again (login page seemed ok), was greeted with this: Router is connected to the firewall via LAN port and connects succesfully to routerahs.asus.com...

Re-tested in 2024: https://blog.nexxwave.be/publieke-dns-malware-filters-in-2024-getest/

https://www.asuswrt-merlin.net/download has checksum for RT-AC68U_386.12_2.trx as 77d32e086cc8802f678b79a778638c3fd44dfaa79d4a4c5a62e14bd0285b719d, but extracted file has 7CBFF05AA94F66C34E4A1E915FE3B7229EC20AD500A2B6DA6C4E481864B530FB

When I take a backup of settings (Asus router, pfSense, what ever), I put the current firmware version info as part of the filename of the backup and never try to restore that backup, if firmware version has changed.

Ok, just stick around, I'm sure you will get it going with so many experts here.

What is your RT- AX86U mode? If AP mode, my problem accessing RT-AC68U was solved by switching from DHCP to static IP RT-AC68U problem with DHCP?

I had problem accessing web UI, but only after some time had passed after reboot. RT-AC68U problem with DHCP?

PfSense has static mappings based on MAC addresses that live in the LAN segment, so it would always give the same IP address for the router. The one, that is now configured to be used as router's LAN IP. After that I have not had any trouble accessing web GUI. I don't have any recollection of...

I was getting ready to revert the firmware and connected the router directly to a laptop, which is normally connected via wifi. I disconnected the router from LAN, power cycled it and fired up Asus Discovery, which found the router at 192.168.1.1. I thought that maybe that was at least related...

"Both" was configured with both used firmwares. I think I'll revert back to 3.0.0.4.386.48262 (or Asuswrt RT-AC68U_386.5_0) and stick with it, if GUI stays available across reboots. If not, then I guess it's time to get a new router.