Gargoyle Forum

Here's the output: root@PF:~# iptables -t filter -L lease_mismatch_check Chain lease_mismatch_check (1 references) target prot opt source destination REJECT all -- !amazon-ca6e4221f.lan anywhere MAC 18:74:2E:1C:C0:8D reject-with icmp-port-unreachable REJECT all -- amazon-ca6e4221f.lan anywhere MAC !...

Well... this is quite strange. Before re-installation of Gargoyle on my 3700v2, everything was working fine. After I re-installed, this strange behaviour has started. And the VMs are always the same, Vmware Player is the same, the physical PC is the same. Anyway, on the "connected devices"...

Why is that happening?
Is there any way to fix this issue?

Yes, it worked.
After disabling the checkbox, both VM started to work correctly

Yes, I have 3 static IP addresses, but they are out of the DHCP range. Let me explain. DHCP range is 192.168.0.100 to 200 DHCP statically assigned IP addresses are set to 192.168.0.10, 11, 12. The VM (I tried both with Windows and Linux) take the IP address from the DHCP range. From within the VM I ...

A couple of days ago I had to re-install Gargoyle 1.10.0 on my router because for some reason it started to continuously reboot. After re-installation (from scratch ... I did not restore from backup), the VMs running on my laptop don't surf the internet anymore, when the NIC is set in "bridged&...

I believe you when you say that it exists since 8 years, but please believe me when I say that I never experienced this behaviour with V1.10.

Anyway, I'm happy to help... also for the other bug I found.
If I can be of any help, just let me know what you need.

Here's the output: root@PF:~# iptables -t mangle -nvL | grep openvpn 26 1794 openvpn_down_bw udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:43203 0 0 openvpn_up_bw all -- tun0 eth1 0.0.0.0/0 0.0.0.0/0 0 0 openvpn_down_bw all -- eth1 tun0 0.0.0.0/0 0.0.0.0/0 3 207 openvpn_up_bw udp -- * eth1 0.0.0.0/0 0.0...

I tried to reboot the router (Gargoyle), but nothing has changed.

This is the 2nd bug that I have discovered in V1.12 in less then 1 month (1st one was related to AdBlock + Tor).

Maybe I'll go back to 1.10 ... 1.12 it's too buggy

Just to say, with V1.10 it was working correctly.