RE: creating a netbsd router

[Derrick Lobo <derrick.lobo%givex.com@localhost>]

Thanks  Yes based on the instruction provided by Brook Milligan I create the 
interface file with "up" in it and it worked..

Thanks once again..  I have it working I have tested it with connecting 4 
switches to the 4 port as well as connecting DHCP and static hardware to the 
4 ports and all worked with no issues.


Derrick


-----Original Message-----
From: Johnny Billquist [mailto:bqt%update.uu.se@localhost]
Sent: Wednesday, July 19, 2017 4:34 PM
To: Derrick Lobo; Francisco Valladolid H.; netbsd-users%netbsd.org@localhost
Subject: Re: creating a netbsd router

On 2017-07-19 18:01, Derrick Lobo wrote:
> Thanks Johnny
>
> So does that means each of the interface has an ip eg 192.168.0.1 on
> wm1
> 192.168.0.2 on wm2 and so on and then just bridge all the interface.
> Ill try that . for now only wm1 had an ip the rest did not have an
> ifconfig.wmx file

No. You should not set an ip address on any of the interfaces. You create a 
bridge interface, connect all the physical interfaces to the bridge 
interface, and you set an ip address on the bridge interface.

	Johnny

>
> Derrick Lobo
> -----Original Message-----
> From: Johnny Billquist [mailto:bqt%update.uu.se@localhost]
> Sent: Wednesday, July 19, 2017 11:53 AM
> To: Derrick Lobo; Francisco Valladolid H.; netbsd-users%netbsd.org@localhost
> Subject: Re: creating a netbsd router
>
> I seriously doubt agr is what you wanted anyway.
> It's for if you want to have multiple parallell connections between
> two devices in order to increase capacity. Ie. aggregate link.
>
> A bridge is what you want if you have multiple connections locally,
> but you want them to all be associated with just one device locally,
> and they should also be able to communicate directly between two ports
> without your host being involved. Ie, a hub or a switch like function,
> with just one interface for your local machine, which works the same
> as any other port on the bridge. It's all like one ethernet segment.
>
> But you need to understand how you actually set it up to get it working.
> You should not be playing with the individual interfaces... Just add
> them all to the bridge interface, and then you use the bridge interface.
>
> 	Johnny
>
> On 2017-07-19 17:44, Derrick Lobo wrote:
>> Thanks Everyone
>>
>>
>>
>> Agr does not work because you have to remove all IPs from the
>> interface, before you add them.. and then theres no way to add an IP
>> to the agr. Eg
>> 192.168.0.1 I need this ip so that it becomes the LAN gateway for my
>> internal PCs.
>>
>>
>>
>> Im checking briding,  for now I could not get it to work will
>> investigate this further.
>>
>>
>>
>> Thanks again everyone
>>
>>
>>
>> Derrick
>>
>>
>>
>>
>>
>> *From:*Francisco Valladolid H. [mailto:ficovh%gmail.com@localhost]
>> *Sent:* Sunday, July 16, 2017 6:41 AM
>> *To:* Derrick Lobo; netbsd-users%netbsd.org@localhost
>> *Subject:* Re: creating a netbsd router
>>
>>
>>
>> Hi folks
>>
>>
>>
>> On Sat, Jul 15, 2017 at 4:06 AM Derrick Lobo <derrick.lobo%givex.com@localhost
>> <mailto:derrick.lobo%givex.com@localhost>> wrote:
>>
>>     I have a device with 8 network interface,so wondering if I can set
>>     this up as my router/switch
>>
>> Ok
>>
>>
>>
>>     I would like to create eth0 as the WAN interface and the remaining
>>     eth1-6 as the LAN interface so that I can connect multiple switches
>>     and devices directly on the 7 remaining ports.. is vlan, bridging
>>     the way to go .. linux uses bonding and im not sure if freebsds lagg
>>     is the same thing.. Anyone can provide information or link on how I
>>     can achieve this.
>>
>>
>>
>> Yes you can. You can use bridging, setting VLAN and agrégate
>> interfaces like Linux with the agr(4)
>>
>>
>>
>> http://man-k.org/man/NetBSD-current/4/agr?r=1&q=Agr
>>
>>
>>
>>
>>
>>     So eth0  would have a public Ip while the rest ports would have one
>>     LAN IP whichis basically a 192.168.0.1  ip  and Irun DHCP namedb etc
>>     on these interface to support my LAN.
>>
>>
>>
>> Yes, eth0 can be wan with the public IP and the rest can be LAN,
>> setting dhcp over any interfaz and setting a DNS cache.
>>
>>
>>
>> Please review the npf.conf manual for information about the firewall
>> program
>>
>>
>>
>> http://man-k.org/man/NetBSD-current/5/npf.conf?r=2&q=Npf.conf
>>
>>
>>
>>
>>
>> Bes regards.
>>
>>     Thanks
>>
>>     Derrick Lobo
>>
>> --
>>
>> Francisco Valladolid H.
>>  -- http://blog.bsdguy.net - Jesus Christ follower.
>>
>
>


-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol