openvpn in rdomain hangs
hi misc, i'm trying to run OpenBSD with two default gateways, one for openvpn and another for everything else. openvpn is in rdomain 1 and everything works fine. OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb 3 07:57:32 MST 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP # cat hostname.em1 !echo "starting em1" rdomain 1 group vpn inet yy.yy.yy.yy/28 !/sbin/route -T 1 add default yy.yy.yy.default !echo -n "starting sshd in rdomain 1" !route -T 1 exec /etc/rc.d/sshd start && echo "." !echo -n "starting openvpn in rdomain 1" !install -d -o _openvpn -g _openvpn -m 0755 /var/run/openvpn && /sbin/route -T 1 exec /usr/local/sbin/openvpn --daemon --config /etc/openvpn/server.conf && echo "." # cat hostname.tun0 !echo "starting tun0" up 10.100.16.1 10.100.16.2 netmask 0x !route add 10.100.16.0/24 10.100.16.2 however, openvpn cannot be restarted in multi-user mode. it hangs in get_default_gateway(). http://www.openssh.com/cgi-bin/cvsweb/ports/net/openvpn/patches/patch-src_openvpn_route_c?rev=1.2;content-type=text%2Fplain ktrace shows that read(2) to routing socket does not return. 10068 openvpn CALL socket(PF_ROUTE,SOCK_RAW,0) 10068 openvpn RET socket 3 10068 openvpn CALL sigprocmask(SIG_BLOCK,~0<>) 10068 openvpn RET sigprocmask 0<> 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x3) 10068 openvpn RET mprotect 0 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x1) 10068 openvpn RET mprotect 0 10068 openvpn CALL sigprocmask(SIG_SETMASK,0<>) 10068 openvpn RET sigprocmask ~0x10100 10068 openvpn CALL write(0x3,0x10ee1949c0,0x80) 10068 openvpn GIO fd 3 wrote 128 bytes "\M^@\0\^E\^D\0\0\0\0\0\0\0\0\^E\0\0\0\^C\0\0\0\0\0\0\0\0\0\0\0\^A\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\ \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^P\^B\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^P\^B\ \0\0\0\0\0\0\0\0\0\0\0\0\0\000" 10068 openvpn RET write 128/0x80 10068 openvpn CALL sigprocmask(SIG_BLOCK,~0<>) 10068 openvpn RET sigprocmask 0<> 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x3) 10068 openvpn RET mprotect 0 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x1) 10068 openvpn RET mprotect 0 10068 openvpn CALL sigprocmask(SIG_SETMASK,0<>) 10068 openvpn RET sigprocmask ~0x10100 10068 openvpn CALL read(0x3,0x10ee1949c0,0x260) when invoked from hostname.em1 during boot, read(2) immediately returned with ESRCH. according to route(4), messages written to the socket should be returned. how can read(2) be blocked? the behavior is same on 5.4, 5.3 and current. -- Tomoyuki Sakurai
Re: erlang : manpages : inaccessible
On Tue, Feb 04, 2014 at 06:49:33PM -0600, Matthew Weigel wrote: > [...] > I believe you should be using "man erlang " with that configuration. > [...] The correct form is for example erl -man time -- Gregor Best -- I never met a piece of chocolate I didn't like.
Re: dhclient
Am 03.02.2014 17:54, schrieb Kenneth Westerback:
Reactivating the dhclient-script is not going to happen.
I am interested in what you would see syntax in dhclient.conf looking like.
Would multi-path routing modifications to all routes be needed? How should this
be combined with supersede/default/append commands for the relevant
options? Would it apply to all members of each option, or route by
route?
If all else fails you can always use the ISC dhclient from ports to
gain access to a dhclient-script again.
Ken
On 31 January 2014 02:04, Holger Glaess wrote:
Am 30.01.2014 13:10, schrieb Giancarlo Razzolini:
Em 29-01-2014 18:13, Holger Glaess escreveu:
hi
i try to setup and multipath configuration with 2 line provider
1 cable with dhcp(client)
1 with pppoe
just dynamic ips.
the pppoe config create well the new default route with -math
but dhclient dont.
[snip pppoe config]
inet 0.0.0.0 255.255.255.255 NONE \
pppoedev msk0 authproto pap \
authname 'bla@blub' authkey 'blub' up
dest 0.0.0.1
!/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
[/snip pppoe config]
after a couple of days i found that the dhclient not use the
dhclient-script since 5.3 anymore.
so how can i setup the -math option at the dhclient config ?
or it is possible to add some lines in dhclient that he check the
sysctl and , if net.inet.ip.multipath=1 ,
he add the default route with ( for ) multipathing.
holger
Check if your dhcp server always gives you the same router ip address.
If so, you can tweak with your dhclient.conf to reject and not ask for
routers, and then set it up manually as you do in your hostname.pppoe0.
And you can always run a script that is run after the dhcp negotiation,
looks for the gateway related entry, deletes it and then re-adds it with
the mpath modifier. There are a lot of options in this regard.
Cheers,
hi
shure , i can write a wrap around solution for the but this not the
"dynamic" way like
pppoe or dhcp to get and set ips.
i'm not the C programmer but i think it is not mutch work to add a solution
in dhclient,
or as option to reaktivate the dhclient-script part.
holger
hi
at moment i have following setup
# cat hostname.pppoe0
inet 0.0.0.0 255.255.255.255 NONE \
pppoedev msk0 authproto pap \
authname 'bla' authkey 'blub' up
dest 0.0.0.1
#!/sbin/route add default -ifp pppoe0 0.0.0.1
#!/sbin/route add -inet6 default -ifp pppoe0 ::0.0.0.1
#
!/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
!/sbin/route add -inet6 -mpath default -ifp pppoe0 ::0.0.0.1
# cat /etc/hostname.vlan5
dhcp vlandev msk1
!/sbin/route add -mpath default xww.x.yy.zz.
# cat /etc/dhclient.conf
timeout 15;
retry 5;
reboot 2;
select-timeout 5;
initial-interval 2;
interface "vlan5" {
ignore domain-name-servers;
ignore host-name;
ignore routers;
send dhcp-lease-time 3600;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name-servers, host-name, ntp-servers;
}
it work for a while with the mpath settings after the start but if the
dhclient renew his setting he set the default route
i his standard way , hi ignore the settings in his config ( is this
right ? )
holger
Missing fclose() in some utilities - worth fixing?
Hi list, I'm currently trying to get familiar with OpenBSD source code and I've noticed that there are fclose() function calls missing sometimes. (e.g. usr.bin/awk/maketab.c, usr.sbin/smtpd/table_passwd.c). I'd like to ask whether these files are intended to be closed by operating system when the utility exits or fclose() calls just has been forgotten. My personal view is that program should always call free, fclose and such even when exiting immediately after. For purpose of clean and transparent code and logic and for purpose of code reusability. But perhaps there are some reasons not to do that I'm missing. Thanks, P. Winter
Re: Missing fclose() in some utilities - worth fixing?
On Wed, Feb 05, 2014 at 12:56:20PM +0100, Paul Winter wrote: > Hi list, > Hi, > I'm currently trying to get familiar with OpenBSD source code and I've > noticed > that there are fclose() function calls missing sometimes. (e.g. > usr.bin/awk/maketab.c, usr.sbin/smtpd/table_passwd.c). > Where do you think a fclose() is missing in table_passwd.c and maketab.c ? As far as table_passwd.c is concerned, I read the file again and don't see a fp leak there. > I'd like to ask whether these files are intended to be closed by operating > system when the utility exits or fclose() calls just has been forgotten. > When a utility exits, we don't necessarily release resources because they are unallocated by the operating system, it would add useless code. > My personal view is that program should always call free, fclose and such > even when exiting immediately after. For purpose of clean and transparent > code and logic and for purpose of code reusability. But perhaps there are > some reasons not to do that I'm missing. > Well, first of all it's redundant as said above, as for clean and transparent code since you're exiting anyway the need for bookkeeping isn't that valuable. Furthermore, I think it was Theo who explained this a while ago, but if for example you are following an error path because someone managed to corrupt your allocator's internal state, the last thing you want to do is call free() in your error path to give him another chance at exploiting the situation. -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: Missing fclose() in some utilities - worth fixing?
On Wed, Feb 05, 2014 at 12:56, Paul Winter wrote: > Hi list, > > I'm currently trying to get familiar with OpenBSD source code and I've > noticed > that there are fclose() function calls missing sometimes. (e.g. > usr.bin/awk/maketab.c, usr.sbin/smtpd/table_passwd.c). > > I'd like to ask whether these files are intended to be closed by operating > system when the utility exits or fclose() calls just has been forgotten. > > My personal view is that program should always call free, fclose and such > even when exiting immediately after. For purpose of clean and transparent > code and logic and for purpose of code reusability. But perhaps there are > some reasons not to do that I'm missing. For functions other than main, I agree. In main it's just clutter.
Re: dhclient
On 5 February 2014 06:35, Holger Glaess wrote:
> Am 03.02.2014 17:54, schrieb Kenneth Westerback:
>
>> Reactivating the dhclient-script is not going to happen.
>>
>> I am interested in what you would see syntax in dhclient.conf looking
>> like.
>>
>> Would multi-path routing modifications to all routes be needed? How should
>> this
>> be combined with supersede/default/append commands for the relevant
>> options? Would it apply to all members of each option, or route by
>> route?
>>
>> If all else fails you can always use the ISC dhclient from ports to
>> gain access to a dhclient-script again.
>>
>> Ken
>>
>> On 31 January 2014 02:04, Holger Glaess wrote:
>>>
>>> Am 30.01.2014 13:10, schrieb Giancarlo Razzolini:
>>>
Em 29-01-2014 18:13, Holger Glaess escreveu:
>
> hi
>
> i try to setup and multipath configuration with 2 line provider
>
> 1 cable with dhcp(client)
> 1 with pppoe
>
> just dynamic ips.
>
> the pppoe config create well the new default route with -math
> but dhclient dont.
>
> [snip pppoe config]
>
> inet 0.0.0.0 255.255.255.255 NONE \
> pppoedev msk0 authproto pap \
> authname 'bla@blub' authkey 'blub' up
> dest 0.0.0.1
> !/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
>
> [/snip pppoe config]
>
>
> after a couple of days i found that the dhclient not use the
> dhclient-script since 5.3 anymore.
>
>
> so how can i setup the -math option at the dhclient config ?
>
>
> or it is possible to add some lines in dhclient that he check the
> sysctl and , if net.inet.ip.multipath=1 ,
> he add the default route with ( for ) multipathing.
>
>
>
>
>
>
> holger
>
Check if your dhcp server always gives you the same router ip address.
If so, you can tweak with your dhclient.conf to reject and not ask for
routers, and then set it up manually as you do in your hostname.pppoe0.
And you can always run a script that is run after the dhcp negotiation,
looks for the gateway related entry, deletes it and then re-adds it with
the mpath modifier. There are a lot of options in this regard.
Cheers,
>>> hi
>>>
>>> shure , i can write a wrap around solution for the but this not the
>>> "dynamic" way like
>>> pppoe or dhcp to get and set ips.
>>>
>>> i'm not the C programmer but i think it is not mutch work to add a
>>> solution
>>> in dhclient,
>>> or as option to reaktivate the dhclient-script part.
>>>
>>>
>>> holger
>
> hi
>
> at moment i have following setup
>
> # cat hostname.pppoe0
>
> inet 0.0.0.0 255.255.255.255 NONE \
> pppoedev msk0 authproto pap \
> authname 'bla' authkey 'blub' up
> dest 0.0.0.1
> #!/sbin/route add default -ifp pppoe0 0.0.0.1
> #!/sbin/route add -inet6 default -ifp pppoe0 ::0.0.0.1
>
> #
> !/sbin/route add -mpath default -ifp pppoe0 0.0.0.1
> !/sbin/route add -inet6 -mpath default -ifp pppoe0 ::0.0.0.1
>
> # cat /etc/hostname.vlan5
> dhcp vlandev msk1
> !/sbin/route add -mpath default xww.x.yy.zz.
>
>
> # cat /etc/dhclient.conf
>
> timeout 15;
> retry 5;
> reboot 2;
> select-timeout 5;
> initial-interval 2;
>
>
> interface "vlan5" {
> ignore domain-name-servers;
> ignore host-name;
> ignore routers;
> send dhcp-lease-time 3600;
> request subnet-mask, broadcast-address, time-offset, routers,
> domain-name-servers, host-name, ntp-servers;
> }
>
>
> it work for a while with the mpath settings after the start but if the
> dhclient renew his setting he set the default route
> i his standard way , hi ignore the settings in his config ( is this right ?
> )
I've never tried mixing vlans and dhclient, so I'm not 100% sure what
the behaviour is going to be. :-)
If you can run dhclient from the command line, and specify the '-L' option and a
file location, I'd be interested in what the offered and effective
dhcp leases look
like. Also a tcpdump of the interaction could supply valuable
information. Again,
not sure of tcpdump vs vlan interfaces, but something like
tcpdump -i msk1 -s 2000 -w
running when you start dhclient should generate a useful file I can peruse.
After that I can send you some dhclient debugging diffs if necessary.
Ken
>
>
> holger
Re: Is [binary] package signing planned?
Em 04-02-2014 18:03, Marc Espie escreveu: > I *encourage* you guys to read signify and pkg_add code and poke holes > in them! I did read both last night. Signify is very easy and straightforward to understand. I wasn't really poking for holes, more for understanding than that. The pkg part is a lot more code and I didn't read them all yet. Cheers, -- Giancarlo Razzolini GPG: 4096R/77B981BC
urtw0 wpa2 working on Lemote?
Hi, with my lemote, I tried to connect to WPA2 secured network at work. Now I'm back at home, where I can connect without issues to my unsecured network. When scanning for WLAN networks using my amd64 notebook, I usually see different dB values, but here, every network is 143 dB signal strength. Is this a known limitation to the urtw driver? # ifconfig urtw0 scan urtw0: flags=8802 mtu 1500 lladdr 00:17:c4:5a:1f:d4 priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid "" 100dBm nwid brb.freifunk.net chan 1 bssid 00:11:09:9a:9a:7e 143dB 11M short_preamble nwid "FRITZ!Box Fon WLAN 7170" chan 6 bssid 00:1c:4a:d5:eb:16 143dB 54M privacy,short_slottime nwid "FRITZ!Box Fon WLAN 7240" chan 1 bssid 00:1f:3f:d1:48:d2 143dB 54M privacy,short_preamble,short_slottime nwid WLAN-6E1076 chan 6 bssid 88:25:2c:6e:10:91 143dB 54M privacy,short_preamble,short_slottime nwid "FRITZ!Box Fon WLAN 7320" chan 11 bssid bc:05:43:f8:e9:49 143dB 54M privacy,short_preamble,short_slottime nwid "Triple X" chan 11 bssid c0:25:06:2e:d6:7e 143dB 54M privacy,short_slottime nwid Demiurge chan 11 bssid e8:40:f2:16:5c:23 143dB 54M privacy,short_slottime Anyways, at work I specify the nwid and the wpakey like this: ifconfig urtw0 nwid MYID wpakey SECRETKEY up but status keeps telling me: no network however, the manual page tells me that WPA and WPA2 should work. any ideas? Sebastian # dmesg [ using 489112 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.5-beta (GENERIC) #2: Tue Feb 4 11:37:08 CET 2014 root@loong.ds9:/usr/src/sys/arch/loongson/compile/GENERIC real mem = 1073741824 (1024MB) avail mem = 1058816000 (1009MB) mainbus0 at root: Lemote Yeeloong cpu0 at mainbus0: STC Loongson2F CPU 797 MHz, STC Loongson2F FPU cpu0: cache L1-I 64KB D 64KB 4 way, L2 512KB 4 way bonito0 at mainbus0: memory and PCI-X controller, rev 1 pci0 at bonito0 bus 0 rl0 at pci0 dev 7 function 0 "Realtek 8139" rev 0x10: irq 5, address 00:23:8b:b5:37:62 rlphy0 at rl0 phy 0: RTL internal PHY smfb0 at pci0 dev 8 function 0 "Silicon Motion LynxEM+" rev 0xb0 wsdisplay0 at smfb0 mux 1: console (std, vt100 emulation) ohci0 at pci0 dev 9 function 0 "NEC USB" rev 0x44: irq 7, version 1.0 ehci0 at pci0 dev 9 function 1 "NEC USB" rev 0x05: irq 7 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1 glxpcib0 at pci0 dev 14 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c isa0 at glxpcib0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 mcclock0 at isa0 port 0x70/2: mc146818 or compatible ykbec0 at isa0 port 0x381/3 gpio1 at glxpcib0: 32 pins iic at glxpcib0 not configured glxclk0 at glxpcib0: clock, prof pciide0 at pci0 dev 14 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 4-sector PIO, LBA, 7815MB, 16007040 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) auglx0 at pci0 dev 14 function 3 "AMD CS5536 Audio" rev 0x01: isa irq 9, CS5536 AC97 ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0) audio0 at auglx0 ohci1 at pci0 dev 14 function 4 "AMD CS5536 USB" rev 0x02: isa irq 11, version 1.0, legacy support ehci1 at pci0 dev 14 function 5 "AMD CS5536 USB" rev 0x02: isa irq 11 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "AMD EHCI root hub" rev 2.00/1.00 addr 1 usb2 at ohci0: USB revision 1.0 uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1 usb3 at ohci1: USB revision 1.0 uhub3 at usb3 "AMD OHCI root hub" rev 1.00/1.00 addr 1 apm0 at mainbus0 umass0 at uhub1 port 1 configuration 1 interface 0 "Generic USB2.0-CRW" rev 2.00/58.87 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI0 0/direct removable serial.0bda015811417340 urtw0 at uhub1 port 4 "Realtek RTL8187B" rev 2.00/2.00 addr 3 urtw0: RTL8187B rev E, address 00:17:c4:5a:1f:d4 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets pmon bootpath: /dev/disk/wd0 boot device: wd0 root on wd0a (4ce70288f4ecaf0f.a) swap on wd0b dump on wd0b
Re: openvpn in rdomain hangs
Em 05-02-2014 07:09, Tomoyuki Sakurai escreveu: > hi misc, > > i'm trying to run OpenBSD with two default gateways, one for openvpn and > another for everything else. openvpn is in rdomain 1 and everything works > fine. > > OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb 3 07:57:32 MST 2014 > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > # cat hostname.em1 > !echo "starting em1" > rdomain 1 > group vpn > inet yy.yy.yy.yy/28 > !/sbin/route -T 1 add default yy.yy.yy.default > !echo -n "starting sshd in rdomain 1" > !route -T 1 exec /etc/rc.d/sshd start && echo "." > !echo -n "starting openvpn in rdomain 1" > !install -d -o _openvpn -g _openvpn -m 0755 /var/run/openvpn && > /sbin/route -T 1 exec /usr/local/sbin/openvpn --daemon --config > /etc/openvpn/server.conf && echo "." > > # cat hostname.tun0 > !echo "starting tun0" > up > 10.100.16.1 10.100.16.2 netmask 0x > !route add 10.100.16.0/24 10.100.16.2 > > however, openvpn cannot be restarted in multi-user mode. it hangs in > get_default_gateway(). > > http://www.openssh.com/cgi-bin/cvsweb/ports/net/openvpn/patches/patch-src_openvpn_route_c?rev=1.2;content-type=text%2Fplain > > ktrace shows that read(2) to routing socket does not return. > > 10068 openvpn CALL socket(PF_ROUTE,SOCK_RAW,0) > 10068 openvpn RET socket 3 > 10068 openvpn CALL sigprocmask(SIG_BLOCK,~0<>) > 10068 openvpn RET sigprocmask 0<> > 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x3) > 10068 openvpn RET mprotect 0 > 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x1) > 10068 openvpn RET mprotect 0 > 10068 openvpn CALL sigprocmask(SIG_SETMASK,0<>) > 10068 openvpn RET sigprocmask ~0x10100 > 10068 openvpn CALL write(0x3,0x10ee1949c0,0x80) > 10068 openvpn GIO fd 3 wrote 128 bytes > > "\M^@\0\^E\^D\0\0\0\0\0\0\0\0\^E\0\0\0\^C\0\0\0\0\0\0\0\0\0\0\0\^A\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\ > > \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^P\^B\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^P\^B\ > \0\0\0\0\0\0\0\0\0\0\0\0\0\000" > 10068 openvpn RET write 128/0x80 > 10068 openvpn CALL sigprocmask(SIG_BLOCK,~0<>) > 10068 openvpn RET sigprocmask 0<> > 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x3) > 10068 openvpn RET mprotect 0 > 10068 openvpn CALL mprotect(0x10ee093000,0x2000,0x1) > 10068 openvpn RET mprotect 0 > 10068 openvpn CALL sigprocmask(SIG_SETMASK,0<>) > 10068 openvpn RET sigprocmask ~0x10100 > 10068 openvpn CALL read(0x3,0x10ee1949c0,0x260) > > when invoked from hostname.em1 during boot, read(2) immediately returned with > ESRCH. according to route(4), messages written to the socket should be > returned. how can read(2) be blocked? > the behavior is same on 5.4, 5.3 and current. > I've used rdomains, but not for this. In this case I would use mpath and pf only. I really do not see the need for using rdomains in this case. It introduces too much complexity for a simple thing. Cheers, -- Giancarlo Razzolini GPG: 4096R/77B981BC
Re: urtw0 wpa2 working on Lemote?
Sebastian Reitenbach l00-bugdead-prods.de> writes: > Anyways, at work I specify the nwid and the wpakey like this: > > ifconfig urtw0 nwid MYID wpakey SECRETKEY up > > but status keeps telling me: no network > however, the manual page tells me that WPA and WPA2 should work. from ifconfig(8): wpakey passphrase | hexkey Set the WPA key and enable WPA. The key can be given using either a passphrase or a full length hex key, starting with 0x. If a passphrase is used the nwid option must be set prior to specifying the wpakey option, since ifconfig will hash the nwid along with the passphrase to create the key.
Intermittent stops in network traffic with urtw interface
Hello, I have an Alfa AWUS036H USB wi-fi adapter that I am using on OpenBSD 5.4 amd64. Problem is, sometimes as often as every 15 minutes, the only way to get the interface to pass traffic is with 'ifconfig urtw0 down && ifconfig urtw0 up'. I've monitored the traffic with tcpdump to look for a pattern as to when it stops passing traffic, but I have not been able to find one. At the tail of dmesg output the following messages are repeated: usb_insert_transfer: xfer=0x80568000 not busy 0x4f4e5155 urtw0: could not send frame: INVAL I am getting a 70-80 dB signal according to ifconfig, which is not ideal, but should by no means be unusable. I have used the interface with media set to DS1 mode 11g and OFDM54 mode 11g, with the same behavior. I am using WPA2-PSK to authenticate to the access point (a Verizon router). dmesg.boot has the following lines for the device: urtw0 at uhub0 port 4 "Realtek RTL8187" rev 2.00/1.00 addr 2 urtw0: RTL8187 rev 0x04, RFv2, address 00:c0:ca:75:31:85 urtw0 at uhub0 port 4 "vendor 0x0bda RTL8187_Wireless" rev 2.00/1.00 addr 2 urtw0: RTL8187 rev 0x04, RFv2, address 00:c0:ca:75:31:85 urtw0: expect 0xe6!! (0xd2) Is there any way in which I can troubleshoot this? It's becoming a bit frustrating, but I'd like to keep using OpenBSD! I'm a bit lost at this point as to how to approach this issue further, so hopefully someone may be able to point me in the right direction. Let me know if any additional information would be of help. Thanks! -Brian
Re: Intermittent stops in network traffic with urtw interface
Brian Curran brianpcurran.com> writes: > > Hello, > > I have an Alfa AWUS036H USB wi-fi adapter that I am using on OpenBSD > 5.4 amd64. Problem is, sometimes as often as every 15 minutes, the only way to > get the interface to pass traffic is with 'ifconfig urtw0 down && > ifconfig urtw0 up'. I've monitored the traffic with tcpdump to look for > a pattern as to when it stops passing traffic, but I have not been able > to find one. when it stops passing traffic, does issuing "ifconfig urtw0 scan" help?
Re: Intermittent stops in network traffic with urtw interface
On Wed, Feb 05, 2014 at 10:51:19PM +, Alexey Suslikov wrote: > Brian Curran brianpcurran.com> writes: > > > > > Hello, > > > > I have an Alfa AWUS036H USB wi-fi adapter that I am using on OpenBSD > > 5.4 amd64. Problem is, sometimes as often as every 15 minutes, the only way > to > > get the interface to pass traffic is with 'ifconfig urtw0 down && > > ifconfig urtw0 up'. I've monitored the traffic with tcpdump to look for > > a pattern as to when it stops passing traffic, but I have not been able > > to find one. > > when it stops passing traffic, does issuing "ifconfig urtw0 scan" help? > I test this just now and it seemed to help, although I only started seeing ping replies about 10 seconds after issuing the scan. There is a similar small delay, though usually not as long, when bringing the interface down then up. Also maybe of note is that the status of the interface as reported by ifconfig remains "active" when it is not receiving any traffic.
