Fwd: [Voyage-linux] Correct way to get persistant nameserver info across reboots

[ka1ifq, Mike]

  Not a mistake, it helped me fix my problem.
Tnx...

On 12/13/2011 4:21 AM, Mirco Schmidt wrote:
> sending directly was my mistake...
>
> Anfang der weitergeleiteten E-Mail:
>
>> *Von: *Mirco Schmidt <mirco.schmidt at mac.com 
>> <mailto:mirco.schmidt at mac.com>>
>> *Betreff: **Re: [Voyage-linux] Correct way to get persistant 
>> nameserver info across reboots*
>> *Datum: *12. Dezember 2011 18:31:38 MEZ
>> *An: *ka1ifq <ka1ifq at sbcglobal.net <mailto:ka1ifq at sbcglobal.net>>
>>
>> search the List-Archive for /etc/network/interfaces
>>
>> or use something like this:
>>
>> auto eth0
>> # Beim Bootvorgang automatisch starten
>> iface eth0 inet static
>> 	address 192.168.0.97   # Zu benutzende Adresse
>> 	netmask 255.255.255.0  # Netzwerkmaske
>> 	gateway 192.168.0.1    # Standard-Gateway
>> 	dns-nameservers 192.168.0.1 10.10.0.2
>> Greetz
>> Mirco
>>
>>
>> Am 12.12.2011 um 17:04 schrieb ka1ifq:
>>
>>>
>>> This is something that just popped up on me. I am using Voyage 
>>> 0.7.0. Up till now the system has been used for incoming 
>>> connections, now I wish to do some outgoing things, but I get errors 
>>> when trying to connect out, even doing an apt-get update.
>>>
>>> Is there an official way to accomplish this?
>>>
>>> Still in the learning curve.
>>>
>>> Thanks, Mike.
>>> -- 
>>> Sent from my Suse Desktop
>>>
>>> _______________________________________________
>>> Voyage-linux mailing list
>>> Voyage-linux at list.voyage.hk <mailto:Voyage-linux at list.voyage.hk>
>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
>
>
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20111214/a1fc3ea7/attachment-0001.html>