Re: Postscript printer recommendations
On 7/16/19 11:03 AM, Jonathan Drews wrote: On Tue, Jul 16, 2019 at 10:36:03AM -0700, BSD user wrote: On 7/16/19 4:13 AM, Jonathan Drews wrote: On Tue, Jul 16, 2019 at 08:06:20AM +, Roderick wrote: At this point, I am going to look for another printer that is more OpenBSD friendly. My Desjet 6940 is pretty old and the cartridges cost a lot (> USD $120.00) Kind regards, Jonathan I may just be a luddite, but after wasting multiple days messing around with cups, ghostscript, hplip et al, I decided it was just easier to print everything via postscript. . . . This solution doesn't offer the convenience of automagically converting arbitrary file formats to PCL or whatever the printer format of the day is, but it works for me without having to have add a ridiculous number of packages and configs. Thanks Roderick: I got to this instruction in the CUPS Readme: *** WARNING *** ulpt(4) needs to be disabled in the kernel (see config(8)) or the printer will not be available to libusb. I read the manpage for config (8) and I can't seem to find the appropriate configuration file in /usr/src/sys/arch/amd64/compile. I'll have to read up on compiling the kernel and modifying it's configuration file. Once again thanks for all the generous help form you guys. Regards, Jonathan I think you can temporarily disable ulpt via ukc, but I can't confirm as I'm currently travelling. As sthen@ said (IIRC) earlier in the thread, if your printer has networking (ethernet or wifi) support, it's usually easiest to just print over the network as it saves having to mess with kernel configs and device node permissions. Because I don't trust printers and their ancient firmware and "cloud" features, I threw my printer on an isolated VLAN with a firewall rule set in my router to block any outgoing internet traffic from the printer. Cheers
Re: Postscript printer recommendations
On 7/16/19 4:13 AM, Jonathan Drews wrote: On Tue, Jul 16, 2019 at 08:06:20AM +, Roderick wrote: At this point, I am going to look for another printer that is more OpenBSD friendly. My Desjet 6940 is pretty old and the cartridges cost a lot (> USD $120.00) Kind regards, Jonathan I may just be a luddite, but after wasting multiple days messing around with cups, ghostscript, hplip et al, I decided it was just easier to print everything via postscript. My printing "workflow" is quite rudimentary, but it has yet to fail me. I set up a simple lpd server on my desktop pointing to my Brother printer, from which I can print raw .txt, pdf or postscript files directly via lpr/lpd. If I find myself needing to print a file that isn't in one of these formats, I simply convert them to that format manually. If I need to print a .doc or .odt file, I just open them in LibreOffice and export them to pdf, which can then be printed via lpr. (As an aside, LibreOffice supports rendering pages to postscript and printing them directly as it seems to detect my lpd setup and offers "Generic Printer" as an option, allowing me to print directly from within LibreOffice.) This solution doesn't offer the convenience of automagically converting arbitrary file formats to PCL or whatever the printer format of the day is, but it works for me without having to have add a ridiculous number of packages and configs.
Re: Moving from Bird to OpenBGPD
On 7/14/19 11:24 PM, Claudio Jeker wrote:
On Sun, Jul 14, 2019 at 07:28:29PM -0700, BSD user wrote:
On 7/14/19 12:52 AM, Denis Fondras wrote:
On Sat, Jul 13, 2019 at 09:44:28PM -0700, BSD user wrote:
Hello,
My apologies for sending this email multiple times.
I was so mortified by Tutanota's awful text formatting that I
created a new mail account that supported IMAP so that I could load
it up in Thunderbird with text only mode enabled.
Once again, my apologies for my rookie mistake choosing Tutanota for
use on an international mailing list such as this one. I hope you
guys will give me one more chance.
My (hopefully) unmangled message is below.
You did not include which version you are running, I'll assume this is
6.5. It seems you do not have any filter, OpenBGPD denies everything
by default.
Thanks for the reply Denis. You were right, I was missing my allow
rules. After setting "allow from any AS 64515" and "allow to any" rules,
everything started working. I was able to get IPv6 working as well
without a hitch.
Are there any other filter rules I should be setting to secure my BGP
deployment? I'm on a private ASN assigned to me by Vultr. This is my
first forray into BGP land, so any advice or tips would be much
appreciated.
Ideally you want to limit the filters to only announce what you really
need to announce to prevent leaking of prefixes because of a
missconfiguration. Also what is Vultr sending you via BGP? Depending on
that you may be able to limit the input as well.
I guess in this simple setup it does not matter to have simple allow
filters since this bgpd instance is not connected to the default free zone
and so there is less risk of leaking or receiving leaked routes. In
general if your BGP setup has more than one external neighbor you need to
take care of your filters to make sure that you don't leak updates from
one neighbor to the other.
Thanks for the reply Claudio!
You were right, my "allow from" rule was unnecessary, Vultr doesn't
appear to be sending me anything.
I managed to get my "allow to" rule tightened up to look like this:
allow to any prefix {xxx.xxx.xxx.141/32 2001:::::/64}
I tried tightening the rule down further to restrict to Vultr's upstream
AS and IP addresses like so:
'allow to 169.254.169.254 AS 64515 prefix 140.82.0.141/32'
Unfortunately the rule doesn't work properly as my prefixes immediately
become unpingable after loading that rule. I'm probably missing
something obvious. Any suggestions on how to tighten down the rule further?
My final question is concerning assigning prefixes to interfaces. Is it
best practice to assign the addresses to something like 'lo1' loopback
interface, or should assigning it as an alias on an egress interface
suffice? I tried and they both seem to work.
Thanks
Re: Moving from Bird to OpenBGPD
On 7/14/19 12:38 PM, Rudy Baker wrote: It's sad how hostile this mailing list is that you need to beg forgiveness for using a different email client because you may have triggered some of these people. 🙄 I'm not too concerned. I'm grateful for the fact that the OpenBSD community has high standards. Upon reading my message on marc.info, I my self was irritated by the poor formatting. I appreciate that Ingo contacted my privately and informed me that tutanota was mangling my mail. Upon realizing this, I rectified the issue, as it's a matter of etiquette-- I'm already asking strangers to take time out of their day to assist me, the least I can do is make it easy for them to understand my request.
Re: Moving from Bird to OpenBGPD
On 7/14/19 12:52 AM, Denis Fondras wrote: On Sat, Jul 13, 2019 at 09:44:28PM -0700, BSD user wrote: Hello, My apologies for sending this email multiple times. I was so mortified by Tutanota's awful text formatting that I created a new mail account that supported IMAP so that I could load it up in Thunderbird with text only mode enabled. Once again, my apologies for my rookie mistake choosing Tutanota for use on an international mailing list such as this one. I hope you guys will give me one more chance. My (hopefully) unmangled message is below. You did not include which version you are running, I'll assume this is 6.5. It seems you do not have any filter, OpenBGPD denies everything by default. Thanks for the reply Denis. You were right, I was missing my allow rules. After setting "allow from any AS 64515" and "allow to any" rules, everything started working. I was able to get IPv6 working as well without a hitch. Are there any other filter rules I should be setting to secure my BGP deployment? I'm on a private ASN assigned to me by Vultr. This is my first forray into BGP land, so any advice or tips would be much appreciated. Cheers
Moving from Bird to OpenBGPD
Hello,
My apologies for sending this email multiple times.
I was so mortified by Tutanota's awful text formatting that I created a
new mail account that supported IMAP so that I could load it up in
Thunderbird with text only mode enabled.
Once again, my apologies for my rookie mistake choosing Tutanota for use
on an international mailing list such as this one. I hope you guys will
give me one more chance.
My (hopefully) unmangled message is below.
--
Hello,
I’m having some trouble configuring OpenBGPD to replace my Bird deployment.
I’m trying to set up redundant web infrastructure for a few websites I
host with Vultr. To do so, I followed this guide:
https://www.vultr.com/docs/high-availability-on-vultr-with-floating-ip-and-bgp
It works flawlessly with Bird running on OpenBSD, but I obviously prefer
to run utilities from the base system wherever possible. I’ve spent more
time than I’d like to admit trying to get this setup working on OpenBGPD.
The only thing I did different from the above guide was use lo1 rather
than a dummy interface, as dummy interfaces appear to be a linuxism as
per this mailing list thread I found:
http://openbsd-archive.7691.n7.nabble.com/Dummy-Interface-In-OpenBGPd-td34009.html
Basically, all I’m trying to do is port my Bird config over to OpenBGPD.
At this point I’m just banging my head against a wall. I’ve spent
several days googling, reading man pages and trying different configs. I
must be missing something basic, and it’s likely something obvious I’m
missing, as I am by no means a BGP expert.
My bird config looks like this:
log "/var/log/bird" all;
router id xxx.xxx.224.9;
protocol device
{
scan time 60;
}
protocol direct
{
interface "lo1";
}
protocol bgp vultr
{
local as 65xxx;
source address xxx.xxx.224.9;
import none;
export all;
graceful restart on;
next hop self;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "xx";
}
My attempt at a bgpd.conf looks like this:
# Global Configuration
AS 65xxx
router-id xxx.xxx.224.9
# Our Address Space
network xxx.xxx.0.141/32
network inet connected
# IPv4 Peers
neighbor 169.254.169.254 {
remote-as 64515
tcp md5sig password xx
set nexthop self
multihop2
descr Vultr
local-address xxx.xxx.224.9
announceIPv4 unicast
}
Any assistance you fine folks could provide to help me get this working
would be hugely appreciated.
I've also attached my config files to eliminate any chance of them being
mangled.
Thanks so much for your time.
# Global Configuration
AS 65xxx
router-id xxx.xxx.224.9
# Our Address Space
network xxx.xxx.0.141/32
network inet connected
# IPv4 Peers
neighbor 169.254.169.254 {
remote-as 64515
tcp md5sig password xx
set nexthop self
multihop2
descr Vultr
local-address xxx.xxx.224.9
announceIPv4 unicast
}
log "/var/log/bird" all;
router id xxx.xxx.224.9;
protocol device
{
scan time 60;
}
protocol direct
{
interface "lo1";
}
protocol bgp vultr
{
local as 65xxx;
source address xxx.xxx.224.9;
import none;
export all;
graceful restart on;
next hop self;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "xx";
}
Re[2]: [patch] Huawei E1750 support
> 20 P8QP;Q 2011, 23:00 P>Q David Coppa : > > On Wed, Jul 20, 2011 at 8:34 PM, bsd user wrote: > > > Hi, > > > I got E1750 with O2 and noticed it's not working with -current. Here is > > > the > > little patch, that should do the trick. > > > Without this patch, device shows up as a sdX (just the flash part of > > > device, > > and /dev/cuaU0 is not set up) > > > Cheers, > > > Jurij > > > > Please, can you provide us a dmesg with your patch applied? I've snipped dmesg from unimportant things (hope that's not problem) dmesg before patching: --- umsm0 at uhub0 port 3 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 umsm1 at uhub0 port 3 configuration 1 interface 1 "HUAWEI Technologies HUAWEI Mobile Modem" rev 2.00/0.00 addr 2 umsm0 detached umsm1 detached umass0 at uhub0 port 3 configuration 1 interface 3 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 umass0: using SCSI over Bulk-Only scsibus2 at umass0: 2 targets, initiator 0 sd2 at scsibus2 targ 1 lun 0: SCSI2 0/direct removable ugen0 at uhub0 port 3 configuration 1 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 -- and dmesg after patching: -- umsm0 at uhub0 port 3 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 umsm1 at uhub0 port 3 configuration 1 interface 1 "HUAWEI Technologies HUAWEI Mobile Modem" rev 2.00/0.00 addr 2 umsm0 detached umsm1 detached umsm0 at uhub0 port 3 configuration 1 interface 0 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 ucom0 at umsm0 umsm1 at uhub0 port 3 configuration 1 interface 1 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 ucom1 at umsm1 umsm2 at uhub0 port 3 configuration 1 interface 2 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 ucom2 at umsm2 umsm3 at uhub0 port 3 configuration 1 interface 3 "HUAWEI Technology HUAWEI Mobile" rev 2.00/0.00 addr 2 -- > > Is the device working with ppp? Yes, it's working with ppp as /dev/cuaU0 > > ciao, > > David > Cheers, Jurij
[patch] Huawei E1750 support
Hi,
I got E1750 with O2 and noticed it's not working with -current. Here is the
little patch, that should do the trick.
Without this patch, device shows up as a sdX (just the flash part of device,
and /dev/cuaU0 is not set up)
Cheers,
Jurij
Index: dev/usb/umsm.c
===
RCS file: /cvs/src/sys/dev/usb/umsm.c,v
retrieving revision 1.77
diff -u -p -r1.77 umsm.c
--- dev/usb/umsm.c 8 Jul 2011 23:10:31 - 1.77
+++ dev/usb/umsm.c 20 Jul 2011 17:22:33 -
@@ -140,6 +140,7 @@ static const struct umsm_type umsm_devs[
{{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_Mobile }, DEV_HUAWEI},
{{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_K3765_INIT }, DEV_UMASS5},
{{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_K3765 }, 0},
+ {{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1750 }, DEV_UMASS5},
{{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1752 }, 0},
{{ USB_VENDOR_HYUNDAI, USB_PRODUCT_HYUNDAI_UM175 }, 0},
Index: dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.548
diff -u -p -r1.548 usbdevs
--- dev/usb/usbdevs 8 Jul 2011 23:09:06 - 1.548
+++ dev/usb/usbdevs 20 Jul 2011 17:22:34 -
@@ -1963,6 +1963,7 @@ product HUAWEI E220 0x1003 HUAWEI Mobil
product HUAWEI Mobile 0x1008 HUAWEI Mobile Modem
product HUAWEI E1800x140c HUAWEI Mobile E180
product HUAWEI E5100x1411 HUAWEI Mobile E510
+product HUAWEI E1750 0x1406 HUAWEI Mobile Modem
product HUAWEI E1752 0x1417 HUAWEI Mobile Modem
product HUAWEI E1820x1429 HUAWEI Mobile Modem
product HUAWEI E1610x1446 HUAWEI Mobile Modem
Index: dev/usb/usbdevs.h
===
RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
retrieving revision 1.558
diff -u -p -r1.558 usbdevs.h
--- dev/usb/usbdevs.h 8 Jul 2011 23:09:28 - 1.558
+++ dev/usb/usbdevs.h 20 Jul 2011 17:22:34 -
@@ -1970,6 +1970,7 @@
#defineUSB_PRODUCT_HUAWEI_Mobile 0x1008 /* HUAWEI
Mobile Modem */
#defineUSB_PRODUCT_HUAWEI_E180 0x140c /* HUAWEI Mobile E180 */
#defineUSB_PRODUCT_HUAWEI_E510 0x1411 /* HUAWEI Mobile E510 */
+#defineUSB_PRODUCT_HUAWEI_E17500x1406 /* HUAWEI Mobile Modem
*/
#defineUSB_PRODUCT_HUAWEI_E17520x1417 /* HUAWEI
Mobile Modem */
#defineUSB_PRODUCT_HUAWEI_E182 0x1429 /* HUAWEI Mobile Modem
*/
#defineUSB_PRODUCT_HUAWEI_E161 0x1446 /* HUAWEI Mobile Modem
*/
Index: dev/usb/usbdevs_data.h
===
RCS file: /cvs/src/sys/dev/usb/usbdevs_data.h,v
retrieving revision 1.552
diff -u -p -r1.552 usbdevs_data.h
--- dev/usb/usbdevs_data.h 8 Jul 2011 23:09:28 - 1.552
+++ dev/usb/usbdevs_data.h 20 Jul 2011 17:22:36 -
@@ -4010,6 +4010,10 @@ const struct usb_known_product usb_known
"HUAWEI Mobile E510",
},
{
+ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1750,
+ "HUAWEI Mobile Modem",
+ },
+ {
USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E1752,
"HUAWEI Mobile Modem",
},
