Re: Compiler error building 5.3
On Fri, Jun 07, 2013 at 04:43:24PM +1000, John Tate wrote: > >I didn't think I had to, 5.3 is stable not current or am I wrong about >that? Confusing. >I ended up just upgrading using the sets and everything is fine now. Lol, but you were trying to build from src, without having done any normal binary update first.
Re: Compiler error building 5.3
I didn't think I had to, 5.3 is stable not current or am I wrong about that? Confusing. I ended up just upgrading using the sets and everything is fine now. On Wed, Jun 5, 2013 at 11:03 PM, Marc Espie wrote: > On Wed, Jun 05, 2013 at 07:01:27PM +1000, John Tate wrote: > > I am having trouble building 5.3, I ran cvs a second time just be to be > > sure everything was right. > > ../../../../arch/i386/i386/locore.s > > ../../../../arch/i386/i386/locore.s: Assembler messages: > > ../../../../arch/i386/i386/locore.s:1755: Error: no such instruction: > `stac' > > ../../../../arch/i386/i386/locore.s:1759: Error: no such instruction: > `clac' > > *** Error code 1 > > You didn't read the FAQ, did you ? especially the part about > "following current"... > -- www.johntate.org
Wireless access point not appearing to clients.
I just configured a wireless device for hostap and put it on a bridge with my wired network and a virtual ethernet device to give it an address. The wired network is working fine, so if I solve this problem the wireless should work fine, but the access point is not appearing in scans. I might have missed an option for it to do this. menger:root # cat /etc/hostname.run0 up media autoselect mediaopt hostap nwid KintaroADOBE chan 12 wpa wpakey XXX wpaprotos wpa2 menger:root # cat /etc/hostname.fxp0 up menger:root # cat /etc/hostname.vether0 inet 10.0.0.1 255.0.0.0 10.0.0.255 up menger:root # cat /etc/hostname.bridge0 add vether0 add fxp0 add run0 up menger:root # ifconfig run0 run0: flags=8943 mtu 1500 lladdr 00:22:75:8e:f2:f8 priority: 4 groups: wlan media: IEEE802.11 autoselect (DS1 mode 11g) status: no network ieee80211: nwid KintaroADOBE chan 12 wpakey wpaprotos wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip inet6 fe80::222:75ff:fe8e:f2f8%run0 prefixlen 64 tentative scopeid 0x5 What have I missed? -- www.johntate.org
Re: 5.3 change affecting hostname.if, dhcp
On Thu, Jun 06, 2013 at 07:09:05PM -0400, gpon...@spamcop.net wrote: > I recently updated from 5.2 to 5.3 and one ethernet port got broken. > The port connected to a cable modem and was configured for DHCP. > With 5.3, the DHCP assigned address is getting lost when I add an > alias. Mixing dhcp and aliases is not supported in 5.3 as we search for a consistant and reliable way to accomplish it. dhclient will always remove all addresses present on the interface when applying the lease. Ken >The alias and a route table addition give the LAN a way to > communicate with the modem's web interface which is fixed at > 192.168.100.1. My hostname.em2 contents are: > > dhcp rdomain 1 > alias 192.168.100.2 255.255.255.0 > !route -T 1 add 192.168.100.0/24 192.168.100.2 > > I also have a DSL modem on em1 with fixed IP that should not be > affected by the DHCP response, so my implementation used a separate > routing table for the two WAN ports. > > /etc >> sh /etc/netstart em2 > > DHCPREQUEST on em2 to 255.255.255.255 port 67 > DHCPACK from 73.70.192.1 (00:01:5c:33:0e:01) > bound to 98.207.205.23 -- renewal in 5572 seconds. > route: writing to routing socket: File exists > add net 192.168.100.0/24: gateway 192.168.100.2: File exists > > > /etc >> ifconfig em2 > em2: > flags=28b43 > rdomain 1 mtu 1500 > lladdr 00:24:81:7f:ee:0b > priority: 0 > media: Ethernet autoselect (1000baseT full-duplex,master) > status: active > inet 192.168.100.2 netmask 0xff00 broadcast 192.168.100.255 > /etc >> > > I would have expect to see two inet lines, one with the DHCP > assigned address and another with the alias. As it is, the LAN can't > get to the cable modem and the LAN can't route through the > DHCP-assigned gateway. Removing the alias solves the routing problem > but not the cable modem management access. Any thoughts or > suggestions for how to fix this, or an alternate solution ? > > GP
5.3 change affecting hostname.if, dhcp
I recently updated from 5.2 to 5.3 and one ethernet port got broken. The port connected to a cable modem and was configured for DHCP. With 5.3, the DHCP assigned address is getting lost when I add an alias. The alias and a route table addition give the LAN a way to communicate with the modem's web interface which is fixed at 192.168.100.1. My hostname.em2 contents are: dhcp rdomain 1 alias 192.168.100.2 255.255.255.0 !route -T 1 add 192.168.100.0/24 192.168.100.2 I also have a DSL modem on em1 with fixed IP that should not be affected by the DHCP response, so my implementation used a separate routing table for the two WAN ports. /etc >> sh /etc/netstart em2 DHCPREQUEST on em2 to 255.255.255.255 port 67 DHCPACK from 73.70.192.1 (00:01:5c:33:0e:01) bound to 98.207.205.23 -- renewal in 5572 seconds. route: writing to routing socket: File exists add net 192.168.100.0/24: gateway 192.168.100.2: File exists /etc >> ifconfig em2 em2: flags=28b43 rdomain 1 mtu 1500 lladdr 00:24:81:7f:ee:0b priority: 0 media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 192.168.100.2 netmask 0xff00 broadcast 192.168.100.255 /etc >> I would have expect to see two inet lines, one with the DHCP assigned address and another with the alias. As it is, the LAN can't get to the cable modem and the LAN can't route through the DHCP-assigned gateway. Removing the alias solves the routing problem but not the cable modem management access. Any thoughts or suggestions for how to fix this, or an alternate solution ? GP
Re: Disable inteldrm
On Thu, Jun 06, 2013 at 02:37:54PM +0200, Gregor Best wrote: > > Just for the record, that URL links to a post about IPSEC. I'm quite > confident you meant another post :) Sorry. This is the thread: http://marc.info/?l=openbsd-misc&m=136689079009585&w=2 > Might I ask why you want to disable inteldrm? A bug report that leads to > an actual fix for your problem might be more useful than sidestepping > the issue. I explained in the link above (now the correct one). The hardware is pretty generic, and only one person signaled to have the same issue, so I thought it was pretty specific to my configuration. Thank you.
Re: extattr on OpenBSD
2013/6/7 Ted Unangst > On Thu, Jun 06, 2013 at 03:40, Jiri B wrote: > > As now FUSE is in the tree, is there a plan to resuscitate > > extattr on OpenBSD, so some filesystems in usespace could > > work or benefit from it? I'd like to see to be able to access > > glusterfs for example which uses extattr for its own metadata. > > I don't think so. > Too many tools remain unaware of them, causing attributes to get > stripped off doing rather mundane operations. > > Samba 4 also may use extattr to save some network-share-specific information, so this could be really useful in that case. But not for generic use, of course - and adding a bloat to kernel just to the sake of compatibility with other OS... oh, we already have Linux ABI, don't we? :) -- WBR, Vadim Zhukov
Re: extattr on OpenBSD
On Thu, Jun 06, 2013 at 03:40, Jiri B wrote: > As now FUSE is in the tree, is there a plan to resuscitate > extattr on OpenBSD, so some filesystems in usespace could > work or benefit from it? I'd like to see to be able to access > glusterfs for example which uses extattr for its own metadata. I don't think so. Too many tools remain unaware of them, causing attributes to get stripped off doing rather mundane operations.
Re: Suspend/Resume on Lemote Yeeloong netbook
Do you know if this is an OpenBSD issue, or hardware? I didn't keep Linux on it long enough to check... So, does this mean that no kind of suspend/hibernate works? It starts up pretty quick, but not quick enough to replace suspend/resume for me I don't think. On Thu, Jun 6, 2013 at 5:45 PM, Bryan Irvine wrote: > oops, replied to only Miod. > > > On Thu, Jun 6, 2013 at 9:43 AM, Bryan Irvine wrote: > > > > > > > > > On Wed, Jun 5, 2013 at 9:25 PM, Miod Vallat wrote: > > > >> > I have installed OpenBSD onto my Lemote netbook, and have apmd running > >> on > >> > startup. If I run the command 'zzz' the computer suspends perfectly. > >> > However, on turning the machine back on, it boots as normal, with > >> complains > >> > about being uncleanly shutdown. > >> > >> How did you `turn the machine back on'? > >> > >> > On closing the lid of the netbook, the computer remains on. > >> > >> OpenBSD is not able to detect lid close on the Yeeloong at the moment. > >> > >> > So, simply put, how can I make suspend/resume work? I'm happy to run > the > >> > 'zzz' command instead of closing the lid, I'd just like to know how to > >> make > >> > it work at all. > >> > >> Suspend: zzz > >> Resume: press any key or the touchpad. Do not touch the power button. > >> > > > This only intermittently works on my 8089B.
Re: ALTQ(32bit)
On 2013-06-04, Andy wrote:
> So whilst it may seem strange to create state as the packet enters an
> interface and record a queue name in the state which only works in the
> opposite (egress) direction (ALTQ can only queue on egress), all 'reply'
> packets which are part of the connection will get queued as they egress
> the internal interface.
Just to pick up one point from this, I recommend using the same queue
names on multiple interfaces, it significantly simplifies handling reply
traffic as you don't have to worry about which direction created the
state.
e.g.
altq on bnx0 hfsc bandwidth 1000Kb queue {fast, med, low, bulk}
queue fast on bnx0 bandwidth 30% priority 8 qlimit 20 hfsc (realtime 180Kb)
queue med on bnx0 bandwidth 5% priority 4 qlimit 40 hfsc (realtime (250Kb,
1, 90Kb))
queue low on bnx0 bandwidth 20% priority 2 qlimit 50 hfsc (realtime (200Kb,
1, 60Kb) default)
queue bulk on bnx0 bandwidth 5% priority 1 qlimit 50 hfsc
altq on em1 hfsc bandwidth 2150Kb queue {fast, med, low, bulk}
queue fast on em1 bandwidth 30% priority 8 qlimit 50 hfsc (realtime 256Kb)
queue med on em1 bandwidth 5% priority 4 qlimit 50 hfsc (realtime (200Kb,
1, 72Kb))
queue low on em1 bandwidth 20% priority 2 qlimit 50 hfsc (realtime (200Kb,
1, 72Kb) default)
queue bulk on em1 bandwidth 5% priority 1 qlimit 50 hfsc
altq on bnx1 hfsc bandwidth 80Mb queue {local, internet}
queue local on vlan3666 bandwidth 1% priority 8 qlimit 50 hfsc (realtime 50Mb
upperlimit 50Mb)
queue internet on vlan3666 bandwidth 3Mb priority 8 qlimit 50 hfsc (realtime
3Mb upperlimit 3Mb) {fast, med, low, bulk}
queue fast on vlan3666 bandwidth 1% priority 8 qlimit 50 hfsc (realtime
256Kb)
queue med on vlan3666 bandwidth 1% priority 4 qlimit 50 hfsc (realtime
(800Kb, 1, 256Kb) upperlimit 800Kb)
queue low on vlan3666 bandwidth 1% priority 2 qlimit 50 hfsc (realtime
(500Kb, 1, 256Kb) upperlimit 500Kb default)
queue bulk on vlan3666 bandwidth 1% priority 1 qlimit 50 hfsc
Re: Suspend/Resume on Lemote Yeeloong netbook
oops, replied to only Miod. On Thu, Jun 6, 2013 at 9:43 AM, Bryan Irvine wrote: > > > > On Wed, Jun 5, 2013 at 9:25 PM, Miod Vallat wrote: > >> > I have installed OpenBSD onto my Lemote netbook, and have apmd running >> on >> > startup. If I run the command 'zzz' the computer suspends perfectly. >> > However, on turning the machine back on, it boots as normal, with >> complains >> > about being uncleanly shutdown. >> >> How did you `turn the machine back on'? >> >> > On closing the lid of the netbook, the computer remains on. >> >> OpenBSD is not able to detect lid close on the Yeeloong at the moment. >> >> > So, simply put, how can I make suspend/resume work? I'm happy to run the >> > 'zzz' command instead of closing the lid, I'd just like to know how to >> make >> > it work at all. >> >> Suspend: zzz >> Resume: press any key or the touchpad. Do not touch the power button. >> > This only intermittently works on my 8089B.
Re: Disable inteldrm
On Wed, Jun 05, 2013 at 09:18:26AM -0300, Daniel Bolgheroni wrote: > [...] > http://marc.info/?l=openbsd-misc&m=136688870408752&w=2 > [...] Just for the record, that URL links to a post about IPSEC. I'm quite confident you meant another post :) > Disabling with 'boot -c' is OK, X works, but I can't set my native > resolution. Setting Option "DRI" to "False" in xorg.conf doesn't help > either. > [...] That is because the intel driver in current Xenocara needs inteldrm for the modesetting. If the modesetting is not available, the intel driver fails to attach and Xenocara falls back to vesa, which only supports the most basic resolutions. Might I ask why you want to disable inteldrm? A bug report that leads to an actual fix for your problem might be more useful than sidestepping the issue. -- Gregor Best
Re: Suspend/Resume on Lemote Yeeloong netbook
Thank you for the reply, I have now tried suspending with 'zzz', which puts the netbook to sleep within a second, but it will not turn back on by pressing keys or the touchpad/touchpad buttons. So now the machine will not go back on, unless I assume, if I use the power button, in which case it will come up from cold boot rather than resume. Thanks for the help, any other ideas? On Thu, Jun 6, 2013 at 5:25 AM, Miod Vallat wrote: > > I have installed OpenBSD onto my Lemote netbook, and have apmd running on > > startup. If I run the command 'zzz' the computer suspends perfectly. > > However, on turning the machine back on, it boots as normal, with > complains > > about being uncleanly shutdown. > > How did you `turn the machine back on'? > > > On closing the lid of the netbook, the computer remains on. > > OpenBSD is not able to detect lid close on the Yeeloong at the moment. > > > So, simply put, how can I make suspend/resume work? I'm happy to run the > > 'zzz' command instead of closing the lid, I'd just like to know how to > make > > it work at all. > > Suspend: zzz > Resume: press any key or the touchpad. Do not touch the power button. > > Miod
extattr on OpenBSD
As now FUSE is in the tree, is there a plan to resuscitate extattr on OpenBSD, so some filesystems in usespace could work or benefit from it? I'd like to see to be able to access glusterfs for example which uses extattr for its own metadata. Just curious. jirib
