Hi, finally, I following to https://wiki.debian.org/NetworkConfiguration,
make both openbsd and debian support vlan, then I can ping/connect both side
now.
Thanks.
On 2019年1月29日 09:53:07 [GMT+08:00], johnw wrote:
>Hi, thank you first, and I think I totally misunderstand vlan.
>
>I want create vl
Hi, thank you first, and I think I totally misunderstand vlan.
I want create vlan network, because minidlna / wifi.
My openbsd system have 4nics(em0-3), and em2 is connected a wifi
rounter(tplink), which already setup as bridge,
and the wifi client(sony tv/mobile) can request dhcp/ip from open
This works for me:
$cat /etc/hostname.vr1
up
$cat /etc/hostname.vlan2
inet 10.0.2.254 255.255.255.0 NONE vlan 2 vlandev vr1
$cat /etc/hostname.vlan100
inet 10.0.100.254 255.255.255.0 NONE vlan 100 vlandev vr1
OpenBSD 6.3 (GENERIC) #3: Thu Dec 20 09:35:15 MST 2018
t...@syspatch-63-i386.openbs
On 2019-01-28, Josh Grosse wrote:
> On Mon, Jan 28, 2019 at 07:57:01PM +0800, johnw wrote:
>> hi, I want create vlan network
>
> vlan(4) **REQUIRES** switching equipment that supports
> 802.1Q Ethernet tagging. These are known as "managed
> switches".
>
>
At the risk of adding confusion, but
On 2019-01-28, johnw wrote:
> hi, I want create vlan network, I create two files
>
> hostname.vio0
> up
>
> hostname.vlan0
> inet 10.10.10.101 255.255.255.0 10.10.10.255 parent vio0 vnetid 10
>
> then reboot
>
> I can not ping 10.10.10.1
>
> If I create bridge0, and add vio0 and vlan0 to bridge0,
On Mon, Jan 28, 2019 at 07:57:01PM +0800, johnw wrote:
> hi, I want create vlan network
vlan(4) **REQUIRES** switching equipment that supports
802.1Q Ethernet tagging. These are known as "managed
switches".
My system is:
OpenBSD 6.4-current (GENERIC.MP) #639: Sun Jan 27 14:27:05 MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Thanks.
On 2019年1月28日 19:57:01 [GMT+08:00], johnw wrote:
>hi, I want create vlan network, I create two files
>
>hostname.vio0
>up
>
>hostname.v
hi, I want create vlan network, I create two files
hostname.vio0
up
hostname.vlan0
inet 10.10.10.101 255.255.255.0 10.10.10.255 parent vio0 vnetid 10
then reboot
I can not ping 10.10.10.1
If I create bridge0, and add vio0 and vlan0 to bridge0, then I can ping
10.10.10.1
Or if I just use vio0
On Tue, Sep 24, 2013 at 9:57 PM, Henning Brauer wrote:
> * Daniel Gillen [2013-09-24 17:36]:
> > After some debugging with tcpdump, I found out that from 5.0 to 5.1,
> > OpenBSD introduced vlan priorisation support (IEEE 802.1p) and per
> > default sets the vlan PCP field to the value 3.
> >
> >
* Daniel Gillen [2013-09-24 17:36]:
> After some debugging with tcpdump, I found out that from 5.0 to 5.1,
> OpenBSD introduced vlan priorisation support (IEEE 802.1p) and per
> default sets the vlan PCP field to the value 3.
>
> Unfortunately, my ISP only allows connections when this field is se
Hi list
I recently upgraded my firewall from OpenBSD 5.0 to 5.3 (i386).
Unfortunately, after the upgrade process, my pppoe connection to my ISP
didn't work anymore.
I'm using kernel pppoe with the following setup:
/etc/hostname.xl1:
up
/etc/hostname.vlan0:
vlan 35 vlandev xl1 up
/etc/hostn
Is possible
You need to specify the netmask of your vlan interfaces
cat out one of your hostname.vlan?? and show us
one of mine looks like
inet 10.120.6.102 255.255.255.0 NONE vlan 6 vlandev em0
On 1/26/09 10:42 AM, Denis Souza wrote:
Friends,
I'm using OpenBSD 4.1 with a VLAN with 2 IPs
Friends,
I'm using OpenBSD 4.1 with a VLAN with 2 IPs only (Netmask
30bits-255.255.255.252), but the SO is classfull, creating a link line in my
router table:
# netstat -rn
...
172.16/16 link#12
UC 10 - vlan1
...
But in my project the subnet
172.16.0.0
13 matches
Mail list logo