Date: Sun, 21 Jun 2015 16:43:37 +0200 From: Kajetan Staszkiewicz <vegeta@tuxpowered.net> To: "Chuck @ Mantis" <chuck@mantis.biz> Cc: freebsd-pf@freebsd.org Subject: Re: adding an additional block & gateway Message-ID: <2646372.HZAPXgGrRl@energia> In-Reply-To: <55843762.3040106@mantis.biz> References: <55839619.8000603@mantis.biz> <1704069.kZvlBVo68Y@energia> <55843762.3040106@mantis.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Dnia piątek, 19 czerwca 2015 11:38:10 Chuck @ Mantis pisze: > Our data center responded to your question, here is the text: > > We can confirm that the new netblock is routed direct via your vlan as with > your original netblock > > VLAN: vlan655-cbcbmedi-809, Created at: Mon Oct 20 13:42:05 2014 > 802.1Q Tag: 655, Internal index: 205, Admin State: Enabled, Origin: Static > Layer 3 interface: vlan.655 (UP) > IPV4 addresses: > 60.34.75.209/28 > 79.112.227.33/27 > Protocol: Port Mode, Mac aging time: 300 seconds > Number of interfaces: Tagged 0 (Active = 0), Untagged 1 (Active = 1) > ge-5/0/20.0*, untagged, access > Just add another subnet and hosts in it (carp?) to the usual interface and use the existing gateway, it should work just fine. Both gateways are the same device which will happily accept traffic from any source. Or start using real routing. -- | pozdrawiam / greetings | powered by Debian, FreeBSD and CentOS | | Kajetan Staszkiewicz | jabber,email: vegeta()tuxpowered net | | Vegeta | www: http://vegeta.tuxpowered.net | `------------------------^---------------------------------------' [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEUEABECAAYFAlWGzZsACgkQ47RQr217OhQm3gCYoduyH1QvaddZ/XeIsL0/LaUa DwCeO7lpKV9MjAls9dfqGytQawxdgTw= =7KWS -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2646372.HZAPXgGrRl>