> And you don't think I have read the mail list/archives?
yes.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Dec 28, 2008, at 2:44 AM, arne anka wrote:
only a few weeks ago was the recurrent thread about the issue, even
regarding the living in the same subnet -- please check the archives
before asking!
And you don't think I have read the mail list/archives?
Would I ask, if the suggested items wou
only a few weeks ago was the recurrent thread about the issue, even
regarding the living in the same subnet -- please check the archives
before asking!
> ip_forward=no
that would efecctively prevent any access from the fr to the inet via your
host pc, whatever you do else.
in my host's (de
On Dec 27, 2008, at 4:29 PM, William Kenworthy wrote:
I moved to the 192.168.0.* to get connected. "I" could not get it
working the other way.
Just configure the freerunner for a different IP and have the linux
box
nat it out onto the network.
On my network, I subnet the 192.168.0 into 19
Just configure the freerunner for a different IP and have the linux box
nat it out onto the network.
On my network, I subnet the 192.168.0 into 192.168.0.0/30 and
192.168.0.192/27 so they stay separate and I dont have to worry about
the ADSL modem - more problematic than the FR to stay configured.
Debian stable & OM default w/updates. OM is not my daily phone, yet.
My debian machine is 192.168.0.101, the default GW is 192.168.0.1
Was able to get the default install onto the net, and grab updates a
few weeks ago. Right after I did the update, now I am not able to get
back onto the net.
6 matches
Mail list logo
