Hi,
I just replaced the stock firmware on my Buffalo WHR-G125 with the tomato firmware and can't connect to mysqueezebox.com or my squeezebox server through the receiver. With the stock firmware I don't recall having to forward any ports. So the logitech site says the receiver uses ports 9000 and 3483 but I saw a post here saying you shouldn't need to forward any ports. Just to try it out I did try to forward those ports with no luck. Can anyone running tomato firmware shed some light on this?
Thanks.
Results 1 to 5 of 5
-
2010-05-31, 10:32 #1Junior Member
- Join Date
- Oct 2009
- Posts
- 14
Need help: Anyone running tomato firmware on router?
-
2010-05-31, 12:30 #2
I'm running Tomato v1.25 on my Linksys WRT54GL - no problems here. Sorry I can't be more help.
-
2010-05-31, 12:34 #3Senior Member
- Join Date
- Oct 2005
- Posts
- 2,769
I'm also running Tomato here, without any port forwarding (don't do that!), and without problems.
http://www.tux.org/~peterw/
Note: The best way to reach me is email or PM, as I don't spend time on the forums.
Free plugins: AllQuiet Auto Dim/AutoDisplay BlankSaver ContextMenu DenonSerial
FuzzyTime KidsPlay KitchenTimer PlayLog PowerCenter/BottleRocket SaverSwitcher
SettingsManager SleepFade StatusFirst SyncOptions VolumeLock
-
2010-05-31, 15:40 #4Junior Member
- Join Date
- Oct 2009
- Posts
- 14
Thanks, guys. I should have realized when I checked the devices list in the tomato GUI only the controller was showing up. I had to hold the button on the front of the receiver and then reconnect to it from the controller.
I can connect to my squeezebox server running on my PC but not to mysqueezebox.com now. Furthermore, if I try to play a song off my squeezebox server it plays for a second and then stops. Looking at the tomato logs the traffic from my squeezebox server PC and squeezebox receiver have very strange destination addresses, not what I would expect.Last edited by audiophile; 2010-05-31 at 16:23.
-
2010-06-01, 20:24 #5Junior Member
- Join Date
- Oct 2009
- Posts
- 14
Ok, not sure the heck was up but I had to hold the button on the receiver and reconfigure it via the controller. The receiver was sending packets to my old gateway for some reason. Real strangeness, but everything works now.

Reply With Quote
