Two comments and then I need to hit the road. <br><br>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.<br>
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 issue.<br><br>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.<br>
<br>Ok... two hour drive to work. Good luck and hope it works out for you.<br><br><br><div class="gmail_quote">On Sun, Jun 28, 2009 at 6:10 PM, jeremy jozwik <span dir="ltr"><<a href="mailto:jerjoz.forums@gmail.com">jerjoz.forums@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">returns:<br>
<br>
[root@localhost sbin]# ./ip addr add <a href="http://192.168.0.200/24" target="_blank">192.168.0.200/24</a> dev eth1<br>
Cannot find device "eth1"<br>
<br>
also got a lovely little notification on the linux system bar<br>
"SELinux is preventing the iptables from using potentially mislabeled files"<br>
<div><div></div><div class="h5"><br>
<br>
On Sun, Jun 28, 2009 at 9:05 AM, Lowell Higley<<a href="mailto:higleylh@gmail.com">higleylh@gmail.com</a>> wrote:<br>
> As root, I drop the following in a terminal:<br>
><br>
> iptables -A POSTROUTING -t nat -j MASQUERADE -s <a href="http://192.168.0.0/24" target="_blank">192.168.0.0/24</a><br>
> sysctl -w net.ipv4.ip_forward=1<br>
> ip addr add <a href="http://192.168.0.200/24" target="_blank">192.168.0.200/24</a> dev eth1<br>
> ifconfig eth1 up<br>
> ssh <a href="mailto:root@192.168.0.202">root@192.168.0.202</a><br>
><br>
> Works like a charm. Only caveat is make sure you clear the previous SSH<br>
> signature out of .ssh/known_hosts<br>
><br><br>
</div></div></blockquote></div><br>