Re: disable fvwm screensaver?
On 07/12/18 18:34, Edgar Pettijohn III wrote: man xset I haven't used it to disable the screen saver, so I'm not sure the exact command. But you need something like: xset s off Hey Edgar, Thanks for help! 'xset s off && xset -dpms' seemed to do the trick. I popped it into my ~/.profile and am now off to the races! Cheers, Jordan
Re: Wireless on ThinkPad T40 - Connects but no data
On 12.7.2018 17:37, Richard Laysell wrote:
Hello,
I'm having a problem getting the wireless network to work on a ThinkPad
T40. The wireless seems to connect OK, but I can't get any packets
through it.
The device is ipw0 and it seems to be configured correctly as far as I
can see.
# cat /etc/hostname.ipw0
nwid anderella24
wpakey "password"
inet 192.168.28.79 255.255.255.0
Why no DHCP use here? Your AP is providing static IP configuration?
I have the 1.3 firmware installed
# fw_update -i
Installed: radeondrm-firmware-20170119 ipw-firmware-1.3p2
intel-firmware-20180312v0
The card reports as connected to the wireless
# ifconfig -a
lo0: flags=8049 mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
em0: flags=8802 mtu 1500
lladdr 00:16:41:a8:8d:8b
index 1 priority 0 llprio 3
media: Ethernet autoselect (none)
status: no carrier
ipw0: flags=8843 mtu 1500
lladdr 00:04:23:61:fe:6c
index 2 priority 4 llprio 3
groups: wlan egress
media: IEEE802.11 autoselect (DS11 mode 11b)
status: active
ieee80211: nwid anderella24 chan 13 bssid b0:39:56:4f:a9:14
-50dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher
ccmp
inet 192.168.28.79 netmask 0xff00 broadcast 192.168.28.255
enc0: flags=0<> index 3 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141 mtu 33172
index 5 priority 0 llprio 3
groups: pflog
Did you try with debug mode enabled on ipw0 to see if there is
something?
But when I try to ping an existing system using this interface, there
is no connection
You did not show 'netstat -rn' or 'route -n show' outputs
I have another laptop (running Linux) which is connected to the same
wireless AP and this can ping the existing system OK
The wireless AP is a Netgear WAC104 and this shows the card as
connected
Status Device Name BSSID SSIDType Radio MAC
Address Connection Type
Allowed Unknown B0:39:56:4F:A9:14 anderella24 WPA2-PSK 2.4G
00:04:23:61:FE:6C Wireless
Is anyone else using a similar network card and are they having any
problems?
Full dmesg below
OpenBSD 6.3 (GENERIC) #490: Sat Mar 24 14:31:33 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1500MHz ("GenuineIntel"
686-class) 1.50 GHz cpu0:
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2,PERF
real mem = 1072578560 (1022MB) avail mem = 1039097856 (990MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 02/27/06, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev.
2.33 @ 0xe0010 (61 entries) bios0: vendor IBM version "1RETDOWW
(3.20 )" date 02/27/2006 bios0: IBM 237342G
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT
acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4)
USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (PCI1)
acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7
acpitz0 at acpi0: critical temperature is 93 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"IBM0057" at acpi0 not configured
"IBM0071" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "IBM-08K8193" serial 21133 type LION oem
"SANYO" acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: DOCK not docked (0)
acpivideo0 at acpi0: VID_
bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000
0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: Enhanced SpeedStep 1496 MHz: speeds: 1500, 1400, 1200, 1000, 800,
600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xd000, size 0x1000
ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M7" rev 0x00
drm0 at radeondrm0
radeondrm0: irq 11
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 "Intel 82801BAM
Hub-to-PCI" rev 0x81 pci2 at ppb1 bus 2
2:0:0: mem address conflict 0xb000/0x1000
2:0:1: mem address conflict 0xb100/0x1000
cbb0 at pci2 dev 0 function 0 "TI PCI1520 CardBus" rev 0x01:
Re: disable fvwm screensaver?
On 07/12/18 20:19, Jordan Geoghegan wrote: Hello, Sorry for the noob question. I am having trouble disabling the screen saver / screen timeout for fvwm. I am using an OpenBSD machine as a video terminal for my CCTV system and need the screen to be on 24/7 so employees can see the camera playback. Unfortunately the screen blanks after a short time. I have done the RTFM dance, but I am feeling a little special right now-- I can't find any reference to screen timeout in the fvwm man page. How would one go about disabling the screen timeout on fvwm? Cheers, Jordan man xset I haven't used it to disable the screen saver, so I'm not sure the exact command. But you need something like: xset s off
disable fvwm screensaver?
Hello, Sorry for the noob question. I am having trouble disabling the screen saver / screen timeout for fvwm. I am using an OpenBSD machine as a video terminal for my CCTV system and need the screen to be on 24/7 so employees can see the camera playback. Unfortunately the screen blanks after a short time. I have done the RTFM dance, but I am feeling a little special right now-- I can't find any reference to screen timeout in the fvwm man page. How would one go about disabling the screen timeout on fvwm? Cheers, Jordan
Re: Wireless on ThinkPad T40 - Connects but no data
On Thu, Jul 12, 2018 at 06:57:43PM +, Mike Coddington wrote: > I've got a Thinkpad X220 and have experienced a similar issue. My > machine uses the iwn(4) driver, but I have also seen the same behavior > with a cheapo USB wireless dongle that I plug in. This is mainly useless > information, but here is what I am wondering: does this problem occur > for you when you connect to other access points? My connectivity issue only > crops up at my office's access point. Things work great at home and on > the bus. You may want to try and connect to some other public wifi networks > and see if the problem is the same for you. I also noticed that I could > *CONNECT* to the access point fine, but only ARPs would make it to my > machine. Maybe do some tcpdump work and see if your problem is similar. > > I haven't really spent a whole heck of a lot of time troubleshooting my > own problem because I can connect via a wired connection. However, > hopefully my experience gets you headed in the right direction. I get very poor signal on a ThinkPad X220. It works at max 3 meters away from the router. After that, almost 100% packet loss. The AP doesn't matter. However, it is not OpenBSD-related: https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/X220-wifi-very-poor-performance/td-p/484303 ThinkPad T420 works great with iwn(4). -- db
Re: Wireless on ThinkPad T40 - Connects but no data
On 2018年7月13日 0:37:27 JST, Richard Laysell wrote:
>
>Hello,
>
>I'm having a problem getting the wireless network to work on a ThinkPad
>T40. The wireless seems to connect OK, but I can't get any packets
>through it.
>
>The device is ipw0 and it seems to be configured correctly as far as I
>can see.
>
># cat /etc/hostname.ipw0
>nwid anderella24
>wpakey "password"
>inet 192.168.28.79 255.255.255.0
>
>I have the 1.3 firmware installed
># fw_update -i
>Installed: radeondrm-firmware-20170119 ipw-firmware-1.3p2
>intel-firmware-20180312v0
>
>The card reports as connected to the wireless
># ifconfig -a
>lo0: flags=8049 mtu 32768
> index 4 priority 0 llprio 3
> groups: lo
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
> inet 127.0.0.1 netmask 0xff00
>em0: flags=8802 mtu 1500
> lladdr 00:16:41:a8:8d:8b
> index 1 priority 0 llprio 3
> media: Ethernet autoselect (none)
> status: no carrier
>ipw0: flags=8843 mtu 1500
> lladdr 00:04:23:61:fe:6c
> index 2 priority 4 llprio 3
> groups: wlan egress
> media: IEEE802.11 autoselect (DS11 mode 11b)
> status: active
> ieee80211: nwid anderella24 chan 13 bssid b0:39:56:4f:a9:14
>-50dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher
>ccmp
>inet 192.168.28.79 netmask 0xff00 broadcast 192.168.28.255
>enc0: flags=0<> index 3 priority 0 llprio 3
> groups: enc
> status: active
>pflog0: flags=141 mtu 33172
> index 5 priority 0 llprio 3
> groups: pflog
>
>But when I try to ping an existing system using this interface, there
>is no connection
>
>I have another laptop (running Linux) which is connected to the same
>wireless AP and this can ping the existing system OK
>
>The wireless AP is a Netgear WAC104 and this shows the card as
>connected
>Status Device Name BSSID SSIDType Radio MAC
>Address Connection Type
>Allowed Unknown B0:39:56:4F:A9:14 anderella24 WPA2-PSK 2.4G
>00:04:23:61:FE:6C Wireless
>
>Is anyone else using a similar network card and are they having any
>problems?
>
>Full dmesg below
>OpenBSD 6.3 (GENERIC) #490: Sat Mar 24 14:31:33 MDT 2018
>dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>cpu0: Intel(R) Pentium(R) M processor 1500MHz ("GenuineIntel"
>686-class) 1.50 GHz cpu0:
>FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2,PERF
>real mem = 1072578560 (1022MB) avail mem = 1039097856 (990MB)
>mpath0 at root
>scsibus0 at mpath0: 256 targets
>mainbus0 at root
>bios0 at mainbus0: date 02/27/06, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev.
>2.33 @ 0xe0010 (61 entries) bios0: vendor IBM version "1RETDOWW
>(3.20 )" date 02/27/2006 bios0: IBM 237342G
>acpi0 at bios0: rev 2
>acpi0: sleep states S0 S3 S4 S5
>acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT
>acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4)
>USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits
>acpiec0 at acpi0
>acpiprt0 at acpi0: bus 0 (PCI0)
>acpiprt1 at acpi0: bus 1 (AGP_)
>acpiprt2 at acpi0: bus 2 (PCI1)
>acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7
>acpitz0 at acpi0: critical temperature is 93 degC
>acpibtn0 at acpi0: LID_
>acpibtn1 at acpi0: SLPB
>"IBM0057" at acpi0 not configured
>"IBM0071" at acpi0 not configured
>acpibat0 at acpi0: BAT0 model "IBM-08K8193" serial 21133 type LION oem
>"SANYO" acpiac0 at acpi0: AC unit online
>acpithinkpad0 at acpi0
>acpidock0 at acpi0: DOCK not docked (0)
>acpivideo0 at acpi0: VID_
>bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000
>0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor)
>mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
>cpu0: Enhanced SpeedStep 1496 MHz: speeds: 1500, 1400, 1200, 1000, 800,
>600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
>intelagp0 at pchb0
>agp0 at intelagp0: aperture at 0xd000, size 0x1000
>ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
>pci1 at ppb0 bus 1
>radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M7" rev 0x00
>drm0 at radeondrm0
>radeondrm0: irq 11
>uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
>uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
>uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
>ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
>usb0 at ehci0: USB revision 2.0
>uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
>2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 "Intel 82801BAM
>Hub-to-PCI" rev 0x81 pci2 at ppb1 bus 2
>2:0:0: mem address conflict 0xb000/0x1000
>2:0:1: mem address conflict 0xb100/0x1000
>cbb0 at pci2 dev 0 function 0 "TI PCI1520 CardBus" rev 0x01: irq 11
>cbb1 at pci2 dev 0 function 1 "TI PCI1520 CardBus" rev 0x01: irq 11
>em0 at pci2 dev 1 function
Re: Wireless on ThinkPad T40 - Connects but no data
On Thu, Jul 12, 2018 at 04:37:27PM +0100, Richard Laysell wrote: > > Hello, > > I'm having a problem getting the wireless network to work on a ThinkPad > T40. The wireless seems to connect OK, but I can't get any packets > through it. > > Is anyone else using a similar network card and are they having any > problems? I've got a Thinkpad X220 and have experienced a similar issue. My machine uses the iwn(4) driver, but I have also seen the same behavior with a cheapo USB wireless dongle that I plug in. This is mainly useless information, but here is what I am wondering: does this problem occur for you when you connect to other access points? My connectivity issue only crops up at my office's access point. Things work great at home and on the bus. You may want to try and connect to some other public wifi networks and see if the problem is the same for you. I also noticed that I could *CONNECT* to the access point fine, but only ARPs would make it to my machine. Maybe do some tcpdump work and see if your problem is similar. I haven't really spent a whole heck of a lot of time troubleshooting my own problem because I can connect via a wired connection. However, hopefully my experience gets you headed in the right direction. -- Put your Nose to the Grindstone! -- Amalgamated Plastic Surgeons and Toolmakers, Ltd.
Wireless on ThinkPad T40 - Connects but no data
Hello,
I'm having a problem getting the wireless network to work on a ThinkPad
T40. The wireless seems to connect OK, but I can't get any packets
through it.
The device is ipw0 and it seems to be configured correctly as far as I
can see.
# cat /etc/hostname.ipw0
nwid anderella24
wpakey "password"
inet 192.168.28.79 255.255.255.0
I have the 1.3 firmware installed
# fw_update -i
Installed: radeondrm-firmware-20170119 ipw-firmware-1.3p2
intel-firmware-20180312v0
The card reports as connected to the wireless
# ifconfig -a
lo0: flags=8049 mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
em0: flags=8802 mtu 1500
lladdr 00:16:41:a8:8d:8b
index 1 priority 0 llprio 3
media: Ethernet autoselect (none)
status: no carrier
ipw0: flags=8843 mtu 1500
lladdr 00:04:23:61:fe:6c
index 2 priority 4 llprio 3
groups: wlan egress
media: IEEE802.11 autoselect (DS11 mode 11b)
status: active
ieee80211: nwid anderella24 chan 13 bssid b0:39:56:4f:a9:14
-50dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher
ccmp
inet 192.168.28.79 netmask 0xff00 broadcast 192.168.28.255
enc0: flags=0<> index 3 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141 mtu 33172
index 5 priority 0 llprio 3
groups: pflog
But when I try to ping an existing system using this interface, there
is no connection
I have another laptop (running Linux) which is connected to the same
wireless AP and this can ping the existing system OK
The wireless AP is a Netgear WAC104 and this shows the card as connected
Status Device Name BSSID SSIDType Radio MAC Address
Connection Type
Allowed Unknown B0:39:56:4F:A9:14 anderella24 WPA2-PSK 2.4G
00:04:23:61:FE:6C Wireless
Is anyone else using a similar network card and are they having any
problems?
Full dmesg below
OpenBSD 6.3 (GENERIC) #490: Sat Mar 24 14:31:33 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1500MHz ("GenuineIntel"
686-class) 1.50 GHz cpu0:
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2,PERF
real mem = 1072578560 (1022MB) avail mem = 1039097856 (990MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 02/27/06, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev.
2.33 @ 0xe0010 (61 entries) bios0: vendor IBM version "1RETDOWW
(3.20 )" date 02/27/2006 bios0: IBM 237342G
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT
acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4)
USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (PCI1)
acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7
acpitz0 at acpi0: critical temperature is 93 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"IBM0057" at acpi0 not configured
"IBM0071" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "IBM-08K8193" serial 21133 type LION oem
"SANYO" acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
acpidock0 at acpi0: DOCK not docked (0)
acpivideo0 at acpi0: VID_
bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000
0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: Enhanced SpeedStep 1496 MHz: speeds: 1500, 1400, 1200, 1000, 800,
600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82855PM Host" rev 0x03
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xd000, size 0x1000
ppb0 at pci0 dev 1 function 0 "Intel 82855PM AGP" rev 0x03
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility M7" rev 0x00
drm0 at radeondrm0
radeondrm0: irq 11
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 "Intel 82801BAM
Hub-to-PCI" rev 0x81 pci2 at ppb1 bus 2
2:0:0: mem address conflict 0xb000/0x1000
2:0:1: mem address conflict 0xb100/0x1000
cbb0 at pci2 dev 0 function 0 "TI PCI1520 CardBus" rev 0x01: irq 11
cbb1 at pci2 dev 0 function 1 "TI PCI1520 CardBus" rev 0x01: irq 11
em0 at pci2 dev 1 function 0 "Intel 82540EP" rev 0x03: irq 11, address
00:16:41:a8:8d:8b ipw0 at pci2 dev 2 function 0 "Intel PRO/Wireless
2100" rev 0x04: irq 11, address 00:04:23:61
Re: Weird routing problem on simple CARP setup
That makes sense. Thanks for your advices. -- Cordialement, Pierre BARDOU -Message d'origine- De : Stuart Henderson Envoyé : mercredi 11 juillet 2018 23:24 À : misc@openbsd.org Objet : Re: Weird routing problem on simple CARP setup On 2018-07-11, Tom Smyth wrote: > Hi Pierre, > > with VRRP on other vendors the IP on the Virtual interface is > recommended to be a /32, > > > afaik > it prevents ambiguity when it comes to your connected routes do you > route a packet out the carp interface which as an ip on the configured > /24 network or do you route the packet out the physcial interface > which also has a /24 network configured > > > I note the examples and faq page in openbsd show ips configured with > a /24 configured https://man.openbsd.org/carp > > and a /24 seems to be the default ip if a subnet mask is not specified > > > But I would love to hear / learn more experienced OpenBSD Admins Devs > take on it My GBP0.02 (which isn't worth much these days ;) - generally /32 for addresses on carp - if there are no IPs from the subnet used in carp on another "real" interface (i.e. the address is only on the carp interface) then use the full /XX for one IP in that subnet on carp - if you're redistributing a subnet on a carp interface into OSPF you need the full /XX on the carp interface so it can announce the network rather than a single host (you want to announce it from carp rather than the "real" interface so the priority changes depending on the carp state)
Re: ISDN Card /PRI Card support on OpenBSD
Wed, 11 Jul 2018 21:15:59 + (UTC) Stuart Henderson > On 2018-07-11, Tom Smyth wrote: > > Hello all, > > > > this is an odd one but I have a client that needs to > > migrate some legacy services > > Is there support for ISDN type interfaces in OpenBSD ? > > > > man / apropos shows nothing > > > > or is there a package that would add ISDN support > > (although I didnt see a package containing isdn or ISDN > > in packages) > > is ISDN support available under a different name by any chance > > > > Thanks > > > > Tom Smyth > > > > > > ISDN covers various things, data/voice, and various types of line > (BRI = 2 64k data/voice "B" channels plus one signalling "D" channel .. > PRI = up to 30 B channels over an E1/T1 circuit). Hi Tom, Mandatory reference material to restore retro knowledge where applicable. Integrated Services Digital Network (elements) https://en.wikipedia.org/wiki/Isdn#ISDN_elements BRI (2B+D) https://en.wikipedia.org/wiki/Basic_Rate_Interface PRI (30B+2D) https://en.wikipedia.org/wiki/Primary_Rate_Interface > Would need more information about what the "legacy services" are before > it's possible to make any kind of suggestion (but apart from some data > services on BRI which might work with an async TA, it's not really going > to involve OpenBSD in directly terminating the ISDN). There are both external and internal modems for BRI ISDN, with similar to the analogue (ISDN is digital) modem caveats. External modems use HAYES, https://en.wikipedia.org/wiki/Hayes_command_set#The_basic_Hayes_command_set command set (AT commands) and can do bonding at ISDN level so you get the 128 kbps as advertised when using both B channels. I've successfully did a number of deployments using Zyxel external modems which could be bought in stores as CPE (Client Premises Equipment) just as the other modems but at a considerably higher cost. The nice part of the ISDN setup were that you could pick up the phone and the modem would go single channel auto as the D line for signalling handles these, and you can get a micro ISDN PBX setup with the 2 lines for up to 8 phone lines of the "cheapest" models.. There are also internal cards, Fritz! AVM is one notable brand of devices AVM (BRI ISDN PCI cards) https://en.wikipedia.org/wiki/AVM_GmbH#Products both hardware and software based sets (the soft WOULDN'T work) which were possible to get to work yet very unreliable. As for the PRI ISDN, I have done only a couple of deployments for considerably high costs (300 EU/mo) local fees + activation (2x) and it is terminated by the TELCO as E1 line 2048 kbps most typically as HDSL2E1 termination for PBX E1/PRI interfaces so this provided 30 incoming and outgoing concurrent digital phone lines. You'll probably never have the chance to use PRI these days as faster and newer less complicated (and expensive) subscriber lines do the last mile. The time frame this got obsoleted is 2005 here in the SE EU with the mass avail of inexpensive ADSL broadband for the general population all towns. The most looked after feature was the synchronous data line rates for BRI and the almost instantaneous dial (digital signalling) connection set up, which I was typically configuring as dial-on-demand (at the gateway PC).. In Germany (where I worked at the time) ISDN lines were also used as ADSL due to the reliable and fast operation (digital lines) and similar costs. As a closing line (pun intended) the ISDN is considered obsolete in 2018. Kind regards, Anton Lazarov
