Assigning virtual Interfaces to Debian 5

Finally got Debian 5 to behave.

Only 2 issues now:

how to set up a virtual interface

and

How to make certain resolv.conf is not erased on a reboot.


What has chaged from Debian 4 to Debian 5?
--
Member - Liberal International This is (E-Mail Removed)
Ici (E-Mail Removed) God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
Point to http://tv.cityonahillproductions.com/

In comp.os.linux.misc The Doctor <(E-Mail Removed)> wrote:
> how to set up a virtual interface
> How to make certain resolv.conf is not erased on a reboot.

Are you (now) using NetworkManager, or are you using
/etc/network/interfaces to define network configuration?

If it's NetworkManager I can't help you. Otherwise I'll have a go.
Chris

["Followup-To:" header set to comp.os.linux.setup.]
On 2009-03-24, The Doctor <(E-Mail Removed)> wrote:
>
>
> Finally got Debian 5 to behave.
>
> Only 2 issues now:
>
> how to set up a virtual interface
>
> and
>
> How to make certain resolv.conf is not erased on a reboot.
>
Uninstall the resolvconf package, or learn how to set its defaults.

>
> What has chaged from Debian 4 to Debian 5?

Release notes should be available at debian.org.

In article <(E-Mail Removed)>,
Chris Davies <(E-Mail Removed)> wrote:
>In comp.os.linux.misc The Doctor <(E-Mail Removed)> wrote:
>> how to set up a virtual interface
>> How to make certain resolv.conf is not erased on a reboot.
>
>Are you (now) using NetworkManager, or are you using
>/etc/network/interfaces to define network configuration?
>
>If it's NetworkManager I can't help you. Otherwise I'll have a go.
>Chris

/etc/network/interfaces
--
Member - Liberal International This is (E-Mail Removed)
Ici (E-Mail Removed) God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
Point to http://tv.cityonahillproductions.com/

In comp.os.linux.misc The Doctor <(E-Mail Removed)> wrote:
> how to set up a virtual interface
> How to make certain resolv.conf is not erased on a reboot.

> [this is using] /etc/network/interfaces

OK.

1. Create a vIF by naming it in the same way that you would for eth0 or
wlan0, etc. Here's a line from a firewall I look after:

auto eth1:5
iface eth1:5 inet static
address 10.1.30.190
netmask 255.255.255.224
broadcast 10.1.30.191

After that it "just works". Or did you mean that you wanted a TUN/TAP
interface, or a Bridge? You can invent these by using the pre-up and up
lines for your required interface.


2. Leaving resolv.conf alone

* Have you removed the resolvconf package?

* If you're using ppp* have you told it to leave your resolv.conf alone?

* If you're using dhclient, try this:
echo 'make_resolv_conf () { return 0; }' > /etc/dhcp3/dhclient-enter-hooks.d/local

Chris

In article <(E-Mail Removed)>,
Chris Davies <(E-Mail Removed)> wrote:
>In comp.os.linux.misc The Doctor <(E-Mail Removed)> wrote:
>> how to set up a virtual interface
>> How to make certain resolv.conf is not erased on a reboot.
>
>> [this is using] /etc/network/interfaces
>
>OK.
>
>1. Create a vIF by naming it in the same way that you would for eth0 or
>wlan0, etc. Here's a line from a firewall I look after:
>
> auto eth1:5
> iface eth1:5 inet static
> address 10.1.30.190
> netmask 255.255.255.224
> broadcast 10.1.30.191
>
>After that it "just works". Or did you mean that you wanted a TUN/TAP
>interface, or a Bridge? You can invent these by using the pre-up and up
>lines for your required interface.
>

NO TUN interface or bridge.

Let me try the above.

>
>2. Leaving resolv.conf alone
>
> * Have you removed the resolvconf package?
>
> * If you're using ppp* have you told it to leave your resolv.conf alone?
>

All right, let me look at that.

> * If you're using dhclient, try this:
> echo 'make_resolv_conf () { return 0; }' >
>/etc/dhcp3/dhclient-enter-hooks.d/local
>
>Chris


--
Member - Liberal International This is (E-Mail Removed)
Ici (E-Mail Removed) God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
Point to http://tv.cityonahillproductions.com/