dmassage - openbsd 5.4 build failure
Hi, prompted by the quest of a smaller kernel on my old OmniBook 800 (for which memory modules are harder to find than a standard laptop), I tried my luck with dmassage against a stock GENERIC 5.4 kernel conf. I used the generated config fil, except that I enabled a couple of more PCMCIA drivers, which are of course all disabled except the currently inserted card. Build fails with: cc -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-main -Wno-uninitialized -Wno-format -Wstack-larger-than-2047 -fno-builtin-printf -fno-builtin-snprintf -fno-builtin-vsnprintf -fno-builtin-log -fno-builtin-log2 -fno-builtin-malloc -O2 -pipe -nostdinc -I../../../.. -I. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM_SWAP_ENCRYPT -DCOMPAT_43 -DCOMPAT_O51 -DCOMPAT_O53 -DLKM -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DSOCKET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DINET -DALTQ -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DKVM86 -DUSER_LDT -DAPERTURE -DCOMPAT_LINUX -DPROCFS -DNTFS -DHIBERNATE -DPCIVERBOSE -DEISAVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE -DMAXUSERS=80 -D_KERNEL -MD -MP -c ../../../../arch/i386/pci/pci_machdep.c ../../../../arch/i386/pci/pci_machdep.c: In function 'pci_intr_map_msi': ../../../../arch/i386/pci/pci_machdep.c:604: error: 'mp_busses' undeclared (first use in this function) ../../../../arch/i386/pci/pci_machdep.c:604: error: (Each undeclared identifier is reported only once ../../../../arch/i386/pci/pci_machdep.c:604: error: for each function it appears in.) *** Error 1 in /usr/src/sys/arch/i386/compile/ob800 (Makefile:566 'pci_machdep.o') I suppose something got disabled which was a required dependency of something else? What could it be? Question two: option APERTURE# in-kernel aperture driver for XFree86 I suppose I can disable this, since this machine is pci only and has no AGP, right? Riccardo
Re: nsd sendto failure - how to debug?
On 13-12-24 08:46 AM, Stuart Henderson wrote: Is there any chance you receive (and try to reply to) packets with bogus source addresses (spoofed/non-reachable, or packets which should have been natted but weren't)? I would also keep an eye on output of 'route -n monitor' and look for instability there (e.g. RTM_MISS messages). There should be absolutely nothing happening routing-wise on my nameservers. They each have a single interface (one has em0, one has vio0), and a common carp0 on top of that. They have one default IPv4 route and one default IPv6 route. I do see the occasional RTM_ADD relating to (I think) ARP and/or NDP activity, but that's it so far... I'll leave it running. It's certainly possible my routers could pass on spoofed packets; the nameservers sit directly behind my border routers. (URPF isn't really an option for BGP routers with multiple sessions...) There's one NAT'd private address space in use, but the routers have static routes for it to bypass the NAT function, and in any event that wouldn't generate an EHOSTUNREACH. Oh, for !@#$!@#%!%. I just found the problem. My IPv6 default route was missing. Looks like I added it manually, but forgot to add it to /etc/mygate. Of course, I then rebooted at some point in the last few weeks... My original complaint stands: If the error message had contained the failing destination address, I would have noticed my error almost immediately. (Since presumably all the failures were for globally-routeable IPv6 addresses.) Sorry for all the noise :-( -- -Adam Thompson athom...@athompso.net
Re: dmassage - openbsd 5.4 build failure
On Wed, Dec 25, 2013, at 08:25 AM, Riccardo Mottola wrote: > Hi, > > prompted by the quest of a smaller kernel on my old OmniBook 800 (for > which memory modules are harder to find than a standard laptop), I tried > my luck with dmassage against a stock GENERIC 5.4 kernel conf. > > I used the generated config fil, except that I enabled a couple of more > PCMCIA drivers, which are of course all disabled except the currently > inserted card. What I found is as of a few versions ago, I forget exactly when, dmassage by itself will generate a busted kernel config now. Basically, to have a working kernel you need to compile in certain drivers, even if they not show up in the dmesg. Unfortunately I've forgotten which ones they were and I don't have a system I can experiment on... -- Shawn K. Quinn skqu...@rushpost.com
Re: netstat segfault on -current
On Mon, Dec 23, 2013 at 11:51 PM, Kenneth R Westerback wrote: > It is a real issue, due to errors I made replacing CIRCLEQ with TAILQ. > > A fix is being worked on, and a workaround probably sooner than that. Looks like the recent updates have resolved the issue. Thanks!
Re: dmassage - openbsd 5.4 build failure
Shawn K. Quinn wrote: On Wed, Dec 25, 2013, at 08:25 AM, Riccardo Mottola wrote: Hi, prompted by the quest of a smaller kernel on my old OmniBook 800 (for which memory modules are harder to find than a standard laptop), I tried my luck with dmassage against a stock GENERIC 5.4 kernel conf. I used the generated config fil, except that I enabled a couple of more PCMCIA drivers, which are of course all disabled except the currently inserted card. What I found is as of a few versions ago, I forget exactly when, dmassage by itself will generate a busted kernel config now. Basically, to have a working kernel you need to compile in certain drivers, even if they not show up in the dmesg. Unfortunately I've forgotten which ones they were and I don't have a system I can experiment on... For example: mpbios0 at bios0 I tried, but it is not enough... Riccardo
Re: Unable to associate with wifi AP until channel changed on AP
> Sorry for late answer - had some problems with my ISP. > > On Sunday 22 December 2013 01:42:09 electronmuontau neutrino wrote: > > I have two machines configured as wifi access points that use the > > athn(4) driver. One is an Acer Aspire One D250 and the other is an > > ALIX.2D13 with a Compex WLM200NX Atheros 802.11 a/b/g/n miniPCI > > card. Both have OpenBSD 5.4 release installed. I've been able to > > reproduce the problem reliably on both. The following is one > > procedure I used to test the problem: > > > > -boot machine with athn down > > > > $ ifconfig athn0 > > athn0: flags=8802 mtu 1500 > > lladdr: xx:xx:xx:xx:xx:xx > > priority: 4 > > groups: wlan > > media: IEEE802.11 autoselect > > status: no network > > ieee80211: nwid "" > > $ sudo ifconfig athn0 inet 192.168.2.1 255.255.255.0 nwid > > 1234567890 wpakey keykeykey mediaopt hostap > > $ ifconfig athn0 > > athn0: flags=8843 mtu > > 1500 lladdr: xx:xx:xx:xx:xx:xx > > priority: 4 > > groups: wlan > > media: IEEE802.11 autoselect (autoselect hostap) > > status: active > > ieee80211: nwid 1234567890 chan 3 bssid xx:xx:xx:xx:xx:x: > > wpakey wpaprotos wpa1, wpa2 wpaakms psk wpaciphers > > tkip, ccmp wpagroupcipher tkip > > inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 > > inet6 ::xxx:::%athn0 pfrefixlen 64 scopeid > > 0x1 > > > > -edit dhcpd.conf and run dhcpd daemon > > $ sudo /usr/sbin/dhcpd athn0 > > > > -attempt to associate from MacOSX and WinXP machines > > -not able to see nwid on WinXP after refreshing list multiple > > times -can see nwid on MacOSX, but connection times out when trying > > to associate > > > Down to here you are sending on 5120MHz, right? I don't know. How would you determine that? > > > -change channel on access point > > $ sudo ifconfig athn0 chan 7 > Now you switch to 2.4GHz - right? > > > > > -association with AP is successful from MacOSX and WinXP machines > > now and IP addresses are assigned > WinXP machine might not work with 5GHz? > > Are the antennas suitable for 5GHz? What about signal strength? > On the MAC it might be useful to install a WiFi scanner which will > tell you all about signal strength. > There is a free program called "Wifi Scanner" in the AppleStore. It is > very useful. The antennas I used were from PCEngines - listed as antsma on their website. antsma - Antenna for 2.4 GHz band, 5 dBi nominal gain. Reverse SMA connector. They do have another antenna, antsmadb, that is dual band which I don't have. antsmadb - Antenna for 2.4 GHz and 5 GHz band, 5 dBi peak gain in 2.4 GHz band. Reverse SMA connector. I don't think signal strength was an issue because I tested with each AP next to the Mac and Windows machines and still had the same result. > > I can't help with the COMPEX miniPCI 'cause I got another brand on my > Alix 2D13. But I realized that signal strength with 5GHz can be > significantly lower than with 2.4GHz using antennas which are meant to > work on both bands. > > Just my 2 c > > > > Acer Aspire One D250 > > athn0 at pci1 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 4 int > > 16 athn0: AR9280 rev 2 (2T2R), ROM rev 22, address > > xx:xx:xx:xx:xx:xx > > > > Alix 2D13 > > athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9 > > athn0: AR9280 rev 2 (2T2R), ROM rev 22, address xx:xx:xx:xx:xx:xx > Some might like to see a complete dmesg of this setup [hint-hint] > > > > Has anyone else encountered this? Please let me know if more info > > is needed. > > Cheers > Eike
