Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Jul 2014 19:11:25 +0200 (CEST)
From:      wp1160256-paul <paul@mueller-blockhaus.de>
To:        Vladislav Prodan <universite@ukr.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: vlan address-aliassing not working
Message-ID:  <1634671217.97151.1406826685276.open-xchange@app02.ox.hosteurope.de>
In-Reply-To: <1406825080.567617631.8yxkvawh@frv35.fwdcdn.com>
References:  <20140731123414.388112e1@paul-pc.mbnet.de> <1406825080.567617631.8yxkvawh@frv35.fwdcdn.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Thanks,
I read, it works with other names of the vlans, but why not with these?
Isn't this the new default of the vlannames?

Greetings Paul

> Vladislav Prodan <universite@ukr.net> hat am 31. Juli 2014 um 18:48
> geschrieben:
>
>
>
>
>
> --- Original message ---
> From: "Paul Blockhaus" <paul@mueller-blockhaus.de>
> Date: 31 July 2014, 13:35:18
>
>
>
> > Hello Guys,
> >
> > recently I set up ezjail on my UTM and made aliasses for my vlan, so
> > far no problems, but after reboot the aliases for the vlans hasn't been
> > recreated, only for the physical non-vlan NICs.
> > Any Ideas why the aliases weren't created, is it my mistake?
> >
> > Greetings Paul
> >
> > my /etc/rc.conf:
> ...
> > ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0"
> > vlans_em0="50 150"
> > ifconfig_em0_50="inet 192.168.2.1 netmask 255.255.255.0"
> > ifconfig_em0_150="inet 192.168.6.1 netmask 255.255.255.0"
> ...
> > ifconfig_em0_alias0="inet 192.168.1.2 netmask 255.255.255.0"
> > ifconfig_em0.50_alias0="inet 192.168.2.3 netmask 255.255.255.0"
> > ifconfig_em0_150_alias0="inet 192.168.6.2 netmask 255.255.255.0"
>
>
> Use the following settings:
> cloned_interfaces="vlan50 vlan150"
>
> ifconfig_vlan50="inet 192.168.2.1/24 vlan 50 vlandev em0 mtu 1500 up"
> ifconfig_vlan150="inet 192.168.6.1/24 vlan 150 vlandev em0 mtu 1500 up"
>
> ifconfig_em0_alias0="inet 192.168.1.2/24"
> ifconfig_vlan50_alias0="inet 192.168.2.3/24"
> ifconfig_vlan150_alias0="inet 192.168.6.2/24"
>
>
>
> --
> Vladislav V. Prodan
> System & Network Administrator
> support.od.ua
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
From owner-freebsd-questions@FreeBSD.ORG  Thu Jul 31 18:40:18 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 94910A9D
 for <freebsd-questions@freebsd.org>; Thu, 31 Jul 2014 18:40:18 +0000 (UTC)
Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "ozzie.tundraware.com",
 Issuer "ozzie.tundraware.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 54FAF269F
 for <freebsd-questions@freebsd.org>; Thu, 31 Jul 2014 18:40:17 +0000 (UTC)
Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2])
 (authenticated bits=0)
 by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s6VIda2u012839
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
 for <freebsd-questions@freebsd.org>; Thu, 31 Jul 2014 13:39:37 -0500 (CDT)
 (envelope-from tundra@tundraware.com)
Message-ID: <53DA8D68.9040508@tundraware.com>
Date: Thu, 31 Jul 2014 13:39:36 -0500
From: Tim Daneliuk <tundra@tundraware.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject: Help With ipwf Rules
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (ozzie.tundraware.com [75.145.138.73]); Thu, 31 Jul 2014 13:39:37 -0500 (CDT)
X-TundraWare-MailScanner-Information: Please contact the ISP for more
 information
X-TundraWare-MailScanner-ID: s6VIda2u012839
X-TundraWare-MailScanner: Found to be clean
X-TundraWare-MailScanner-From: tundra@tundraware.com
X-Spam-Status: No
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2014 18:40:18 -0000

I am working on a FreeBSD 10-STABLE machine that has two NICS:

    re0  - Connects to the internet
    em0  - NATs to a private flat Class C LAN  (192.168...)

There is already an IPFW ruleset in place, primarily to control
who can get in via re0 - pretty much anything is allowed out from
the FreeBSD machine itself and from the 192 network.

I need to add a few additional ipfw rules to do the following:

1) Bandwidth shaping/management.   I need to ensure that the total
    amount of bandwidth being used by hosts on the LAN never exceeds,
    say, 3 mb/sec down and 1 mb/sec up.  Then I need a similar rule
    for traffic originating ON the FreeBSD box itself.

2) I need to create rules that permit a VOIP phone to plug in on
    the NATed LAN and still work properly.

I am somewhat familiar with ipfw having set up the original rule set
but I am a bit unclear on how to do these two things.   The help of
some kind soul with the expertise would be most appreciated ...


-- 
----------------------------------------------------------------------------
Tim Daneliuk     tundra@tundraware.com
PGP Key:         http://www.tundraware.com/PGP/




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?1634671217.97151.1406826685276.open-xchange>