forum.excito.org

Just installed it - seems to work ok!

Have you looked at this http://forum.bittorrent.com/topic/18974 ... c/?p=47774

I have had some problems with bubba2 2.4 version too.

By looking into forked-daap's logs I found out that avahi-daemon blocks daaps starting.


nolla@bubba:~$ tail -f /var/log/forked-daapd.log
[2012-04-04 00:46:27] mdns: Failed to create service browser: Bad state
[2012-04-04 00:46:27] player ...

I can't get it work either with b2 2.4rc. I get it work really well with an earlier version.

I had bad sectors in my hard drive and something wrong with my motherboard aswell. With a new unit all is working well.

However, the internet problem still existed! With the new unit, the problem could be solved with the help of this post: http://forum.excito.net/viewtopic.php?f=1&t=3397#p17556 ...

B2 Upgrade successful! I hit a bump with the firewall, which wasn't forwarding traffic from the internal network to the outside world. The above instructions didn't help, and in fact locked me out! What did help was

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

which got the local ...

Hopefully this is not related to 2.4 rc or it's installer, but my bubba died during reinstallation process. Now, everytime I plug in power to my bubba, Bubba's led goes on, but does not blink even once. It reads hd for 5 secs and then stops reading it.

What does it mean if bubba does not blink?

I guess that my bubba is going through the same issue: http://forum.excito.net/viewtopic.php?f=9&t=3400#p17329

I guess this could be a same issue as this: http://forum.excito.net/viewtopic.php?f=9&t=3160

Binkem wrote:You have to connect to the WAN port if you use the rescue stick!

I did, and saw the ip lease on my router.

After executing commands that Johannes asked, like with every other configuration here, I cannot access to Bubba anymore. Not even via rescue system. While trying to fix bubba with rescue system, I can see that bubba leases an ip, but I still cannot access it. Connection timed out is responded ...

Now while I've been trying to get my network to work properly, I have also tested web interface's firewall setup. The firewall page crashes permanently if trying to add additional rules. I have tried to open a tcp wan port (3784) and everytime I have done that, the firewall settings page have ...

I did find my old firewall config that I used in bubba, while I had earlier release installed in it. So, I formatted hdd once again, because after editing firewall rules, I accidentally locked myself out from bubba. I replaced empty firewall.conf with the old firewall.conf and ran "/sbin/iptables ...

I did...

nolla@bubba:/etc/init.d$ sudo iptables -A FORWARD -i eth1 -j ACCEPT
nolla@bubba:/etc/init.d$ sudo iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
nolla@bubba:/etc/init.d$ sudo iptables -A FORWARD -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
sudo /etc/init.d/bubba.firewall ...

Well, it indeed seems to be at the right place.
Now, I'm not the greatest expert on this file.
But if I see this correctly, some elements seem to be missing.
If I get that right, your file only opens up some ports for external access.
Here is my firewall.conf for a reference. Note: eth0 is WAN ...