Gargoyle Forum

also for that "option noscan '1' " setting in AP mode which enables 40 mhz mode in all conditions without taking into account the other neighbour Ap's; There is a lot I don't know about your router environment but this statement makes me wonder if your in a busy wifi area and 1.9.x series...

If you have a PPPoE connection established, how does Gargoyle know the 'route' to the bridged modem?
The default route should now be the external ISP and there is no additional 'internal' network configured to access the bridged modem.

Lantis,

Thanks, I'll upgrade and reconfigure rather then take a change to unbrick later.

Hi Adri, thanks for your help again. I am just trying to set everything up such that my modem is bridged and the router (with Gargoyle firmware) is handling everything else (including the VLAN tag as needed). I haven't had any success with simply setting the router to PPPoE straight away. It seems ...

iSPY version 1.9.x from 27-01-2017?

I don't know what you are trying to achieve..... If you are using PPPoE, then the WAN-side ip-address is negotiated as part of setting up the PPPoE connection with the ISP server. DHCP is never used in combination with PPPoE. You talking about a modem sitting in the middle? In that case the modem ha...

Would there be any problem upgrading to gargoyle 1.9.2 from the iSpy 1.9.x version of 27-jan-2017 with 'preserve settings'?
Or it it recommended to redo the configuration?

This might get you started: config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix 'REMOVED' config interface 'lan' option ifname 'eth1' option force_link '1' option type 'bridge' option pro...

Anyone using a bridge config shouldn't preserve settings. Because we updated the way bridges are handled. Yeah.... And this is documented where? On the download page, it is said preserve setting is possible between 1.9.0 and 1.9.1! Also the client bridge is no longer working as a bridge. It is now ...

Lantis, I also did a sysupgrade and a Linksys WRT160NL from 1.9.0 to 1.9.1, using 'preserve settings'. The update was succeeded, but afterwards the router went into a 'boot loop'. I solved it by using the standard Openwrt 'recovery button', telnet into the router and issuing a 'firstboot'. It seems ...