[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: newbie: netstart and net.inet.ip.forwarding
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: newbie: netstart and net.inet.ip.forwarding
- From: Csillag Tamas <cstamas_(_at_)_digitus_(_dot_)_itk_(_dot_)_ppke_(_dot_)_hu>
- Date: Fri, 10 Sep 2004 14:18:05 +0200
- Reply-to: Csillag Tamas <cstamas_(_at_)_digitus_(_dot_)_itk_(_dot_)_ppke_(_dot_)_hu>
On 09/09, Csillag Tamas wrote:
> Hi,
>
> I am new to openbsd and I need some hint with the hostname.if(5)
> schema and ip.forwarding.
>
> So first, I am using 3.6 snapshot from Aug 27.
> Right now the machine is disconnected from the backbone network so I
> copied the essential (I hope) config files and I cannot upgrade to the
> latest available snapshot.
>
> The setup of the network is the following:
> em0: Uplink (not connected yet)
> em1: vlan trunk interface
> em2: DMZ
>
> # more hostname.*
> ::::::::::::::
> hostname.em0
> ::::::::::::::
> inet 192.168.5.2 255.255.255.224
> ::::::::::::::
> hostname.em2
> ::::::::::::::
> inet 123.456.109.62 255.255.255.192
> ::::::::::::::
> hostname.vlan219
> ::::::::::::::
> inet 10.2.19.254 255.255.255.0 NONE vlan 219 vlandev em1
> !ifconfig em1 up
> ::::::::::::::
> hostname.vlan220
> ::::::::::::::
> inet 10.2.20.254 255.255.255.0 NONE vlan 220 vlandev em1
> !ifconfig em1 up
> ::::::::::::::
> (I ommited the next 7 vlans...)
>
> When I boot, em0 and the vlan* interfaces are fine. But I do not know
> what to put in hostname.em1 (I would like to avoid '!ifconfig em1 up').
> I tried echo up > hostname.em1 , but it did not work.
> (The iface was down.) The em2 interface is also down and I cannot set
> up it even with:
> sh /etc/netstart em2
> (I had to setup by hand)
>
> And another strange thing that I cannot make changes to hostname.xxx
> files then run: sh /etc/netstart xxx
> It does not alter the settings of the interface.
> I can say: ifconfig vlan220 destroy; sh /etc/netstart vlan220
> but this kind of command does not work for emN interfaces.
>
> Another stangeness that in spite of the fact I set net.inet.ip.forwarding to 1
> it does not route packets between vlan220 and DMZ.
...
This problem was my mistake (sorry).
The only question is what to write to hostname.em1 which is a vlan trunk
interface? and how to alter with netstart the already working interface.
(It is possible or only for bring them up at boot?)
Thanks.
>
> What am I doing wrong?
> Thanks in advance.
--
cstamas
Visit your host, monkey.org