Hi misc@,
I'm trying to achieve something similar to Cisco's firewall contexts or
Juniper's virtual systems with PF and OpenBSD.
Currently I run an OpenBSD box as a firewalling device for multiple
environments, most of them independent of each other. My main problem
with this arrangement is that
uot; rev 1.10/0.01 addr 2
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub3 port 1 configuration 1 interface 1 "ServerEngines SE USB
Device" rev 1.10/0.01 addr 2
uhidev1: iclass 3/1
ums0 at uhidev1: 8 buttons, Z dir
wsmouse0 at ums0 mux 0
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (dc15560267503288.a) swap on wd0b dump on wd0b
--
regards,
Wiesław Kielas
Administrator
Blue Media S.A.
www.bluemedia.pl <http://www.bluemedia.pl/>
h can do that?
--
regards,
Wiesław Kielas
* Wiesław Kielas [04.09.2013. @15:44:05 +0200]:
> Hi misc@,
>
> I have a Dell PowerEdge M600 machine running OpenBSD 5.3 which causes
> frequent problems - once about every few days vlan interfaces stop
> working.
>
> Ifconfig reports them being up the whole time, bu
switches, and
all machines using OpenBSD have ports configured in the exactly same way
on them - the port is in general mode, with vlan1 untagged and the rest
tagged - yet only one machine has the described earlier vlan problems.
> 2013/9/4 Wiesław Kielas
>
> > Hi misc@,
> >
>
3 report ids
ums1 at uhidev3 reportid 1: 5 buttons, Z dir
wsmouse1 at ums1 mux 0
uhid0 at uhidev3 reportid 2: input=2, output=0, feature=0
uhid1 at uhidev3 reportid 3: input=1, output=0, feature=0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (c12abee9ad63bcb9.a) swap on wd0b dump on wd0b
bnx0: address 00:22:19:87:00:31
brgphy0 at bnx0 phy 2: BCM5708S 1000/2500baseSX PHY, rev. 1
bnx1: address 00:22:19:87:00:33
brgphy1 at bnx1 phy 2: BCM5708S 1000/2500baseSX PHY, rev. 1
bnx2: address 00:1d:09:74:30:50
brgphy2 at bnx2 phy 2: BCM5708S 1000/2500baseSX PHY, rev. 1
bnx3: address 00:1d:09:74:30:52
brgphy3 at bnx3 phy 2: BCM5708S 1000/2500baseSX PHY, rev. 1
--
regards,
Wiesław Kielas
27;t match?
I guess this could create problems when one is deleting a large number of /32
aliases, mistakengly catching also the main /24 address.
--
regards,
Wiesław Kielas
g lifetimes?
If not, are there any downsides to reducing the key lifetime? What would be a
good value?
--
with regards,
Wiesław Kielas
8 matches
Mail list logo