[shr-unstable] making bricks...
higleylh at gmail.com
Sun Jun 28 18:22:57 CEST 2009
Two comments and then I need to hit the road.
1) I tried using a SHR unstable image a few days ago (the 26th I believe)
and found that it had some serious issues and went back to my previous
image. I was able to SSH in but I wasn't able to do small things like
receive SMS or make/receive calls. I could send SMS, though.
2) I have never used SELinux (never really been that paranoid?) So I can't
speak to that error. I'm using a gentoo based distro and not having that
Only thing I can think of off the top of my head is did you update the
kernel and the bootloader as well? If not, try that that, too. I'd
download the latest image of each (including rootfs) and try again. After
that, I am out of ideas.
Ok... two hour drive to work. Good luck and hope it works out for you.
On Sun, Jun 28, 2009 at 6:10 PM, jeremy jozwik <jerjoz.forums at gmail.com>wrote:
> [root at localhost sbin]# ./ip addr add 192.168.0.200/24 dev eth1
> Cannot find device "eth1"
> also got a lovely little notification on the linux system bar
> "SELinux is preventing the iptables from using potentially mislabeled
> On Sun, Jun 28, 2009 at 9:05 AM, Lowell Higley<higleylh at gmail.com> wrote:
> > As root, I drop the following in a terminal:
> > iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
> > sysctl -w net.ipv4.ip_forward=1
> > ip addr add 192.168.0.200/24 dev eth1
> > ifconfig eth1 up
> > ssh root at 192.168.0.202
> > Works like a charm. Only caveat is make sure you clear the previous SSH
> > signature out of .ssh/known_hosts
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the community