ssh from wan/network of the first router

[aligatro]

First of all, thanks for your hard work. You made an excellent webgui. It's much easier to use then luci and x-wrt. Also, I find it more responsive. I am using my fonera as wifi repeater, but there is a problem: I can't access ssh and webgui from the network of the first router. I played with iptables but didn't have any success.

Thanks in advance.

[Eric]

This issue should now be fixed in the latest bleeding-edge firmware. Please let me know if you still have problems.

[aligatro]

The bug is gone. Thank you. One question: Is it normal to not receive ping when pinging from the first router's network ?

Just noticed another problem: I can't access internet from console of the router. However, wifi clients(and also the pc connected by cable) of the second router are able to surf the web.

Code: Select all

root@OpenWrt:~# wget http://www.google.ca/intl/en_ca/images/logo.gif
wget: bad address 'www.google.ca'

Code: Select all

root@OpenWrt:~# opkg update
Downloading http://downloads.openwrt.org/kamikaze/8.09/atheros/packages/Packages.gz
wget: bad address 'downloads.openwrt.org'
Collected errors:
 * opkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp    -P /tmp/opkg-JeonJE http://downloads.openwrt.org/kamikaze/8.09/atheros/packages/Packages.gz'
root@OpenWrt:~#

[Eric]

Yes, I am aware of the ping issue. I actually solved the bug you reported only for TCP connections, but since both web and ssh access are tcp, they now work fine. I'm not aware of any other real connection needed to the bridge so I stopped there.

I suspect (but I'm not certain) that the inability to connect out from the bridge itself is a dns issue. Since it has a static ip, it doesn't know where the network dns server is, even though I do currently have a place to specify the gateway. If you're comfortable sshing in (and you seem to be, otherwise you wouldn't have this problem...) Try editing /etc/config/network, adding "option dns [your dns server ip]" under the lan section.

[aligatro]

Now it just simply waits and then shows "bad address" or "bad port spec" when I ping some address with "http://" in front.

[Eric]

Yeah, turns out the problem was a bit more complex than that. It should be fixed now (and the dns should automatically get set to the gateway now too. Really, I probably should have just implemented separate DNS fields for the bridge, but I was feeling lazy ) New bleeding-edge firmware has been uploaded.

Oh, and you should now be able to ping the bridge device from the outer network too.

[aligatro]

Thanks. Everything works great now.