Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. G

    Port Forwarding troubles - AX88U, 386.1_2

    Can you pls further detail/explain what is not working now ? access to your NAS remotely, .... ?
  2. G

    Solved Strange IP address in wireless log ...

    A router reboot solved the issue ... :rolleyes:
  3. G

    Port Forwarding troubles - AX88U, 386.1_2

    Quite obvious but this you check this one : (yes, Open NAT port fwd is new and when you put it off it also put the below off as well):
  4. G

    Solved Strange IP address in wireless log ...

    Yes, DHCP logging on and no, no error messages with duplicate name ; May I ask why you are focusing on duplicate hostname ? As I see it, the issue could also be at router side since the PC itself has a correct LAN IP (as shown above), works OK with LAN and WAN, only its IP address is...
  5. G

    Solved Strange IP address in wireless log ...

    Disconnecting, but I just wired it this afternoon to make a test, otherwise it is always connected via Wifi. There is no duplicate host name since WL card and NIC card have different mac address. It seems that arp table on the router has a 169 address , but I cannot manually delete it: arp -d...
  6. G

    Solved Strange IP address in wireless log ...

    No, I have just rebooted again one more time, no error on mac address, still being reported wrongly and still showing the correct 192. address in W10 ... :oops: PS: this only happens when connected to wireless, if I go via wire, PC is correctly recognised and reported in the router ...
  7. G

    Solved Strange IP address in wireless log ...

    Thanks for the suggestion ; that did not make it.
  8. G

    Solved Strange IP address in wireless log ...

    Thanks. In fact no, even after disconnect/reconnect, this PC is systematically reported in the WL log screen with this 169 IP address, while on the PC I have this:
  9. G

    Open VPN Client- Very Weird Experience

    check this parameter:
  10. G

    Solved Strange IP address in wireless log ...

    Hi, just have a look here, this is a W10 PC connected to my 2.4GHz network on my AX86U (386.1_2): and then here : and finally: Any idea why this PC is not recognised with its legitime 192.168.1.73 lan IP ? Thx, GS (PS: this only happens with this specific PC ! which has nothing special...
  11. G

    Change in OpenVPN Server connectivity within LAN ?

    yes, I understand it is usefull for testing the config only. I had the impression it did not work before, so I was wrong, nevermind
  12. G

    Change in OpenVPN Server connectivity within LAN ?

    Hi, a bit by hasard I just noticed that it is now possible to connect to OpenVPN Server while being connected in LAN. Is this a correct that this was not the case some time ago or I dreamt ? Thx, GS
  13. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    I do not think so because when you set the ASUS router in AP mode, you do not have access anymore to the OpenVPN Server gui screen ...
  14. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    ... the objective of all this set-up is to provide an on-demand OpenVPN Server via a second router connected to an AC/DC homePlug that can be switched on/off remotely. BTW this was @eibgrad suggestion I saw in another threat. So, the first thing was to have that second router working correctly...
  15. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    could it be possible that the one below (on main server) is generated thanks to the static routes definition ? -A FORWARD -s 192.168.1.0/24 -d 192.168.98.0/24 -i br0 -o br0 -j ACCEPT EDIT: I think I found it: in nat-start script on second router, there is this one: iptables -I INPUT -s...
  16. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    ... wow, I am struggling to follow the recents posts. I confirm that on my second router, the firewall is OFF (otherwise 1.x devices cannot access 98.x devices) but nat is ON (otherwise devices on 98.x network do not have access to internet). I can show here any output of iptables of both...
  17. G

    Kernel error on RT-AX86U Merlin 386.1_2

    Hi, getting this: Mar 17 17:38:28 kernel: wl0: PSM microcode watchdog fired at 1537848 (seconds). Resetting. Mar 17 17:38:28 kernel: wl0: reason = psm watchdog at 1537848 seconds. corerev 131 ucode revision 1570.159 features 0x3106 Mar 17 17:38:28 kernel: psmdebug 0x01ff000c phydebug 0x0 macctl...
  18. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    .. no problem, I really appreciate your help and BTW it is rather my bad than yours. I shoud have specified in the drawing that devices were Windows machines. The push route made the job dispite the client access set to LAN only Again, @eibgrad many thanks for your help, GS
  19. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    ... There you lost me ... The client that is connecting to the OpenVPN Server is a windows machine !!! the option you talk about "inbound firewall" is on the OpenVPN Client on the router !!!. Refering to your previous post, is this what you mean ?
  20. G

    Solved issue accessing a LAN device thru OpenVPN Server connected device

    Thanks for your answer, I need now to try to understand it ... and how to practically implement this. :oops: I guess the first thing is a to add a "route 192.168.98.0/24 255.255.255.0" and/or "192.168.1.0/24 255.255.255.0" in the custom config .... for the CN I must admit at this point in time...
Top