Intranet routing with dynamic IPs
Hi everyone, I have a routing question which I don't know how to solve. I have two routers. Both are connected to my ISP and get a dynamic IP. Both are also connected to a local VLAN. I'd like to use the local VLAN for any traffic in between the two and the ISP for everything else. Basically, it should be like: # Router A 1.2.3.x (DHCP) 10.0.0.1/30 10.0.1.1/24 # Router B 2.3.4.x (DHCP) 10.0.0.2/30 10.0.2.1/24 # Network A: 10.0.1.0/24 route 0.0.0.0/0 via 10.0.0.1 route 2.3.4.x/32 via 10.0.0.2 # Network B: 10.0.2.0/24 route 0.0.0.0/0 via 10.0.0.2 route 1.2.3.x/32 via 10.0.0.1 I've tried doing this with BGP with a config like this (on Router A, by example): AS 65001 router-id 10.0.0.1 network inet connected neighbor 10.0.0.2 { remote-as 65002 } The problem here is that a computer in Network A will now try to use Router B to connect to IP-address 2.3.4.5, whereas I want it to use Router A. I'd appreciate if anyone could lead me in the right direction here. The reason why I'm doing is: I want to keep two networks separate, letting them browse the Internet with different IP addresses, but use the immediate link between the local routers for better performance. Kind regards, John Longe
Re: multiple manpaths for man.cgi?
Hi Justina, justina colmena wrote on Sat, May 19, 2018 at 07:52:35PM +: > On Sat, 19 May 2018 18:01:11 + > justina colmenawrote: >> 3.) The links are not generated in the "see also" section for pages on >> the second and third manpaths. > Okay. This looks like more of an issue with the man pages themselves... > which just don't happen to be as fancy as OpenBSD's. > > /usr/local/man/man1/initdb.1 > > .SH "SEE ALSO" > \fBpg_ctl\fR(1), \fBpostgres\fR(1) That is typical man(7) code; BSD systems use the better mdoc(7) language. > The "\fB" and "\fR" are just literal codes for font bold and back to > font regular, not intended to automatically generate links like > OpenBSD's man pages. The feature request has been rotting on the TODO list for some years: http://mandoc.bsd.lv/cgi-bin/cvsweb/TODO?annotate=HEAD Search for "try to guess Xr" in that page. 1.187 406: - jsg on icb, Nov 3, 2014: 407: try to guess Xr in man(7) for hyperlinking 1.226 408: and render them with 409: https://github.com/Debian/debiman/issues/15 410: loc * exist * algo ** size ** imp ** As you see from the classification, it's rated at the lower edge of medium difficulty and medium importance, but people aren't all that eager to spend their time on the obsolete man(7) language, unless their name is esr@, and esr@ didn't contribute to mandoc so far. I guess if you do it the quick and dirty way, it will probably be about twenty to thirty LOC in a single file, i.e. in the man_html.c formatter. If you do it properly, generating AST nodes in the man(7) parser, which i might prefer (not sure yet), it might touch half a dozen files, with the main 20-30 lines going to the man.c parser and the changes to the other files being relatively minor. Yours, Ingo > http://man.openbsd.org/roff > /usr/share/man/man1/ls.1 > > .Sh SEE ALSO > .Xr chflags 1 , > .Xr chmod 1 , > .Xr symlink 7 , > .Xr sticky 8 > > And that ".Xr" is some sort of macro more suitable for processing into > a link.
Re: Viewport for man.openbsd.org -- readability on phones
Thank you Ingo, http://man.openbsd.org/ works great for me too now. -- I've found some more OpenBSD web pages that could benefit from readable text on phone devices: - httpd, all directory listings. sample: http://ftp.openbsd.org/pub/OpenBSD/6.3/i386/ - cvsweb, all pages: https://cvsweb.openbsd.org/cgi-bin/cvsweb/ - iked project pages: http://www.openiked.org/goals.html http://www.openiked.org/manual.html http://www.openiked.org/papers.html http://www.openiked.org/users.html http://www.openiked.org/security.html -- screenshots (original | viewport): https://viewports.github.io/httpd-cvsweb-iked.html info about viewport: https://marc.info/?l=openbsd-misc=152665457925541=2
Re: multiple manpaths for man.cgi?
Hi Justina, justina colmena wrote on Sat, May 19, 2018 at 06:01:11PM +: > I was looking for more man pages, so I copied the ones > in /usr/X11R6/man and /usr/local/man over to /var/www/man and listed > them in manpath.conf as instructed. So now they are available here. > > https://amarillo.colmena.biz/cgi-bin/man.cgi > > Several issues here: What you report is all intentional and working as designed. > 1.) The search is not falling through to the second and third manpaths. No. That is intentional. For man.cgi(8), different manpaths are intended to represent completely independent manual page trees, for example for different operating systems or different operating system versions. So if you want to search across a given set of manual pages, put them all into the same manpath. For man(1), from the perspective of search tools, having all the pages in a single path would also be simpler, but it would mix base system, Xenocara, and ports content, so we don't do it. That difference also makes sense from the following perspective: Using man(1) locally on a given machine, you typically want to look at manual pages of the installed version of the installed operating system only, so having only one operating system set up is a sane default. Of course, if you want to install pages for a different system, you can still do so in a user-defined tree. For example, the man-pages-posix port does something like that. On a web server, you often want to serve pages for more than one system, so having easy multi-system support is sane. Of course, you can still put everything into a single manpath if that's what you want. That will even automatically hide the selection dropdown. > 2.) The manpath appears in the URL for the second and third manpaths, > but not the first. That's intentional. We shorten the URI as much as possible because that's very convenient for users. As a matter of fact, i type out URIs by hand more often that using the search form. My main use case for the search form is complicated apropos(1) queries. Besides, the first manpath is intended as the default operating system served by the server, the other for alternative systems requested less frequently. I guess every server has a default system. > 3.) The links are not generated in the "see also" section for pages on > the second and third manpaths. No. It is intentional that you cannot link from one operating system to a different one. That would be seriously confusing. Yours, Ingo
Re: multiple manpaths for man.cgi?
On Sat, 19 May 2018 18:01:11 + justina colmenawrote: > 3.) The links are not generated in the "see also" section for pages on > the second and third manpaths. Okay. This looks like more of an issue with the man pages themselves... which just don't happen to be as fancy as OpenBSD's. /usr/local/man/man1/initdb.1 .SH "SEE ALSO" \fBpg_ctl\fR(1), \fBpostgres\fR(1) The "\fB" and "\fR" are just literal codes for font bold and back to font regular, not intended to automatically generate links like OpenBSD's man pages. http://man.openbsd.org/roff /usr/share/man/man1/ls.1 .Sh SEE ALSO .Xr chflags 1 , .Xr chmod 1 , .Xr symlink 7 , .Xr sticky 8 And that ".Xr" is some sort of macro more suitable for processing into a link.
Re: Viewport for man.openbsd.org -- readability on phones
On 05/19/18 00:04, Mihai Popescu wrote: I don't understand what you are trying to say. I took and iPhone with iOS and Safari ( i think!) on it and pointed the browser to the current link of man pages [1]. All i can say is the layout is displayed on full display, not stretched. Text is fine, paragraphs are scaled ok, not even a simple problem. Font is fine. [1] https://man.openbsd.org/ I tried it on my iPhone 5s and everything looks great!
Re: OT: Temperature sensors suggestions?
http://man.openbsd.org/onewire http://man.openbsd.org/uow.4 http://man.openbsd.org/owtemp.4
multiple manpaths for man.cgi?
I was looking for more man pages, so I copied the ones in /usr/X11R6/man and /usr/local/man over to /var/www/man and listed them in manpath.conf as instructed. So now they are available here. https://amarillo.colmena.biz/cgi-bin/man.cgi Several issues here: 1.) The search is not falling through to the second and third manpaths. 2.) The manpath appears in the URL for the second and third manpaths, but not the first. 3.) The links are not generated in the "see also" section for pages on the second and third manpaths.
Re: OT: Temperature sensors suggestions?
On 5/19/2018 4:52 AM, Hiltjo Posthuma wrote: > On Fri, May 18, 2018 at 04:42:01PM -0400, Daniel Ouellet wrote: >> Does anyone have a decent temperature sensors that can connect to an >> OpenBSD server and be reliable and give any decent reading via either >> USB or Serial port or even stand alone via Ethernet? >> [snip] > > I use PCsensors TEMPer-based USB device and the ugold(4) driver. > It works well. > For a simple temperature sensor setup, the TEMPer-based sensor works very well. I just plugged it into the USB port via a short USB extension cable, and started to monitor the temperature via OpenBSD's sensor framework. # sysctl hw.sensors.cpu0.temp0 hw.sensors.cpu0.temp0=23.00 degC
Re: OT: Temperature sensors suggestions?
I would suggest bme280 sensor. If you have a spare VGA port you can use the d2c bus as i2c and plug directly into it with a modified VGA cable. Other wise yeah esp8266 module + bme280 for 5$ is going to give you the best result. On Fri., 18 May 2018, 4:01 pm Base Pr1me,wrote: > I roll SHT31-Ds through ESP8266s via I2C. Of course, there is programming > involved. > Good hardware though, if that's what you're looking for. > > On Fri, May 18, 2018 at 2:42 PM, Daniel Ouellet > wrote: > > > Does anyone have a decent temperature sensors that can connect to an > > OpenBSD server and be reliable and give any decent reading via either > > USB or Serial port or even stand alone via Ethernet? > > > > I asked because yes I can use the sensors on some servers, but I got a > > pretty expensive router blowing up because an AC unit stop working and > > in a few hours the router was history and I need something reliable so I > > can graph the changes in temperature to keep track of things. > > > > I got lucky this time as that using was providing 192 VoIP channels and > > I had just moved them from PRI to full SIP like a month earlier. If I > > haven't done that it would have been a disaster for me! > > > > So, I need more then just servers sensors so I can place these at > > various location to get a better idea of what's going on. > > > > I don't understand why it is so difficult to have decent AC technician > > keep AC units working properly. It's not like brain surgery, but that's > > always a problem. > > > > Anything you know or use that is reliable that you can recommend would > > be very much appreciated. > > > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > > no proprietary shit or Windows crap like I found tonnes of them. I have > > NO Windows systems for 20+ years already and I am sure hell not going to > > install any either. I try to keep it simple. Even snmp reading is find. > > Simpler the better. I can grab the reading and save to a database to > > graph later and what not. I got two self standing units in the pass, > > nice but they get hacked and not useful obviously, so add-on to OpenBSD > > is better to me. I trust that way more then all the self standing units, > > records proving it... > > > > If that's no interest for the list fell free to reply off line as well, > > but I guess some might like to know too. > > > > Thanks in advance for any suggestions... > > > > Daniel > > > > >
Re: Viewport for man.openbsd.org -- readability on phones
On Saturday, May 19, 2018, Mihai Popescuwrote: > > I don't understand what you are trying to say. > > I took and iPhone with iOS and Safari ( i think!) on it and pointed > the browser to the current link of man pages [1]. All i can say is the > layout is displayed on full display, not stretched. > Text is fine, paragraphs are scaled ok, not even a simple problem. Font is > fine. > > [1] https://man.openbsd.org/ > > I can second that. It looks perfect on iPhone using Safari. --Andy
Re: OT: Temperature sensors suggestions?
I do not remember where I bought my ugold(4) back then (maybe soekris?), but this one looks the same: https://www.amazon.de/Thermometer-Temperatur-Sensor-Rekord-F%C3%BCr-PC-Maschine/dp/B00C0OW4OE Since it says on the inside: "pcsensor.com" this might be the origin: http://pcsensor.com/usb-thermometers/gold-temper.html With it I get: hw.sensors.ugold0.temp0=29.12 degC (inner) It's not super correct, my tests seemed to show that the deviation depends on the current temperatur range. Marcus dan...@presscom.net (Daniel Ouellet), 2018.05.18 (Fri) 22:42 (CEST): > Does anyone have a decent temperature sensors that can connect to an > OpenBSD server and be reliable and give any decent reading via either > USB or Serial port or even stand alone via Ethernet? > > I asked because yes I can use the sensors on some servers, but I got a > pretty expensive router blowing up because an AC unit stop working and > in a few hours the router was history and I need something reliable so I > can graph the changes in temperature to keep track of things. > > I got lucky this time as that using was providing 192 VoIP channels and > I had just moved them from PRI to full SIP like a month earlier. If I > haven't done that it would have been a disaster for me! > > So, I need more then just servers sensors so I can place these at > various location to get a better idea of what's going on. > > I don't understand why it is so difficult to have decent AC technician > keep AC units working properly. It's not like brain surgery, but that's > always a problem. > > Anything you know or use that is reliable that you can recommend would > be very much appreciated. > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > no proprietary shit or Windows crap like I found tonnes of them. I have > NO Windows systems for 20+ years already and I am sure hell not going to > install any either. I try to keep it simple. Even snmp reading is find. > Simpler the better. I can grab the reading and save to a database to > graph later and what not. I got two self standing units in the pass, > nice but they get hacked and not useful obviously, so add-on to OpenBSD > is better to me. I trust that way more then all the self standing units, > records proving it... > > If that's no interest for the list fell free to reply off line as well, > but I guess some might like to know too. > > Thanks in advance for any suggestions... > > Daniel >
Re : Temperature sensors suggestions?
Hello, For production environment, You may give a try to mosquitto package and to industrial modules which support mqtt 3.1 or 3.1.1. As far as i remember there's some which support standard rtd sensor like pt100/pt1000 and publish their data over wifi or ethernet. (Try adam 6015 series for example). It usually fits on a DIN rail... Eric.
Re: Troubleshooting rl instability on OpenBSD 6.1 [Machine replaced with APU2]
On 06/05/18 16:02, Stuart Longland wrote: > About 45 minutes later, I got a burst of errors from my cron job. > Pinging the border router yielded no reply, but I could still ping the > TS-7670. I think that confirms hardware. > > Disappointingly, I've not heard from PC Engines regarding the APU2 and > its power supply tolerance, but I've placed an order with Yawarra > Computers anyway, as it *looks* as if all the expensive bits that touch > 12V can take 24V+. > > If a 12V capacitor blows, well I have the schematics and a soldering > iron to replace that part. Plus, the old border router is still there > even if not the most reliable. > > When that arrives, I can look at getting OpenBSD 6.3 onto that, and > migrating my old config across. Okay, I've moved the configuration over now to a shiny new APU2. Turns out there's a TVS diode which starts conducting at 14V, so I'm using a LM1085-12 on a small heatsink to drop the ~14V supply from the battery down to 12V for the APU2. Interestingly, the boot firmware in dmesg says "APU3" (invoice says APU2 though): > OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 4261076992 (4063MB) > avail mem = 4124868608 (3933MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdffb7020 (7 entries) > bios0: vendor coreboot version "4.0.7" date 03/02/2017 > bios0: PC Engines APU3 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S1 S2 S3 S4 S5 > acpi0: tables DSDT FACP SSDT APIC HEST SSDT SSDT HPET > acpi0: wakeup devices PWRB(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) > UOH1(S3) UOH3(S3) UOH5(S3) XHC0(S4) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD GX-412TC SOC, 998.26 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1 > cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line > 16-way L2 cache > cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative > cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative > acpitimer0: recalibrated TSC frequency 998010337 Hz > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 99MHz > cpu0: mwait min=64, max=64, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD GX-412TC SOC, 998.14 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1 > cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line > 16-way L2 cache > cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative > cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 2 (application processor) > cpu2: AMD GX-412TC SOC, 998.15 MHz > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1 > cpu2: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line > 16-way L2 cache > cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative > cpu2: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: AMD GX-412TC SOC, 998.14 MHz > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1 > cpu3: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line > 16-way L2 cache > cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative > cpu3: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative > cpu3: smt 0, core 3, package 0 > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins > ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins > , remapped to apid 5 > acpihpet0 at
Re: OT: Temperature sensors suggestions?
On Fri, May 18, 2018 at 04:42:01PM -0400, Daniel Ouellet wrote: > Does anyone have a decent temperature sensors that can connect to an > OpenBSD server and be reliable and give any decent reading via either > USB or Serial port or even stand alone via Ethernet? > > I asked because yes I can use the sensors on some servers, but I got a > pretty expensive router blowing up because an AC unit stop working and > in a few hours the router was history and I need something reliable so I > can graph the changes in temperature to keep track of things. > > I got lucky this time as that using was providing 192 VoIP channels and > I had just moved them from PRI to full SIP like a month earlier. If I > haven't done that it would have been a disaster for me! > > So, I need more then just servers sensors so I can place these at > various location to get a better idea of what's going on. > > I don't understand why it is so difficult to have decent AC technician > keep AC units working properly. It's not like brain surgery, but that's > always a problem. > > Anything you know or use that is reliable that you can recommend would > be very much appreciated. > > I am trying to keep it simple, so using base tools in OpenBSD is a must, > no proprietary shit or Windows crap like I found tonnes of them. I have > NO Windows systems for 20+ years already and I am sure hell not going to > install any either. I try to keep it simple. Even snmp reading is find. > Simpler the better. I can grab the reading and save to a database to > graph later and what not. I got two self standing units in the pass, > nice but they get hacked and not useful obviously, so add-on to OpenBSD > is better to me. I trust that way more then all the self standing units, > records proving it... > > If that's no interest for the list fell free to reply off line as well, > but I guess some might like to know too. > > Thanks in advance for any suggestions... > > Daniel > I use PCsensors TEMPer-based USB device and the ugold(4) driver. It works well. -- Kind regards, Hiltjo
Re: Viewport for man.openbsd.org -- readability on phones
https://man.openbsd.org/mandoc.css That's the css. You style it how you like it. That's the whole point of it. And I agree. It's very readable on my phone. Original message From: Mihai PopescuDate: 5/18/18 11:04 PM (GMT-09:00) To: misc@openbsd.org Subject: Re: Viewport for man.openbsd.org -- readability on phones > I don't understand what you are trying to say. I took and iPhone with iOS and Safari ( i think!) on it and pointed the browser to the current link of man pages [1]. All i can say is the layout is displayed on full display, not stretched. Text is fine, paragraphs are scaled ok, not even a simple problem. Font is fine. [1] https://man.openbsd.org/
Re: Viewport for man.openbsd.org -- readability on phones
> I don't understand what you are trying to say. I took and iPhone with iOS and Safari ( i think!) on it and pointed the browser to the current link of man pages [1]. All i can say is the layout is displayed on full display, not stretched. Text is fine, paragraphs are scaled ok, not even a simple problem. Font is fine. [1] https://man.openbsd.org/