I have always used the Router's global address when configuring a static
route or static default gateway.
I have seen routing protocols like OSPF/BGP/etc. use link-local addresses
for nexthop, but when statically configuring,
I've always used the global address that is located within the same
On Tue, Jun 26, 2018 at 7:05 PM Edgar Pettijohn III
wrote:
>
>
>
> On 06/26/18 13:50, Raul Miller wrote:
> > Personally, I can't totally figure out what this policy would be.
> >
> > My current best approximation is: there's a period of time when
> > pkg_add and syspatch are running and that is a
Hello misc,
I am wondering whether the good volks here would be able to share
their insight on configuring the IPv6 gateway address for a machine
which has been assigned a static IPv6 address.
Based on my layman research, there are two options:
1) Link local gateway address - fe80::1%em0
On Wed, Jul 18, 2018 at 04:27:45PM +0200, Jan Stary wrote:
> This is 6.3-current on and amd64 PC (dmesg below), using
>
> re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL
> (0x2c80), msi, address 50:e5:49:36:ec:0d
>
> as the NIC. With a hostname.re0 that says
>
>
On 2018-07-18, Adonis Peralta wrote:
> At the same time it seems that the documentation on em(4) is incorrect for
> stating i350 supports offloading currently.
Yes, I think this is just a manpage omission at this point. Because the
driver *explicitly* disables offload for this chip it's pretty
At the same time it seems that the documentation on em(4) is incorrect for
stating i350 supports offloading currently.
—
Adonis
>>> On Jul 18, 2018, at 6:58 AM, Kim Zeitler wrote:
>>>
>>> On 07/18/18 11:37, Adonis Peralta wrote:
>>> Will definitely do that, but still looking for any
On Jul 17, 2018 6:57 PM, Andrew wrote:
>
> On 07/17/18 17:53, Edgar Pettijohn III wrote:
> >For some reason xconsole has decided to start seg faulting regularly.
> >I can't remember how to build X with debugging symbols. Could anyone
> >give me a quick rundown so I can provide more
Hello Peter,
On Wed, 2018-07-18 at 12:40 +, Steiner Peter wrote:
> Hello folks,
>
> we are currently looking for new server hardware compatible with
> OpenBSD 6.3 amd64.
> I couldn't find a compatibility list for current systems.
>
> We'd like to use Skylake based XEONs (e.g. Xeon Silver
You may always apply to the UN: they just require a high-school degree, english
and a second language like spanish or french, a first ITIL certificate, working
knowledge of windows xp and office, ibm lotus notes (they are big on wasting
charity funds on Microsoft and Lotus licenses), and a
Hello folks,
we are currently looking for new server hardware compatible with OpenBSD 6.3
amd64.
I couldn't find a compatibility list for current systems.
We'd like to use Skylake based XEONs (e.g. Xeon Silver 4108) in current dual
(or single) socket systems
like "Dell PowerR640", "Fujitsu
The name of the game is to select the best candidate, not to hire the average
joe.
On Mon, Jul 16, 2018 at 05:02, Jacqueline Jolicoeur wrote:
>> Spot the candidate that is aware of common standards, is brave enough to
>> come forward saying that the test is flowed (we ask to write /var stuff
Hi Marcus,
On Wed, 2018-07-18 at 18:19 +0200, Marcus MERIGHI wrote:
> codeb...@inbox.lv (John Long), 2018.07.18 (Wed) 13:51 (CEST):
> > I have minidlna working fine on OpenBSD. However this doens't help
> > with
> > Roon media software since they don't have anything for OpenBSD,
> >
codeb...@inbox.lv (John Long), 2018.07.18 (Wed) 13:51 (CEST):
> I have minidlna working fine on OpenBSD. However this doens't help with
> Roon media software since they don't have anything for OpenBSD,
> unsurprisingly. Roon doesn't want to support dlna.
What network access is officially
I have Samba/OpenBSD server at university's labs (VLANs, ~100
workstations[win7, win10], ~1k users).
There are few readonly shares that are automatically mounted at windows'
startup. Users can mount/umount their /homes by "net use..." script
(user/pass). They can also access their files over
On Wed, 2018-07-18 at 16:57 +0100, Tom Smyth wrote:
> Hi John,
>
> I would just follow the SAMBA documentation in setting up the share,
> /shared folders,
>
> then on the windows clients you may have to tweak the security
> settings
> in the local security policy manager, (but windows out
Hi John,
I would just follow the SAMBA documentation in setting up the share,
/shared folders,
then on the windows clients you may have to tweak the security settings
in the local security policy manager, (but windows out of the box for
domestic
settings) if your windows boxes are controlled
On Wed, Jul 18, 2018 at 04:27:45PM +0200, Jan Stary wrote:
> This is 6.3-current on and amd64 PC (dmesg below), using
>
> re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL
> (0x2c80), msi, address 50:e5:49:36:ec:0d
>
> as the NIC. With a hostname.re0 that says
>
>
@tom @solene
Thanks guys. I'll look into Samba. I hope it won't turn out to be a
typical Windows nightmare.
Are there any reliable setup guides on the net?
I will basically want to just make a couple of directory trees
available read-only.
Thanks,
/jl
On Wed, Jul 18, 2018 at 04:27:45PM +0200, Jan Stary wrote:
> This is 6.3-current on and amd64 PC (dmesg below), using
>
> re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL
> (0x2c80), msi, address 50:e5:49:36:ec:0d
>
> as the NIC. With a hostname.re0 that says
>
>
Hi John,
You would need microsoft services for unix (SFU) for NFS connectivity
I would try SAMBA first, if it was my choice,
be aware that you may have to change some
SMB Signing and NTLM Authentication setings in
local policies / security policy/ Security options/ in microsoft gpedit.msc
This is 6.3-current on and amd64 PC (dmesg below), using
re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL
(0x2c80), msi, address 50:e5:49:36:ec:0d
as the NIC. With a hostname.re0 that says
inet 192.168.11.3 255.255.255.0
it gets configured fine, but only uses
John Long writes:
> Hi,
>
> I have minidlna working fine on OpenBSD. However this doens't help with
> Roon media software since they don't have anything for OpenBSD,
> unsurprisingly. Roon doesn't want to support dlna.
>
> I have my Windows foobar2000 appliance roped-off from my LAN because I
>
Hi,
I have minidlna working fine on OpenBSD. However this doens't help with
Roon media software since they don't have anything for OpenBSD,
unsurprisingly. Roon doesn't want to support dlna.
I have my Windows foobar2000 appliance roped-off from my LAN because I
don't trust Windows boxes on my
On 07/18/18 11:37, Adonis Peralta wrote:
Will definitely do that, but still looking for any explanation from devs :).
https://marc.info/?l=openbsd-tech=135203532704213=2
Seems there have been some errors with offloading and I350 in the past
Cheers
Kim
smime.p7s
Description: S/MIME
Will definitely do that, but still looking for any explanation from devs :).
--
Adonis
> On Jul 18, 2018, at 5:28 AM, LÉVAI Dániel wrote:
>
> Adonis Peralta @ 2018-07-18T10:49:57 +0200:
>>> Maybe this is the culprit?
>>>
>>> /usr/src/sys/dev/pci/if_em.c:
>>> 1893 if (sc->hw.mac_type
Adonis Peralta @ 2018-07-18T10:49:57 +0200:
> > Maybe this is the culprit?
> >
> > /usr/src/sys/dev/pci/if_em.c:
> > 1893 if (sc->hw.mac_type >= em_82543 && sc->hw.mac_type !=
> > em_82575 &&
> > 1894 sc->hw.mac_type != em_82580 && sc->hw.mac_type !=
> > em_i210 &&
> > 1895
Exactly! This is a really really nice card and I don’t get why OpenBSD
doesn’t support the offloading features just as you’ve shown for bge
and re0. Definitely awaiting a response from the devs on this.
--
Adonis
On Jul 18, 2018, at 4:34 AM, LÉVAI Dániel wrote:
LÉVAI Dániel @
LÉVAI Dániel @ 2018-07-18T09:20:15 +0200:
> Adonis Peralta @ 2018-07-18T03:47:43 +0200:
> > Hi,
> >
[...]
> > ifconfig on my lan port shows:
> >
> > ```
> > em2: flags=8843 mtu 1500
> > hwfeatures=10 hardmtu 9216
> > lladdr 00:19:99:d7:88:a3
> > index 3 priority 0 llprio
Adonis Peralta @ 2018-07-18T03:47:43 +0200:
> Hi,
>
> I am running OpenBSD 6.3 with a PCI-Express Intel i350T4 Network card. The
> card is detected with the em(4) driver but upon looking at the hwfeatures
> with ifconfig I notice that none of the offloading features the card
> supports are
During g2k18 I commited rad(8).
The latest amd64 and i386 snapshots should contain it with enough
features to replace rtadvd(8). If you are using rtadvd(8) I'd
appreciate if you could switch to rad(8) and report back if any
features are missing.
The plan is to unhook rtadvd(8) from the build
30 matches
Mail list logo
