Re: text-mode gui
On 12/19/15 18:34, Luke Small wrote: > If installer GUIs are bad, maybe features like full-disk encryption could > be accomplished via lynx-like text -based HTML and/or JavaScript that could > write to cookies that the installer could parse into commands? > > -Luke Please, no. In fact, I'm hoping this whole concept is a bad dream I'm having due to eating raw cookie dough, a contaminated a gyro and overly potent onions. Nick.
Re: -current (#1754) wifi problem
In the -current (1757) wireless network works again. Thank you for you time. 2015-12-19 7:17 GMT+10:00 Stuart Henderson : > > > I have problem with iwn wifi on my Lenovo x201. > > Snapshot kernels contain a diff which is being tested. If you need it to > work now, build a new kernel from a cvs checkout, that won't have the diff > in. > > -- Best wishes.
Re: HUAWEI dongle
On Sat, Dec 19, 2015 at 12:18 PM, Read, James C wrote: >>> Read, James C wrote: >>> > I just installed 5.8, I know my dongle is detected and correctly >>> > switched to the right mode because >>> > >>> > a) I can see in dmesg output that the device is detected and >>> > labelled ugen0 >>> >>> See ugen(4). Basically, the dongle isn't supported. > >>There was recently a good discussion about which WiFi dongles are >>reliably supported. I'd suggest finding cheap well-reviewed options >>online and searching their names on the list archives. > > http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/umsm.4?query=umsm > &sec=4 > > My modem is explicitly listed here (Huawei Mobile E353). And, in fact, the > dmesg mentions umsm0 when the device is detected in dmesg. > > Like I said I know the device is detected and working because I can see the > light continuous. This only happens when the device mode has been succesfully > switched. > > What do I need to do to bring this up with ifconfig? > > Raed Samej > I'm jumping in late, sorry if I'm missing context. If you have your dongle plugged in and it is supported, ifconfig (no switches) should show it as an interface like urtwn0 or another chipset family (in your case, umsm0). I have a Verizon MiFi unit for my wireless internet. Your setup will naturally be different unless you're using the same Verizon MiFi unit for internet. (with root privileges) ifconfig umsm0 up nwid Verizon-291LVW-0007 wpakey You may need firmware for the driver. I have to install iwn firmware for the intel wireless on my X201 ThinkPad. If your network associates with that command above, then dhclient umsm0 I always test by pinging google ping www.google.com Good luck. FWIW, OpenBSD does a better on wireless stick driver support than do the other BSD's, at least last time I went through this a couple years back. The trick is buying a chip (manufacturers switch them out all the time, so you can't depend on the unit model name) that's supported. Carl T.
Huawei Mobile E353 and umsm
Hi, my device Huawei Mobile E353 is listed as known to be supported in the umsm man 4 page http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/umsm.4?query=umsm &sec=4 Does anybody know what the steps are to get a umsm supported device up and running. We are talking basics here. I really don't know where to start. What should I be looking at? PPP? 0x00
Re: HUAWEI dongle
"Read, James C" writes: >>A full dmesg output, or at least an indication of what model the dongle is >>would be useful here. > > Would love to be able to do that. Anybody had success mounting an OpenBSD > filesystem in linux? IIRC it's something like mount -o ro,44bsd. > 0x00 > -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: HUAWEI dongle
>Please send dmesg and the output of: >usbdevs -dv >Both while the Huawei dongle is plugged into your machine, of course... my dmesg gives: umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev 2.00/1.02 addr 2 my usbdevs -dv uhub0 port 1 addr 2 : high speed, power 500 mA, config 1, HUAWEI Mobile E303(0x1f01), HUAWEI Technologies(0x12d1), rev 1.02 cu /dev/cua00 gives Connected to /dev/cua00 (speed 9600) I'm guessing this means everything is working. What do I need to do next to get networking up and running? 0h, by contrast my working lsusb output on Ubuntu gives: Bus 001 Device 007: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131 The packaging says the device is E3533 HSPA+ USB Stick 0x00
text-mode gui
If installer GUIs are bad, maybe features like full-disk encryption could be accomplished via lynx-like text -based HTML and/or JavaScript that could write to cookies that the installer could parse into commands? -Luke
Re: HUAWEI dongle
>> Read, James C wrote: >> > I just installed 5.8, I know my dongle is detected and correctly >> > switched to the right mode because >> > >> > a) I can see in dmesg output that the device is detected and >> > labelled ugen0 >> >> See ugen(4). Basically, the dongle isn't supported. >There was recently a good discussion about which WiFi dongles are >reliably supported. I'd suggest finding cheap well-reviewed options >online and searching their names on the list archives. http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/umsm.4?query=umsm &sec=4 My modem is explicitly listed here (Huawei Mobile E353). And, in fact, the dmesg mentions umsm0 when the device is detected in dmesg. Like I said I know the device is detected and working because I can see the light continuous. This only happens when the device mode has been succesfully switched. What do I need to do to bring this up with ifconfig? Raed Samej
dotted lines flashing on the virtual terminal
Never seen this one before. Just done a clean base install of 5.8 Got white lines of - - flashing across my screen at urandom places. Is this some kind of buffering problem? 0x00
Re: HUAWEI dongle
>You've said that it connects as ugen, and also as umsm. Often the older dongles provided >several serial interfaces, only one of which actually worked. Again, nobody will be able to help >you without the log messages. my dmesg gives: umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev 2.00/1.02 addr 2 my usbdevs -dv uhub0 port 1 addr 2 : high speed, power 500 mA, config 1, HUAWEI Mobile E303(0x1f01), HUAWEI Technologies(0x12d1), rev 1.02 cu /dev/cua00 gives Connected to /dev/cua00 (speed 9600) I'm guessing this means everything is working. What do I need to do next to get networking up and running? 0h, by contrast my working lsusb output on Ubuntu gives: Bus 001 Device 007: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131 The packaging says the device is E3533 HSPA+ USB Stick 0x00
WTMP Question
I've a question about last/utmp/wtmp that someone here should be able to answer. At the shell I do # date Sat Dec 19 16:29:07 MST 2015 # last wtmp begins Sat Dec 19 16:29 2015 This appears to set the beginning time to "now" every time I run the thing. WTF sets the lower bound so as to see back from "now"? It is not exactly obvious from the man pages how this works. I'm sure it's there, I just can't find it. Dhu -- http://babayaga.neotext.ca/PublicKeys/Duncan_Patton_a_Campbell_pubkey.txt Ne obliviscaris, vix ea nostra voco.
Re: HUAWEI dongle
>There was recently a good discussion about which WiFi dongles are >reliably supported. I'd suggest finding cheap well-reviewed options >online and searching their names on the list archives. my dmesg gives: umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev 2.00/1.02 addr 2 my usbdevs -dv uhub0 port 1 addr 2 : high speed, power 500 mA, config 1, HUAWEI Mobile E303(0x1f01), HUAWEI Technologies(0x12d1), rev 1.02 cu /dev/cua00 gives Connected to /dev/cua00 (speed 9600) I'm guessing this means everything is working. What do I need to do next to get networking up and running? 0h, by contrast my working lsusb output on Ubuntu gives: Bus 001 Device 007: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131 The packaging says the device is E3533 HSPA+ USB Stick 0x00
Re: HUAWEI dongle
>A full dmesg output, or at least an indication of what model the dongle is >would be useful here. Would love to be able to do that. Anybody had success mounting an OpenBSD filesystem in linux? 0x00
Re: npppd pppx0 VPN Client can access wan but cannot access lan
> I'm, running OpenBSD 5.8, npppd, mpath and have tried the same on 5.7 and
5.3.
> npppd is works fine and clients can connect using windows pptp client.
> The Client has the pptp connection set as default gateway and can
> access the internet through the vpn gateway but cannot access the LAN
network.
> Traffic arrives on the pppx0 interface but never get forwarded to the
> LAN ip address.
Can you see the traffic for the LAN on $int_if or the other physical
interfaces?
> ## vpn
> pass quick log on pppx
> match out log on $ext1_if from $vpn_net nat-to ($ext1_if)
> match out log on $ext2_if from $vpn_net nat-to ($ext2_if)
> match out log on $int_if from $vpn_net nat-to ($int_if)
Fist line, "pass quick", becomes the last rule for traffic in/out on the
pppx interface since it is "quick". So subsequent rules (including nat) are
not applied.
--yasuoka
I'm used to pf on FreeBSD, the problem was not the quick rule.
It looks like that pf or kernel on OpenBSD sets a "block all" on any
interface not defined in the pf.conf using skip or pass rules, which is a
good thing because this closes unintended security holes.
Thanks for your help.
The below pf.conf does the trick
### NAT
## int_net
match out log on $ext1_if from $int_net nat-to ($ext1_if)
match out log on $ext2_if from $int_net nat-to ($ext2_if)
## vpn
match out log on $ext1_if from $vpn_net nat-to ($ext1_if)
match out log on $ext2_if from $vpn_net nat-to ($ext2_if)
match out log on $int_if from $vpn_net nat-to ($int_if)
### FILTER RULES
block drop quick inet6
block log all
pass out log
## allow ping, traceroute and echo
pass in log inet proto icmp all icmp-type $icmp_types
## internal network
pass in log on $int_if
## pass connections to vpn server
pass in log on pppx
pass log proto { gre } from any to any keep state
pass in log on $ext1_if proto tcp from any to $ext1_if port 1723
pass in log on $ext2_if proto tcp from any to $ext2_if port 1723
Huawei E3533 and umsm
Hi, my dmesg gives: umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev 2.00/1.02 addr 2 my usbdevs -dv uhub0 port 1 addr 2 : high speed, power 500 mA, config 1, HUAWEI Mobile E303(0x1f01), HUAWEI Technologies(0x12d1), rev 1.02 cu /dev/cua00 gives Connected to /dev/cua00 (speed 9600) I'm guessing this means everything is working. What do I need to do next to get networking up and running? 0h, by contrast my working lsusb output on Ubuntu gives: Bus 001 Device 007: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131 The packaging says the device is E3533 HSPA+ USB Stick 0x00
Browsers in OpenBSD with W^X support
Hello, I would like to know if there are others browsers using W^X except Firefox, which I know to have this enabled. I am especially interested in Chromium package.
Re: Browsers in OpenBSD with W^X support
> I would like to know if there are others browsers using W^X > except Firefox, which I know to have this enabled. > I am especially interested in Chromium package. run procmap against such processes, looking for pages which are both "write" and "exece". if you see 1 page that is like that in a program, it isn't triyng to be W^X.
Re: HUAWEI dongle
Anyway, seriously. What do I need to do to get this up and running? I need to connect to the internet to do work on and I've had it with just about every other OS there. It depends on the exact model of dongle. Maybe it's actually supported, but the USB device IDs are different to the ones in the kernel, so it's ignored. Without seeing the full log messages as it connects, it's hard to speculate. As I said previously, I've had Huawei dongles that presented alternative USB device IDs, and after an AT command to disable the unneeded functionality, they presented as a different USB device that was recognised. Alternatively, they worked in their original connect-disconnect-reconnect modes when the other ID was added to the kernel. You've said that it connects as ugen, and also as umsm. Often the older dongles provided several serial interfaces, only one of which actually worked. Again, nobody will be able to help you without the log messages. -- Tati Chevron Perl and FORTRAN specialist. SWABSIT development and migration department. http://www.swabsit.com
Re: HUAWEI dongle
What do I need to do to get this supported. I really don't want to have to work on another system. My Ubuntu usb starts of consuming 1.2 GB of memory after boot and then after a few hours of web browsing is clocking 3.8 GB. Closing the down the desktop the memory is still not freed. Now, if that's not a serious memory leak I can only conclude that it's even worse. And I thought Windows was bad. Help. What do I need to do to get a machine up and running that doesn't steal my memory, CPU cycles, bandwidth etc. etc. etc. END OF RANT Anyway, seriously. What do I need to do to get this up and running? I need to connect to the internet to do work on and I've had it with just about every other OS there. Daer Samej From: Michael McConville Sent: Saturday, December 19, 2015 6:43 PM To: Read, James C Cc: misc@openbsd.org Subject: Re: HUAWEI dongle Read, James C wrote: > I just installed 5.8, I know my dongle is detected and correctly switched to > the right mode because > > a) I can see in dmesg output that the device is detected and labelled ugen0 See ugen(4). Basically, the dongle isn't supported. > b) I can see the led light continuously on the dongle, this only happens in > other environments I've used the dongle in when the dongle is no longer in > mass storage mode (light flashes when in mass storage mode) > > However, when I ifconfig I get nothing.
Re: HUAWEI dongle
>Unfortunately, without more information on YOUR dongle, (which would come >from a dmesg, and/or usbdevs output), I can't give you any specific advice. I'm having trouble mounting my OpenBSD file system under linux so can't get the dmesg for you right now. But I remember the line started with something like umsm0 at HUAWEI So I'm guessing this is the old style? Sorry for the lack of output here. I'm still working on getting my file system mounted so I can get the /var/log/messages for you. 0x00
Re: HUAWEI dongle
Il 19/dic/2015 19:43, "Read, James C" ha scritto: > > Hi, > > I just installed 5.8, I know my dongle is detected and correctly switched to > the right mode because > > a) I can see in dmesg output that the device is detected and labelled ugen0 > b) I can see the led light continuously on the dongle, this only happens in > other environments I've used the dongle in when the dongle is no longer in > mass storage mode (light flashes when in mass storage mode) > > However, when I ifconfig I get nothing. > > What gives? > > 0x00 Please send dmesg and the output of: usbdevs -dv Both while the Huawei dongle is plugged into your machine, of course... Ciao! David
Re: HUAWEI dongle
On Sat, Dec 19, 2015 at 07:30:12PM +, Read, James C wrote: A full dmesg output, or at least an indication of what model the dongle is would be useful here. Would love to be able to do that. Anybody had success mounting an OpenBSD filesystem in linux? 0x00 If you are just trying to move an OpenBSD dmesg to a linux system that has email connectivity, just tar it onto a usb pendrive or similar: # dmesg > /tmp/dm # tar -cf /dev/rsd4c /tmp/dm replacing rsd4c with whatever device the usb pendrive actually shows up as when you connect it. Reading it on the linux machine will be something like: # tar -xf /dev/sda -- Tati Chevron Perl and FORTRAN specialist. SWABSIT development and migration department. http://www.swabsit.com
Re: no mail/reports following power failure
On Sat, Dec 19, 2015 at 01:28:22PM -0500, Nick Holland wrote: Yet another reason bragging about uptime is just plain wrong: not only are you running out of date software, but your most recent changes may not be taking effect as you think they will on next boot. Or, depending where you work, _other peoples' changes_ may not be taking effect as you think they will on next boot. -- Tati Chevron Perl and FORTRAN specialist. SWABSIT development and migration department. http://www.swabsit.com
Re: HUAWEI dongle
On Sat, Dec 19, 2015 at 06:01:19PM +, Read, James C wrote: Hi, I just installed 5.8, I know my dongle is detected and correctly switched to the right mode because a) I can see in dmesg output that the device is detected and labelled ugen0 b) I can see the led light continuously on the dongle, this only happens in other environments I've used the dongle in when the dongle is no longer in mass storage mode (light flashes when in mass storage mode) However, when I ifconfig I get nothing. What gives? 0x00 A full dmesg output, or at least an indication of what model the dongle is would be useful here. The older Huawei dongles appear as serial ports, modern ones will appear as a network adaptor. But they do funky things like presenting themselves first as a CD-ROM device until they are, 'ejected', then re-presenting as a different device with different USB IDs. There are even AT commands to configure which aspects of the functionality you want, (I.E. you can disable the built in driver CD emulation, stop it working with mainstream operating systems, and optimise it for OpenBSD by eliminating the USB connect-disconnect-reconnect cycle). I've done all of this with various Huawei dongles, until they blew up and stopped working due to low production quality, (in my opinion). Unfortunately, without more information on YOUR dongle, (which would come from a dmesg, and/or usbdevs output), I can't give you any specific advice. -- Tati Chevron Perl and FORTRAN specialist. SWABSIT development and migration department. http://www.swabsit.com
Re: HUAWEI dongle
Michael McConville wrote: > Read, James C wrote: > > I just installed 5.8, I know my dongle is detected and correctly > > switched to the right mode because > > > > a) I can see in dmesg output that the device is detected and > > labelled ugen0 > > See ugen(4). Basically, the dongle isn't supported. There was recently a good discussion about which WiFi dongles are reliably supported. I'd suggest finding cheap well-reviewed options online and searching their names on the list archives. > > b) I can see the led light continuously on the dongle, this only > > happens in other environments I've used the dongle in when the > > dongle is no longer in mass storage mode (light flashes when in mass > > storage mode) > > > > However, when I ifconfig I get nothing.
Re: HUAWEI dongle
Read, James C wrote: > I just installed 5.8, I know my dongle is detected and correctly switched to > the right mode because > > a) I can see in dmesg output that the device is detected and labelled ugen0 See ugen(4). Basically, the dongle isn't supported. > b) I can see the led light continuously on the dongle, this only happens in > other environments I've used the dongle in when the dongle is no longer in > mass storage mode (light flashes when in mass storage mode) > > However, when I ifconfig I get nothing.
HUAWEI dongle
Hi, I just installed 5.8, I know my dongle is detected and correctly switched to the right mode because a) I can see in dmesg output that the device is detected and labelled ugen0 b) I can see the led light continuously on the dongle, this only happens in other environments I've used the dongle in when the dongle is no longer in mass storage mode (light flashes when in mass storage mode) However, when I ifconfig I get nothing. What gives? 0x00
Re: no mail/reports following power failure
On 12/19/15 09:21, frcc wrote: > Hi Folks > New here. > Running ver 5.8 on an ibme330 sever. > > Usually get daily reports for disk usage etc > vial mail system on server. > > Following a power interruption I get no more > local mail as user or as Root. ... > > Is there something to re-start in the > daily scheduling system cron? no. OpenBSD is the king of "Just Works", so any time you have to do something like that, you have broken something. > .or. > can someone point me in a general direction > for docs to look at. The process is simple -- root runs a cron job, the output is captured as mail for user root. What happens then is up to what happens to mail sent to root on your system. Follow the trail ... * Is your date/time correct? * Is the cron job still there? (/bin/sh /etc/daily) * What happens when you manually invoke the cron job's script? * What is in /var/cron/log ? * What is in /var/mail/root ? * What is in /var/log/maillog ? * Can you send mail as root to whereever you had the reports go before? Wild guess: you did something which broke something (for example, mail), but didn't actually activate the change by rebooting. So all works great until you reboot (or the power does it for you)...and months later, you wonder "What happened last night?" Wasn't last night. Yet another reason bragging about uptime is just plain wrong: not only are you running out of date software, but your most recent changes may not be taking effect as you think they will on next boot. Nick.
no mail/reports following power failure
Hi Folks New here. Running ver 5.8 on an ibme330 sever. Usually get daily reports for disk usage etc vial mail system on server. Following a power interruption I get no more local mail as user or as Root. Have checked the mail files in etc/mail and run newaliases as root. The mail files appear to be ok according to the man pages for related files in /etc. I have shut the server down and restarted with still no mail delivery locally on lo0 Is there something to re-start in the daily scheduling system cron? .or. can someone point me in a general direction for docs to look at. Thanks in advance
Re: 5.8/sparc64 - boot from softraid(4) fails?
Hi, > ...on Sun, Dec 06, 2015 at 06:02:35PM +0100, Stefan Sperling wrote: > > Can you show the output of 'devalias' at the ok> prompt? > > If your disks are more than 4 levels deep inside the device tree > > then the diskprobe loop in the boot loader won't see them. Finally got around testing your patch (probably just barely, as disk0 is the 10. entry in the devalias list, see previous reply on the list): > Rebooting with command: boot disk0 sr0a:/bsd > Boot device: /pci@1e,60/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0 File > and args: sr0a:/bsd > OpenBSD IEEE 1275 Bootblock 1.4 > >> OpenBSD BOOT 1.7 > Can't read disk label. > Can't open disk label package > sr0* > Booting sr0:a/bsd > 8311464@0x100+3416@0x17ed2a8+209312@0x180+3984992@0x18331a0 Thanks! Alex.
Any idea for table replacement configuration in iked.con
I am trying to find a more efficient way then creating a long list of
policy in iked.conf that would be in in pf using table, but there isn;'t
any table in iked.conf.
As a simple example if I had this in pf
table { 172.16.0.0/16, !172.16.1.0/24, 172.16.1.100 }
would match all the /16, but not the /24 however allow the /32 from the
/24 anyway.
This is a simple one, but how one would go to do something similar in
iked.conf without tables support other the creating a much longer lists
of policy to achieve the same other then creating a bunch of subnet to
cover the same address space?
Any truck may be?
Not a show stopper, but it sure would make the policy much shorter and
avoid human errors down the road.
I would appreciate any possible truck, so far I can't come up with any.
