Re: IPv4 & IPv6 CIDR subnet calculator

2019-09-27 Thread Magnus Wild
On Wed, Sep 25, 2019 at 02:43:55AM -0700, Mark Jamsek wrote:
>
> I’ve created a subnet calculator for both IPv4 and IPv6 written in C.
> 

I've tried it, and it seems to work well. Pretty handy tool!

Thanks for sharing!

/Magnus



Re: recent troubles with iwn(4)

2019-09-08 Thread Magnus Wild
On Sun, 2019-09-08 at 20:31 +, Bryan Stenson wrote:

> I'm running -CURRENT and the iwn(4) driver for my wireless
> card.  Over
> the past year, this has been working great, but recently (within the
> last month or so), I've had issues where the NIC just stops working
> after a few hours of usage.  I don't have a solid steps for
> reproduction.

> A simple "ifconfig iwn0 down; sh /etc/netstart iwn0" seems to fix the
> problem, but I haven't had to do that in the past...it just feels
> like
> a recent change (iwn(4) work?) has put me in this state.

Hello! I have no solution for your problem, but when I read your mail I
was pretty interested, because I've been having the same issue with
previous snapshots from the past year or so, but the other way around;
I've had issues on certain networks, for example the network in my
home, where I get disconnected or my connections times out frequently.

Sometimes it would require me to do the exact thing you are suggesting,
namely take down the interface with either a "ifconfig iwn0 down" or
sometimes also "ifconfig iwn0 delete" and then "sh /etc/netstart".
Other times it was just a matter of having to wait forever before I
could connect to the wireless at home. Or rather, wait to use it,
because almost anything timed out at first. Then after a while it
started working as expected.

This issue has completely gone away some time during the last few weeks
though, which I found relieving. My hardware is a Thinkpad x230 with
the following output from "pcidump -v":

3:0:0: Intel Centrino Advanced-N 6205
0x: Vendor ID: 8086, Product ID: 0085
0x0004: Command: 0006, Status: 0010
0x0008: Class: 02 Network, Subclass: 80 Miscellaneous,
Interface: 00, Revision: 34
0x000c: BIST: 00, Header Type: 00, Latency Timer: 00,
Cache Line Size: 10
0x0010: BAR mem 64bit addr: 0xf1c0/0x2000
0x0018: BAR empty ()
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 8086 Product ID: 1311
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
0x00c8: Capability 0x01: Power Management
State: D0
0x00d0: Capability 0x05: Message Signalled Interrupts (MSI)
Enabled: yes
0x00e0: Capability 0x10: PCI Express
Link Speed: 2.5 / 2.5 GT/s, Link Width: x1 / x1
0x0100: Enhanced Capability 0x01: Advanced Error Reporting
0x0140: Enhanced Capability 0x03: Device Serial Number
Serial Number: 6c8814daa8e4

I never bothered to report it, because I rarely use this particular
machine at home, and since I only had issues there I assumed that it
was some kind of issue with my AP.

/Magnus



Re: What is you motivational to use OpenBSD

2019-08-29 Thread Magnus Wild

On 8/28/19 4:32 PM, Mohamed salah wrote:

I wanna put something in discussion, what's your motivational to use
OPENBSD what not other bsd's what not gnu/Linux, if something doesn't work
fine on openbsd and you love this os so much what will do?



I enjoy using it because of it's clean design. It's a fairly simple 
system, with sane default configuration and it "just works" on most 
laptops that I've used it on.


I use a lot of Linux at work and in other environments as well, and the 
application support is naturally better. But the things I really care 
about works on OpenBSD, and as such, I tend to come back to it when 
using computers in my free time.