Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#223245 - 06/06/2003 23:11 JReceiver 0.25 help please
silicon
stranger

Registered: 09/06/2002
Posts: 11
I would be forever grateful if someone could help me solve my JReceiver issues. I am running 0.25 of JReceiver with blackdown Java 1.4.1 (have tried Sun also). I had an older version running fine on my server a long time ago...but I bought an Audiotron and no longer needed the Rio running. Now...I want to put the Rio in my bedroom and I decided to reinstall JReceiver.

JReceiver runs, streams to Xmms, responds properly to all queries (tags) but the Rio will not see it. The Rio boots fine (NFS) and proceedes to the "Searching for Music" display but never finds the JReceiver server.

Server is Gentoo Linux running as a router/firewall, DNS, DHCP, FTP, HTTPD, etc. It's basically a full on server. My IPTables config is as follows:

# Generated by iptables-save v1.2.8 on Sat Jun 7 01:54:18 2003
*mangle
:PREROUTING ACCEPT [128213:97732695]
:INPUT ACCEPT [2188:467414]
:FORWARD ACCEPT [126025:97265281]
:OUTPUT ACCEPT [2063:481318]
:POSTROUTING ACCEPT [128233:97769753]
COMMIT
# Completed on Sat Jun 7 01:54:18 2003
# Generated by iptables-save v1.2.8 on Sat Jun 7 01:54:18 2003
*nat
:PREROUTING ACCEPT [2301:142900]
:POSTROUTING ACCEPT [395:33177]
:OUTPUT ACCEPT [389:32937]
-A PREROUTING -i eth0 -p tcp -m tcp --dport 4099:5190 -j DNAT --to-destination 192.168.0.254
-A PREROUTING -i eth0 -p tcp -m tcp --dport 6891:6901 -j DNAT --to-destination 192.168.0.254
-A PREROUTING -i eth0 -p udp -m udp --dport 6891:6901 -j DNAT --to-destination 192.168.0.254
-A PREROUTING -i eth0 -p tcp -m tcp --dport 20000:20019 -j DNAT --to-destination 192.168.0.254
-A PREROUTING -i eth0 -p tcp -m tcp --dport 2000 -j DNAT --to-destination 192.168.0.254
-A PREROUTING -i eth0 -p tcp -m tcp --dport 6881:6889 -j DNAT --to-destination 192.168.0.254
-A PREROUTING -i eth0 -p tcp -m tcp --dport 2001 -j DNAT --to-destination 192.168.0.253
-A PREROUTING -i eth0 -p udp -m udp --dport 1791:1792 -j DNAT --to-destination 192.168.0.20
-A POSTROUTING -s 192.168.0.0/255.255.255.0 -o eth0 -j MASQUERADE
COMMIT
# Completed on Sat Jun 7 01:54:18 2003
# Generated by iptables-save v1.2.8 on Sat Jun 7 01:54:18 2003
*filter
:INPUT DROP [0:0]
:FORWARD DROP [1:48]
:OUTPUT ACCEPT [1307:419799]
MZIN - [0:0]
MZOUT - [0:0]
:INETIN - [0:0]
:INETOUT - [0:0]
:LDROP - [0:0]
:LREJECT - [0:0]
:LTREJECT - [0:0]
:TCPACCEPT - [0:0]
:TREJECT - [0:0]
:UDPACCEPT - [0:0]
:ULDROP - [0:0]
:ULREJECT - [0:0]
:ULTREJECT - [0:0]
-A INPUT -i eth0 -j INETIN
-A INPUT -s 192.168.0.0/255.255.255.0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i eth1 -p udp -m udp --dport 67 -j ACCEPT
-A FORWARD -i eth0 -o eth1 -j INETIN
-A FORWARD -i eth1 -o eth0 -j INETOUT
-A FORWARD -s 192.168.0.0/255.255.255.0 -i ! eth0 -o ! eth0 -j ACCEPT
-A OUTPUT -o eth0 -j INETOUT
-A INETIN -m state --state INVALID -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 5 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 9 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 10 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 15 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 16 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 17 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 18 -j TREJECT
-A INETIN -p icmp -m icmp --icmp-type 8 -m limit --limit 1/sec -j ACCEPT
-A INETIN -p icmp -m icmp --icmp-type 8 -j TREJECT
-A INETIN -p icmp -m icmp ! --icmp-type 8 -j ACCEPT
-A INETIN -p tcp -m tcp --dport 21:23 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 25 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 80 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 110 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 113 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 2000:2001 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 4099:5190 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 6699 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 6881:6889 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 6891:6901 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 20000:20019 -j TCPACCEPT
-A INETIN -p tcp -m tcp --dport 50000:50500 -j TCPACCEPT
-A INETIN -p udp -m udp --dport 68 -j UDPACCEPT
-A INETIN -p udp -m udp --dport 1791:1792 -j UDPACCEPT
-A INETIN -p udp -m udp --dport 6257 -j UDPACCEPT
-A INETIN -p udp -m udp --dport 6891:6901 -j UDPACCEPT
-A INETIN -p udp -m udp --dport 27950:27960 -j UDPACCEPT
-A INETIN -m state --state ESTABLISHED -j ACCEPT
-A INETIN -p tcp -m tcp --dport 1024:65535 -m state --state RELATED -j TCPACCEPT
-A INETIN -p udp -m udp --dport 1024:65535 -m state --state RELATED -j UDPACCEPT
-A INETIN -j TREJECT
-A INETOUT -j ACCEPT
-A LDROP -p tcp -m limit --limit 2/sec -j LOG --log-prefix "TCP Dropped " --log-level info
-A LDROP -p udp -m limit --limit 2/sec -j LOG --log-prefix "UDP Dropped " --log-level info
-A LDROP -p icmp -m limit --limit 2/sec -j LOG --log-prefix "ICMP Dropped " --log-level info
-A LDROP -f -m limit --limit 2/sec -j LOG --log-prefix "FRAGMENT Dropped "
-A LDROP -j DROP
-A LREJECT -p tcp -m limit --limit 2/sec -j LOG --log-prefix "TCP Rejected " --log-level info
-A LREJECT -p udp -m limit --limit 2/sec -j LOG --log-prefix "UDP Rejected " --log-level info
-A LREJECT -p icmp -m limit --limit 2/sec -j LOG --log-prefix "ICMP Rejected " --log-level info
-A LREJECT -f -m limit --limit 2/sec -j LOG --log-prefix "FRAGMENT Rejected "
-A LREJECT -j REJECT --reject-with icmp-port-unreachable
-A LTREJECT -p tcp -m limit --limit 2/sec -j LOG --log-prefix "TCP Rejected " --log-level info
-A LTREJECT -p udp -m limit --limit 2/sec -j LOG --log-prefix "UDP Rejected " --log-level info
-A LTREJECT -p icmp -m limit --limit 2/sec -j LOG --log-prefix "ICMP Rejected " --log-level info
-A LTREJECT -f -m limit --limit 2/sec -j LOG --log-prefix "FRAGMENT Rejected "
-A LTREJECT -p tcp -j REJECT --reject-with tcp-reset
-A LTREJECT -p udp -j REJECT --reject-with icmp-port-unreachable
-A LTREJECT -p icmp -j DROP
-A LTREJECT -j REJECT --reject-with icmp-port-unreachable
-A TCPACCEPT -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -m limit --limit 20/sec -j ACCEPT
-A TCPACCEPT -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -m limit --limit 2/sec -j LOG --log-prefix "Possible SynFlood "
-A TCPACCEPT -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j TREJECT
-A TCPACCEPT -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -j ACCEPT
-A TCPACCEPT -m limit --limit 2/sec -j LOG --log-prefix "Mismatch in TCPACCEPT "
-A TCPACCEPT -j TREJECT
-A TREJECT -p tcp -j REJECT --reject-with tcp-reset
-A TREJECT -p udp -j REJECT --reject-with icmp-port-unreachable
-A TREJECT -p icmp -j DROP
-A TREJECT -j REJECT --reject-with icmp-port-unreachable
-A UDPACCEPT -p udp -j ACCEPT
-A UDPACCEPT -m limit --limit 2/sec -j LOG --log-prefix "Mismatch on UDPACCEPT "
-A UDPACCEPT -j TREJECT
-A ULDROP -p tcp -m limit --limit 2/sec -j ULOG --ulog-prefix "LDROP_TCP"
-A ULDROP -p udp -m limit --limit 2/sec -j ULOG --ulog-prefix "LDROP_UDP"
-A ULDROP -p icmp -m limit --limit 2/sec -j ULOG --ulog-prefix "LDROP_ICMP"
-A ULDROP -f -m limit --limit 2/sec -j ULOG --ulog-prefix "LDROP_FRAG"
-A ULDROP -j DROP
-A ULREJECT -p tcp -m limit --limit 2/sec -j ULOG --ulog-prefix "LREJECT_TCP"
-A ULREJECT -p udp -m limit --limit 2/sec -j ULOG --ulog-prefix "LREJECT_UDP"
-A ULREJECT -p icmp -m limit --limit 2/sec -j ULOG --ulog-prefix "LREJECT_UDP"
-A ULREJECT -f -m limit --limit 2/sec -j ULOG --ulog-prefix "LREJECT_FRAG"
-A ULREJECT -j REJECT --reject-with icmp-port-unreachable
-A ULTREJECT -p tcp -m limit --limit 2/sec -j ULOG --ulog-prefix "LTREJECT_TCP"
-A ULTREJECT -p udp -m limit --limit 2/sec -j ULOG --ulog-prefix "LTREJECT_UDP"
-A ULTREJECT -p icmp -m limit --limit 2/sec -j ULOG --ulog-prefix "LTREJECT_ICMP"
-A ULTREJECT -f -m limit --limit 2/sec -j ULOG --ulog-prefix "LTREJECT_FRAG"
-A ULTREJECT -p tcp -j REJECT --reject-with tcp-reset
-A ULTREJECT -p udp -j REJECT --reject-with icmp-port-unreachable
-A ULTREJECT -p icmp -j DROP
-A ULTREJECT -j REJECT --reject-with icmp-port-unreachable
COMMIT
# Completed on Sat Jun 7 01:54:18 2003

No ports are blocked on the internal eth1 iface that the RIO is making it's SSDP requests on. In tcpdump I do see the requests to broadcast but I never see a reply from JReceiver. I have tried the Rio driver set as the IP of the server as well as the hostname with the same results. The MySQL database is in order and everything else seems to be fine. The Rio just for some reaon does not see the JReceiver server. The Sonic Blue software running on a Windows machine does work.

Please, any help would be greatly appreciated. Or, a nice re-write of the Rio kernel to include SMB support hehe :-)

Thanks

P.S. I can't figure out how to get rid of the UBBCode.

Top
#223246 - 06/06/2003 23:38 Re: JReceiver 0.25 help please [Re: silicon]
silicon
stranger

Registered: 09/06/2002
Posts: 11
Ok, here is something new. After a reboot I get the following under the rio driver configuration page:

Validation Error - You must correct the following error(s) to save the form:
unable to load because jreceiver.common.rpc.RpcException: security-problem getting settings (class SettingEditAction)

Top
#223247 - 07/06/2003 23:44 Re: JReceiver 0.25 help please [Re: silicon]
shawn
stranger

Registered: 15/11/2001
Posts: 47
Loc: Silicon Valley
Double check your password settings in the jreceiver.properties configuration and the jreceiver manager application -- specifically the rio fields since you're still able to use XMMS. That was always the bit that got me when I'd update JRec.

Top
#223248 - 09/06/2003 21:19 Re: JReceiver 0.25 help please [Re: shawn]
silicon
stranger

Registered: 09/06/2002
Posts: 11
Thanks for the suggestion. I'll try that this weekend (work full time, school at night).

Top
#223249 - 28/06/2003 12:29 Re: JReceiver 0.25 help please [Re: silicon]
silicon
stranger

Registered: 09/06/2002
Posts: 11
Well, still no go. I'm lost....... :-( jreceiver.properties and the jreceiver app have the same login and pass. Still boots from NFS and starts searching but just hangs there.

Top