I have heard of that specific bug yet.
Perhaps your not on the latest and it may be fixed when the latest does push out (can take up to 5 days)
Just a heads up tho, what you are doing, if it works feel free to go with it... But is is NOT bridged.
Doing what your doing, can have actual negative effects, as all data is being double firewalled, going through two NATs. You could run into issues if you need to do port forwarding.
Really, your dlink's 'external' address is an internal of the cgn3.
I would wait till your sure your on the latest firmware and try the bridging again.
Until then, if you are just looking for better wireless range, you would be better to just put the dlink as an access point instead.
Perhaps your not on the latest and it may be fixed when the latest does push out (can take up to 5 days)
Just a heads up tho, what you are doing, if it works feel free to go with it... But is is NOT bridged.
Doing what your doing, can have actual negative effects, as all data is being double firewalled, going through two NATs. You could run into issues if you need to do port forwarding.
Really, your dlink's 'external' address is an internal of the cgn3.
I would wait till your sure your on the latest firmware and try the bridging again.
Until then, if you are just looking for better wireless range, you would be better to just put the dlink as an access point instead.