ro ignored in fstab
Hi, I have a firewall which was originally installed with 5.4 release, and it was configured to be resistant to sudden power outages by means of mounting / as read only, and /var and /dev partitions as mfs populated from /mfs/var and /mfs/dev. Here's fstab: e3f2007c8606c31a.a / ffs ro 1 1 swap /var mfs rw,-P=/mfs/var,-s=32768,nodev,nosuid,noexec 0 0 swap /dev mfs rw,-P=/mfs/dev,-s=8192,-i=128,nosuid,noexec 0 0 Although this is non-critical box on local network, I wanted to keep it up to date so yesterday I upgraded it to 5.5 first, and then to 5.6. It appears that it no longer mounts / as read only. mount output shows the following: /dev/wd0a on / type ffs (local) mfs:15966 on /var type mfs (asynchronous, local, nodev, noexec, nosuid, size=32768 512-blocks) mfs:29006 on /dev type mfs (asynchronous, local, noexec, nosuid, size=8192 512-blocks) Trying to remount it as read/write says device busy: $ sudo mount -ur / mount_ffs: /dev/wd0a on /: Device busy What could be preventing read-only mount? Thank you in advance, -- Marko Cupać https://www.mimar.rs
Re: ro ignored in fstab
On Wed, Apr 29, 2015 at 01:13:28PM +0200, Marko Cupa?? wrote: Hi, I have a firewall which was originally installed with 5.4 release, and it was configured to be resistant to sudden power outages by means of mounting / as read only, and /var and /dev partitions as mfs populated from /mfs/var and /mfs/dev. Here's fstab: e3f2007c8606c31a.a / ffs ro 1 1 swap /var mfs rw,-P=/mfs/var,-s=32768,nodev,nosuid,noexec 0 0 swap /dev mfs rw,-P=/mfs/dev,-s=8192,-i=128,nosuid,noexec 0 0 Although this is non-critical box on local network, I wanted to keep it up to date so yesterday I upgraded it to 5.5 first, and then to 5.6. It appears that it no longer mounts / as read only. mount output shows the following: /dev/wd0a on / type ffs (local) mfs:15966 on /var type mfs (asynchronous, local, nodev, noexec, nosuid, size=32768 512-blocks) mfs:29006 on /dev type mfs (asynchronous, local, noexec, nosuid, size=8192 512-blocks) Trying to remount it as read/write says device busy: $ sudo mount -ur / mount_ffs: /dev/wd0a on /: Device busy What could be preventing read-only mount? rc mounts / rw explicitly these days, to be able to write a random generator seed for the next boot. Why you cannot update to r/w I don't know, but fstat -f / might tell you more. If a file on / is open for r/w, the mount -u wil fail, as documented. -Otto Thank you in advance, -- Marko Cupa?? https://www.mimar.rs
Re: ro ignored in fstab
On Wed, Apr 29, 2015 at 01:39:34PM +0200, Otto Moerbeek wrote: On Wed, Apr 29, 2015 at 01:13:28PM +0200, Marko Cupa?? wrote: Hi, I have a firewall which was originally installed with 5.4 release, and it was configured to be resistant to sudden power outages by means of mounting / as read only, and /var and /dev partitions as mfs populated from /mfs/var and /mfs/dev. Here's fstab: e3f2007c8606c31a.a / ffs ro 1 1 swap /var mfs rw,-P=/mfs/var,-s=32768,nodev,nosuid,noexec 0 0 swap /dev mfs rw,-P=/mfs/dev,-s=8192,-i=128,nosuid,noexec 0 0 Although this is non-critical box on local network, I wanted to keep it up to date so yesterday I upgraded it to 5.5 first, and then to 5.6. It appears that it no longer mounts / as read only. mount output shows the following: /dev/wd0a on / type ffs (local) mfs:15966 on /var type mfs (asynchronous, local, nodev, noexec, nosuid, size=32768 512-blocks) mfs:29006 on /dev type mfs (asynchronous, local, noexec, nosuid, size=8192 512-blocks) Trying to remount it as read/write says device busy: $ sudo mount -ur / mount_ffs: /dev/wd0a on /: Device busy What could be preventing read-only mount? rc mounts / rw explicitly these days, to be able to write a random Btw, it has been like that since 1997, so you had a modified rc, I presume. generator seed for the next boot. Why you cannot update to r/w I don't know, but fstat -f / might tell you more. If a file on / is open for r/w, the mount -u wil fail, as documented. -Otto Thank you in advance, -- Marko Cupa?? https://www.mimar.rs
Re: help with bgpd error messages
On Tue, 28 Apr 2015 15:11:21 +0200 Claudio Jeker cje...@diehard.n-r-g.com wrote: The fatal in RDE: peer_up: bad state bug is fixed in 5.7 IIRC. Not sure if it was backported to 5.6. As a workaround you can disable the graceful restart capability to not trigger that code path. I was intending to upgrade on Friday anyway so no problem. In the meantime I updated to -stable, it's too early to say if it fixed it. Thank you, -- Marko Cupać https://www.mimar.rs
Touchpad interfering with keyboard
Hello, with my new notebook, the touchpad does not seem to work. In dmesg (below), I do not see any fitting entries. Unfortunately whenever I touch it accidentally, garbage keypress events are occuring. What can I try to improve that? With the pre-installed Linux, the dmesg entries for the touchpad were: [2.895047] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa, board id: 3655, fw id: 582762 [2.932037] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input10 With best regards, Michael Warmuth-Uhl --- dmesg --- OpenBSD 5.7-current (GENERIC.MP) #938: Sun Apr 19 10:33:17 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8491663360 (8098MB) avail mem = 8230457344 (7849MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec200 (39 entries) bios0: vendor American Megatrends Inc. version 5.6.5 date 02/10/2015 bios0: Notebook W54_55_94_95_97AU,AUQ acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT SSDT ASF! SSDT SSDT SSDT DMAR acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) RLAN(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.59 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.22 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.22 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2494.22 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimadt0: bogus nmi for apid 0 acpimadt0: bogus nmi for apid 2 acpimadt0: bogus nmi for apid 1 acpimadt0: bogus nmi for apid 3 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 1 (RP01) acpiprt5 at acpi0: bus -1 (RP02) acpiprt6 at acpi0: bus 2 (RP03) acpiprt7 at acpi0: bus 3 (RP04) acpiprt8 at acpi0: bus -1 (RP05) acpiprt9 at acpi0: bus -1 (RP06) acpiprt10 at acpi0: bus -1 (RP07) acpiprt11 at acpi0: bus -1 (RP08) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpipwrres0 at acpi0: PG00, resource for PEG0 acpipwrres1 at acpi0: PG01, resource for PEG1 acpipwrres2 at acpi0: PG02, resource for PEG2 acpitz0 at acpi0: critical temperature is 120 degC acpipwrres3 at acpi0: FN00, resource for FAN0 acpipwrres4 at acpi0: FN01, resource for FAN1 acpipwrres5 at acpi0: FN02, resource for FAN2 acpipwrres6 at acpi0: FN03, resource for FAN3 acpipwrres7 at acpi0: FN04,
Fwd: [EdLUG] [Other] UK Embedded Systems Conferences
- Forwarded message - Date: Tue, 28 Apr 2015 16:17:07 +0100 To: Edinburgh Linux Users Group ed...@lists.edlug.org.uk Subject: [EdLUG] FW: [Other] UK Embedded Systems Conferences Hi all Forwarded message regarding a forthcoming conference... ... Original Message Hi, we are running this conference which we know is often attended by Linux programmers. http://www.device-developer-conference.co.uk It's free for developers and project managers and will be run in: * Reading, England (12th May) * Cambridge, England (14th May) * Warrington, England (2nd June) * Uphall, Scotland (4th June) We would be very grateful if you could let your membership know about this event. Thanks, kind regards Richard Blackburn ___ EdLUG mailing list ed...@lists.edlug.org.uk https://lists.edlug.org.uk/mailman/listinfo/edlug - End forwarded message -
Re: ro ignored in fstab
On Wed, 29 Apr 2015 13:47:38 +0200 Otto Moerbeek o...@drijf.net wrote: On Wed, Apr 29, 2015 at 01:39:34PM +0200, Otto Moerbeek wrote: On Wed, Apr 29, 2015 at 01:13:28PM +0200, Marko Cupa?? wrote: Hi, I have a firewall which was originally installed with 5.4 release, and it was configured to be resistant to sudden power outages by means of mounting / as read only, and /var and /dev partitions as mfs populated from /mfs/var and /mfs/dev. Here's fstab: e3f2007c8606c31a.a / ffs ro 1 1 swap /var mfs rw,-P=/mfs/var,-s=32768,nodev,nosuid,noexec 0 0 swap /dev mfs rw,-P=/mfs/dev,-s=8192,-i=128,nosuid,noexec 0 0 Although this is non-critical box on local network, I wanted to keep it up to date so yesterday I upgraded it to 5.5 first, and then to 5.6. It appears that it no longer mounts / as read only. mount output shows the following: /dev/wd0a on / type ffs (local) mfs:15966 on /var type mfs (asynchronous, local, nodev, noexec, nosuid, size=32768 512-blocks) mfs:29006 on /dev type mfs (asynchronous, local, noexec, nosuid, size=8192 512-blocks) Trying to remount it as read/write says device busy: $ sudo mount -ur / mount_ffs: /dev/wd0a on /: Device busy What could be preventing read-only mount? rc mounts / rw explicitly these days, to be able to write a random Btw, it has been like that since 1997, so you had a modified rc, I presume. generator seed for the next boot. Why you cannot update to r/w I don't know, but fstat -f / might tell you more. If a file on / is open for r/w, the mount -u wil fail, as documented. Otto, thank you for fstat tip, there was bunch of files but just one that was being written to: pacija@rsbgavaalix02:~ $ sudo fstat -f / USER CMD PID FD MOUNTINUM MODE R/WSZ|DV _syslogd syslogd26174 14 / 390155 -rw--- w 4524 Next, i searched for a file with this INUM: pacija@rsbgavaalix02:~ $ sudo find / -inum 390155 /etc/cron/log AFAIK, cron related stuff should be in /var/cron, not /etc/cron. Listing /var showed that cron is a symlink: pacija@rsbgavaalix02:~ $ ls -lh /var/ lrwxr-xr-x 1 root wheel9B Apr 29 11:43 cron - /etc/cron Maybe this has something to do with the way I copied /var to /mfs/var (i used cp -RPp)? I am going to re-try with tar. -- Marko Cupać https://www.mimar.rs
Re: How pf chooses nics on bridges?
* Listas IT listas...@dna.uba.ar [2015-04-28 21:20]: Why is it that blocked packets appear sometimes on fxp0 and sometimes on vether0? it's simply the interface the packet came in on. Thank you. I get that. The question is why sometimes it logs fxp0 and sometimes is vether0 as both are the same physical nic? it logs whatever teh receiving interface is, as set by the lower layers of the stack. why that is sometimes vether and sometimes the underlaying if I can't tell w/o code digging. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services GmbH, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS. Virtual Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
tmux talk in Edinburgh
- Forwarded message - Date: Tue, 28 Apr 2015 13:49:11 +0100 To: Edinburgh Linux Users Group ed...@lists.edlug.org.uk Hi all, As previously advertised Sunday, Robert has kindly offered to do a talk at the May meeting about tmux, the screen multiplexer. Jean-Louis' talk has been rescheduled for July. The meeting will be in the back room of the Southsider Pub, West Richmond Street, Edinburgh. The talk should kick off shortly after 7:30pm. The main talk is expected to last around 40min, with time for QA afterwards. After the talk, there will be time for socializing, with light bites and a chance to catch up with attendees. See you all next week! Tai
Re: cdce0 in ifconfig
On older modems a configuration with these similar values worked properly: http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/umsm.4?query=umsm sec=4 On Wed, Apr 29, 2015 at 1:02 PM, Fred open...@crowsons.com wrote: On 04/29/15 16:34, Cristián Edwards wrote: Hello, How to configure cdce0 device in OpenBSD? Dmesg: cdce0 at uhub1 port 1 configuration 2 interface 0 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: address 00:a0:c6:60:85:70 ugen0 at uhub1 port 1 configuration 2 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500lladdr 00:a0:c6:60:85:70priority: 0 ifconfig: cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:a0:c6:60:85:70 priority: 0 Hardware: http://consumer.huawei.com/en/solutions/m2m-solutions/products/tech-specs/mu6 09-en.htm Regards, Cristian something like: ifconfig cdce0 inet 192.168.0.1 255.255.255.0 should do the trick. hth Fred
cdce0 in ifconfig
Hello, How to configure cdce0 device in OpenBSD? Dmesg: cdce0 at uhub1 port 1 configuration 2 interface 0 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: address 00:a0:c6:60:85:70 ugen0 at uhub1 port 1 configuration 2 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500lladdr 00:a0:c6:60:85:70priority: 0 ifconfig: cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:a0:c6:60:85:70 priority: 0 Hardware: http://consumer.huawei.com/en/solutions/m2m-solutions/products/tech-specs/mu609-en.htm Regards, Cristian
Re: cdce0 in ifconfig
On 04/29/15 16:34, Cristián Edwards wrote: Hello, How to configure cdce0 device in OpenBSD? Dmesg: cdce0 at uhub1 port 1 configuration 2 interface 0 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: address 00:a0:c6:60:85:70 ugen0 at uhub1 port 1 configuration 2 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500lladdr 00:a0:c6:60:85:70priority: 0 ifconfig: cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:a0:c6:60:85:70 priority: 0 Hardware: http://consumer.huawei.com/en/solutions/m2m-solutions/products/tech-specs/mu609-en.htm Regards, Cristian something like: ifconfig cdce0 inet 192.168.0.1 255.255.255.0 should do the trick. hth Fred
Re: cdce0 in ifconfig
Problem is that only the ugen driver is present... so I think there is no chance of speaking with the modem. Will read the link thoruoughly On Wed, Apr 29, 2015 at 4:27 PM, Zé Loff zel...@zeloff.org wrote: On Wed, Apr 29, 2015 at 12:34:12PM -0300, Cristián Edwards wrote: Hello, How to configure cdce0 device in OpenBSD? Dmesg: cdce0 at uhub1 port 1 configuration 2 interface 0 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: address 00:a0:c6:60:85:70 ugen0 at uhub1 port 1 configuration 2 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500lladdr 00:a0:c6:60:85:70priority: 0 ifconfig: cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:a0:c6:60:85:70 priority: 0 Hardware: http://consumer.huawei.com/en/solutions/m2m-solutions/products/tech-specs/mu6 09-en.htm Regards, Cristian You probably need to bring up the modem first. See this message (and rest of thread) as well as the thread it quotes: http://marc.info/?l=openbsd-miscm=142213746124451w=2 Cheers Zé --
Re: cdce0 in ifconfig
On Wed, Apr 29, 2015 at 07:36:30PM +0100, Fred wrote: On 04/29/15 17:13, Cristián Edwards wrote: Tried dhcp in hostname.cdce0 and it didn't work, your idea doesn't work either. cdce and cdcef allow ethernet communication over USB - ie you plug two computers together using a usb cable and basically provides a brige between two machines so doing dhcp does make much sense... What is on the other end of the link? A modem. Fred --
Re: cdce0 in ifconfig
On Wed, Apr 29, 2015 at 04:29:05PM -0300, Cristián Edwards wrote: Problem is that only the ugen driver is present... so I think there is no chance of speaking with the modem. Didn't see that on the full dmesg you s... oh wait. ;) Will read the link thoruoughly Without ucom devices I'd say you don't have much luck... Again, a full dmesg would be handy. Maybe it needs a new driver, maybe the kernel just needs to be told how to recognize it. Maybe you just need to upgrade to -current. Have I mentioned that a full dmesg would allow us to know which version you're running? Nagging aside, best of luck. Cheers Zé On Wed, Apr 29, 2015 at 4:27 PM, Z?? Loff zel...@zeloff.org wrote: On Wed, Apr 29, 2015 at 12:34:12PM -0300, Cristi??n Edwards wrote: Hello, How to configure cdce0 device in OpenBSD? Dmesg: cdce0 at uhub1 port 1 configuration 2 interface 0 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: address 00:a0:c6:60:85:70 ugen0 at uhub1 port 1 configuration 2 Huawei Technologies HUAWEI Mobile rev 2.00/0.00 addr 2 cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500lladdr 00:a0:c6:60:85:70priority: 0 ifconfig: cdce0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:a0:c6:60:85:70 priority: 0 Hardware: http://consumer.huawei.com/en/solutions/m2m-solutions/products/tech-specs/mu6 09-en.htm Regards, Cristian You probably need to bring up the modem first. See this message (and rest of thread) as well as the thread it quotes: http://marc.info/?l=openbsd-miscm=142213746124451w=2 Cheers Z?? -- --
Driver Request: Huawei MU609 Cellular Modem
Hello, I've noticed that there is no support for MU609, it would be great if a nice developer could add support for this card. Dmesg: https://gist.github.com/crised/21ac828798fa45d855bf Lsusb descriptor: https://gist.github.com/crised/a090e8adb342cbc03314 Linux driver: http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/drivers/usb/serial/option.c Regards, Cristian
Re: relayd crashes often
On 25 apr 2015, at 15:29, Claudio Jeker cje...@diehard.n-r-g.com wrote: Took some time to hunt down the cause of these CLOSE_WAIT sessions and caused some sleepless nights since our loadbalancer was hitting them as well. I think the following diff should solve the issue without causing further regressions. The problematic connections are HTTP session that are closed before the backend is started. In that case we can not wait for the backend. After 200 days of peace, relayd started to get killed for yet unknown reason. ALL process are killed. My guess was that Iâm hitting this problem as well. So diff is applied on top of -current on a backup node. Letâs see how it runs from now on. Iâm was running old, post 5.6 snapshot. //mxb
Re: cdce0 in ifconfig
On 04/29/15 17:13, Cristián Edwards wrote: Tried dhcp in hostname.cdce0 and it didn't work, your idea doesn't work either. cdce and cdcef allow ethernet communication over USB - ie you plug two computers together using a usb cable and basically provides a brige between two machines so doing dhcp does make much sense... What is on the other end of the link? Fred
lidsuspend results in reboot
since the apr 24 snapshot, doing a lidsuspend results in a reboot when raising the lid. this has worked as recently back as the 12 april snapshot. can anybody reproduce this? OpenBSD 5.7-current (GENERIC.MP) #834: Fri Apr 24 00:00:30 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF real mem = 2137341952 (2038MB) avail mem = 2090110976 (1993MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 03/31/11, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @ 0xe0010 (67 entries) bios0: vendor LENOVO version 7BETD8WW (2.19 ) date 03/31/2011 bios0: LENOVO 1705CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 97 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4629 serial 327 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0xea00! 0xcf000/0x1000 0xd/0x1000 0xdc000/0x4000! 0xe/0x1! cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Analog Devices AD1981HD, 0x/0x, using Analog Devices AD1981HD audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 1 int 20 pci1 at ppb0 bus 2 em0 at pci1 dev 0 function 0 Intel 82573L rev 0x00: msi, address 00:16:d3:b6:19:57 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 1 int 21 pci2 at ppb1 bus 3 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 1 int 22 pci3 at ppb2 bus 4 ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 1 int 23 pci4 at ppb3 bus 12 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 1 int 16 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 1 int 17 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 1 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 1 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 1 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci5 at ppb4 bus 21 cbb0 at pci5 dev 0 function 0 Ricoh 5C476 CardBus rev 0xb4: apic 1 int 16 Ricoh 5C552 Firewire rev 0x09 at pci5 dev 0 function 1 not configured sdhc0 at pci5 dev 0 function 2 Ricoh 5C822 SD/MMC rev 0x18: apic 1 int 18 sdmmc0 at sdhc0 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 ichpcib0 at pci0 dev 31 function 0 Intel 82801GBM LPC rev 0x02: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x02: DMA, channel 0
Re: lidsuspend results in reboot
On Wed, Apr 29, 2015 at 11:18:05PM +0200, frantisek holop wrote: since the apr 24 snapshot, doing a lidsuspend results in a reboot when raising the lid. this has worked as recently back as the 12 april snapshot. can anybody reproduce this? Please try a later snapshot as there were various resume fixes that went in around the 26th. -ml OpenBSD 5.7-current (GENERIC.MP) #834: Fri Apr 24 00:00:30 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF real mem = 2137341952 (2038MB) avail mem = 2090110976 (1993MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 03/31/11, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @ 0xe0010 (67 entries) bios0: vendor LENOVO version 7BETD8WW (2.19 ) date 03/31/2011 bios0: LENOVO 1705CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 97 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4629 serial 327 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0xea00! 0xcf000/0x1000 0xd/0x1000 0xdc000/0x4000! 0xe/0x1! cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Analog Devices AD1981HD, 0x/0x, using Analog Devices AD1981HD audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 1 int 20 pci1 at ppb0 bus 2 em0 at pci1 dev 0 function 0 Intel 82573L rev 0x00: msi, address 00:16:d3:b6:19:57 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 1 int 21 pci2 at ppb1 bus 3 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 1 int 22 pci3 at ppb2 bus 4 ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 1 int 23 pci4 at ppb3 bus 12 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 1 int 16 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 1 int 17 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 1 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 1 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 1 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci5 at ppb4 bus 21 cbb0 at pci5 dev 0 function 0 Ricoh 5C476 CardBus rev 0xb4: apic 1 int 16 Ricoh 5C552 Firewire rev 0x09 at pci5 dev 0 function 1 not configured sdhc0 at pci5 dev 0 function 2 Ricoh 5C822 SD/MMC rev 0x18: apic 1 int 18 sdmmc0 at sdhc0
Re: lidsuspend results in reboot
Mike Larkin, 29 Apr 2015 14:30: On Wed, Apr 29, 2015 at 11:18:05PM +0200, frantisek holop wrote: since the apr 24 snapshot, doing a lidsuspend results in a reboot when raising the lid. this has worked as recently back as the 12 april snapshot. can anybody reproduce this? Please try a later snapshot as there were various resume fixes that went in around the 26th. mea culpa sorry for the noise, should have tried a later snapshot first. -f -- i am so open-minded my brain falls out.
Re: lidsuspend results in reboot
since the apr 24 snapshot, doing a lidsuspend results in a reboot when raising the lid. this has worked as recently back as the 12 april snapshot. can anybody reproduce this? OpenBSD 5.7-current (GENERIC.MP) #834: Fri Apr 24 00:00:30 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP What do you mean since the 24th? Did you try the 25th, 26th, 27th, 28th, or ... the 29th? By the time you get this mail you could try the 30th as well. It looks like you tried the 24th. Then stopped. You then assumed that counts for testing the all the successive once, leading to you starting your mail with the word Since. Since you tested the past, obviously the future is the same? There have been nearly 3000 lines of changes to the kernel since the morning of the 25th. More than 700 just to the i386 codebase. There are blogs and such all over the place talking about a significant effort in the i386 codebase which is ongoing. So you could download brand new code and find out, right? Did anyone stop you from downloading? Let's get serious and personal here for a second. In other aspects of life, do you behave the same? It's going to impact your job prospects if you give people like me the opportunity to reply like this...
Re: ro ignored in fstab (SOLVED)
On Wed, 29 Apr 2015 14:16:15 +0200 Marko Cupać marko.cu...@mimar.rs wrote: On Wed, 29 Apr 2015 13:47:38 +0200 Otto Moerbeek o...@drijf.net wrote: On Wed, Apr 29, 2015 at 01:39:34PM +0200, Otto Moerbeek wrote: On Wed, Apr 29, 2015 at 01:13:28PM +0200, Marko Cupa?? wrote: Hi, I have a firewall which was originally installed with 5.4 release, and it was configured to be resistant to sudden power outages by means of mounting / as read only, and /var and /dev partitions as mfs populated from /mfs/var and /mfs/dev. Here's fstab: e3f2007c8606c31a.a / ffs ro 1 1 swap /var mfs rw,-P=/mfs/var,-s=32768,nodev,nosuid,noexec 0 0 swap /dev mfs rw,-P=/mfs/dev,-s=8192,-i=128,nosuid,noexec 0 0 Although this is non-critical box on local network, I wanted to keep it up to date so yesterday I upgraded it to 5.5 first, and then to 5.6. It appears that it no longer mounts / as read only. mount output shows the following: /dev/wd0a on / type ffs (local) mfs:15966 on /var type mfs (asynchronous, local, nodev, noexec, nosuid, size=32768 512-blocks) mfs:29006 on /dev type mfs (asynchronous, local, noexec, nosuid, size=8192 512-blocks) Trying to remount it as read/write says device busy: $ sudo mount -ur / mount_ffs: /dev/wd0a on /: Device busy What could be preventing read-only mount? rc mounts / rw explicitly these days, to be able to write a random Btw, it has been like that since 1997, so you had a modified rc, I presume. generator seed for the next boot. Why you cannot update to r/w I don't know, but fstat -f / might tell you more. If a file on / is open for r/w, the mount -u wil fail, as documented. Otto, thank you for fstat tip, there was bunch of files but just one that was being written to: pacija@rsbgavaalix02:~ $ sudo fstat -f / USER CMD PID FD MOUNTINUM MODE R/W SZ|DV _syslogd syslogd26174 14 / 390155 -rw--- w 4524 Next, i searched for a file with this INUM: pacija@rsbgavaalix02:~ $ sudo find / -inum 390155 /etc/cron/log AFAIK, cron related stuff should be in /var/cron, not /etc/cron. Listing /var showed that cron is a symlink: pacija@rsbgavaalix02:~ $ ls -lh /var/ lrwxr-xr-x 1 root wheel9B Apr 29 11:43 cron - /etc/cron Maybe this has something to do with the way I copied /var to /mfs/var (i used cp -RPp)? I am going to re-try with tar. Deleting /mfs/var/cron as a symlink and moving /etc/cron to /mfs/var/cron solved my problem. I guess back at the time of original setup I followed outdated howto which suggested symlinking cron dir from var to etc: https://www.packetmischief.ca/openbsd-compact-flash-firewall/ Regards, -- Marko Cupać https://www.mimar.rs
