Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

The problem: servers appear to be broken inside my Ubuntu chroot. No matter what kind of server I try to run, they all seem unresponsive (VLC server won't respond to client, mkRemote doesn't move the cursor, Apache gives an error about binding to port 80 and won't start, etc.).

If I'm not mistaken, what should normally happen inside a chroot is that all ports are shared between the chroot and the host, so if another machine tries to hit the host at port 80, it will still see the chrooted Web server. However, here, that isn't what's happening.

When I run netstat from the chroot, every single process lists a foreign address of 0.0.0.0:*, meaning that the only machine which can act as a client is the local host. This is clearly incorrect and abnormal behaviour, as any process on my primary machine meant to be publicly visible lists a foreign address of :::* (which I assume means that any client can see it from any port).
Edit: Disregard that; apparently the foreign address only distinguishes between whether it's listening for IPv4 or IPv6 connections, so it doesn't seem relevant here.

So far, Googling has returned nothing of value, and I'm basically stumped. Any ideas? Could it just be some setting which one of the chroot patch devs enabled by default, or does it seem like a more complicated issue?

Thanks.

More context: http://rootzwiki.com/topic/14682-webos-servers-inside-chrooted-ubuntu/

share|improve this question
    
Possibly relevant information: * buu700.com/tpbind * buu700.com/tpnetstat * buu700.com/tpnmap –  Ryan Lester Jan 9 '12 at 23:13
    
What are your firewall rules (iptables -nvL; iptables -t nat -nvL; iptables -t mangle -nvL)? What traffic does tcpdump show? –  Gilles Jan 9 '12 at 23:47
    
1  
I enabled the Web interface within the chrooted VLC, then went to 192.168.1.5:8080 from both the webOS browser and my laptop browser. The page showed up fine in the local webOS browser, but just hanged when I tried to see it from my laptop (192.168.1.6). buu700.com/tptcpdump0 –  Ryan Lester Jan 10 '12 at 1:03
1  
Sigh. Cross-posted on SU; answer accepted there, so closing here –  Michael Mrozek Nov 6 '12 at 17:49
show 3 more comments

closed as too localized by Michael Mrozek Nov 6 '12 at 17:49

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

3 Answers

The only difference between 0.0.0.0:* and :::* is that the first is IPv4-only and the second is IPv6 (or, more typically, IPv4 and IPv6 since there is a compatibility layer).

How are you trying to connect to the server? (if you're using localhost, maybe that gets resolved to ::1, the IPv6 form?) Try connecting using 127.0.0.1 instead. Perhaps they are running but are unavailable because you are attempting to use IPv6 to connect.

The other option is that maybe a firewall is preventing access to the ports. Try ufw disable (as root) if you have the default Ubuntu firewall installed. Remember that if you are using the tablet on an unprotected network, this may have negative security consequences. ;-)

share|improve this answer
    
Ah, got it, thanks. I've been trying to connect to an mkRemote server and a VLC server using IPv4 from my Android phone (no response from either), so I can't use localhost. I'd try hitting a localhost Web server, but this is what happens when I try to run nginx or Apache: buu700.com/tpbind. ufw doesn't appear to be installed. Any other ideas? –  Ryan Lester Jan 9 '12 at 21:56
    
Also, these may be relevant: buu700.com/tpnetstat ; buu700.com/tpnmap –  Ryan Lester Jan 9 '12 at 22:16
    
What is the output of sudo iptables -v -L? –  Mike Jan 10 '12 at 0:03
    
    
Have you tried iptables -F to clear the firewall rules out? Looks like there are a good number of them. (I didn't look at them in detail though.) –  Mike Jan 10 '12 at 1:12
add comment

Did you mount /proc, /dev etc. ?

# mount

Try netcat:

# nc -v -l 8089
# nc -v 127.0.0.1 8089

Check system log files.

share|improve this answer
add comment

People of the future, do not fear. If you've found this question, you've come across a frustrating problem and are looking for a sure-fire solution. Luckily, I have answered this question on a different SE site. It has worked for both the OP and me. It can be found here.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.