Hi everyone - first post, so go easy on me!
I've put Tomato on an RT-N16 to use as a remote wireless audio recorder, which is partly a learning project, to:
a) be a 'standalone' wireless client on the existing wireless LAN
b) share a USB flash stick to the wireless LAN (samba).
c) record from a USB mic onto the stick (eg. speex files)
It started off well. I installed Tomato ("v1.28.9054 MIPSR2-beta K26 USB Ext"), set it up in "Wireless Client" mode (seemed the most logical choice) and it's getting an IP (192.168.2.215/24) wirelessly via DHCP. I can access its configuration pages and telnet using that IP, from elsewhere on the wireless network.
I left the LAN IP as 192.168.1.1, and assume that I don't care about or need to use that (is that right?).
I've enabled samba, shared the USB flash drive, and used the custom config box to make samba listen on all interfaces (initially it was just listening on 192.168.1.1).
And that's where I'm stuck - nomatter what I do (even reducing wireless MTUs on Windows 7 per some Googled suggestions), I can't access the share wirelessly, eg. "net use r: \\192.168.2.215\share" on my laptop says it cant find the network path (though HTTP and telnet to 192.168.2.215 still work).
However if I also cable my laptop (wired NIC = 192.168.1.215) to the RT-N16 and use "net use r: \\192.168.1.1\share", it works. Doing a limited port scan then reveals:
192.168.1.1 - TCP ports 139, 22, 445, 80 open
192.168.2.215 - TCP ports 2222, 80, 8080 open (no samba!)
Do I have to do some internal port forwarding or IPTABLES stuff on the RT-N16, or something else, or is my whole approach wrong, or is this a known problem area?
I looked for a quick way to disable the Tomato firewall (why would I want a firewall behind a firewall, on an effectively closed embedded system?) but it seems you can't - that's the first thing I've found so far that I really don't like.