cannot get output from pflow on openbsd v. 5.8 amd64

[Imre Oolberg]

Hi!

I have used pflow 5 successfully before but now on OpenBSD v. 5.8 it 
seems to refuse working. Config looks like this


# cat /etc/hostname.pflow0
flowsrc 192.168.10.125 flowdst 192.168.10.250:9784 pflowproto 5 
description "pflow"


and i start it with (also tried to start manually as man pflow says)

# sh /etc/netstart pflow0

As a result new pflow0 interface appears

# ifconfig pflow0
pflow0: flags=41 mtu 1492
description: pflow
priority: 0
pflow: sender: 192.168.10.125 receiver: 192.168.10.250:9784 
version: 5

groups: pflow

but there isnt seen any associated traffic with dst port 9784 and also, 
tcpdump says


# tcpdump -ni pflow0
tcpdump: Failed to open bpf device for pflow0: Device not configured

Maybe i miss here something obvious and i would be thankful for 
directions. This happens on a ordinary 64 bit PC with 'amd64'.



Best regards,

Imre

Re: Add Bay Trail EHCI controller to pcidevs

[Martin Pieuchot]

On 06/12/15(Sun) 20:44, Callum Davies wrote:
> Doesn't work, but at least it makes the dmesg look better.

What doesn't work?

> 
> Index: sys/dev/pci/pcidevs
> ===
> RCS file: /cvs/src/sys/dev/pci/pcidevs,v
> retrieving revision 1.1780
> diff -u -p -u -r1.1780 pcidevs
> --- sys/dev/pci/pcidevs 28 Nov 2015 14:11:33 -  1.1780
> +++ sys/dev/pci/pcidevs 6 Dec 2015 20:38:06 -
> @@ -3102,6 +3102,7 @@ product INTEL BAYTRAIL_LPA0x0f28  Bay Tr
>  product INTEL BAYTRAIL_IGD_1   0x0f31  Bay Trail Video
>  product INTEL BAYTRAIL_IGD_2   0x0f32  Bay Trail Video
>  product INTEL BAYTRAIL_IGD_3   0x0f33  Bay Trail Video
> +product INTEL BAYTRAIL_EHCI0x0f34  Bay Trail EHCI
>  product INTEL BAYTRAIL_XHCI0x0f35  Bay Trail xHCI
>  product INTEL BAYTRAIL_82370x0f40  Bay Trail I2C DMA
>  product INTEL BAYTRAIL_I2C_1   0x0f41  Bay Trail I2C

pax: pledge: Invalid argument

[Sonic]

-current not building:

./icdb.h -> ./icdb.ph
pax: pledge: Invalid argument
*** Error 1 in gnu/usr.bin/perl (Makefile.bsd-wrapper:112 'install')
*** Error 2 in gnu/usr.bin (:48 'realinstall')
*** Error 2 in gnu (:48 'realinstall')
*** Error 2 in . (:48 'realinstall')
*** Error 2 in /usr/src (Makefile:82 'build')

Re: pax: pledge: Invalid argument

[Theo de Raadt]

Your mistake.

I recommend upgrading to a snapshot.

> 
> -current not building:
> 
> ./icdb.h -> ./icdb.ph
> pax: pledge: Invalid argument
> *** Error 1 in gnu/usr.bin/perl (Makefile.bsd-wrapper:112 'install')
> *** Error 2 in gnu/usr.bin (:48 'realinstall')
> *** Error 2 in gnu (:48 'realinstall')
> *** Error 2 in . (:48 'realinstall')
> *** Error 2 in /usr/src (Makefile:82 'build')

Re: which in /dev/* for tethering to android?

[luke350]

On 11/28/15 15:15, Jiri B wrote:

On Sat, Nov 28, 2015 at 03:07:15PM -0700, luke...@onemodel.org wrote:

I'd like to get an internet connection via my android phone (on
tmobile).  After connecting the phone via usb and turning on its
tethering option, I see the usb info in dmesg, but when I try to run
the pppd chat script it doesn't get any response from the phone.


Why do you do this? urndis is like ethernet iface, it is you phone
which establishes connection and acts as a gateway for your laptop.


Thanks.  It seems the key part I didn't realize was where 'man urndis'
mentions 'man ifconfig', which in turn mentions the hostname.if file:
It seems that I needed to create that file, with one line
saying 'dhcp' in it.  Maybe it would have been easier if 'man ifconfig'
said something like:  "If a device was not already automatically
created, see 'man hostname.if' for details."  So to that point it might
be good now, on the laptop side.

But it disconnects after a couple of minutes, with android saying
something about can't connect to data, but maybe that's something to do
with android and I need to get a later cyanogenmod release and see if
that helps, or something else phone-related.  (The data plan works fine
w/ the built-in android browser.)

I probably won't be able to work on this more now, for a while. I'm
sending the reply in case anyone else gets stuck at the same point as I
did.

Thanks for the kind help.

-Luke

Re: pax: pledge: Invalid argument

[Sonic]

On Mon, Dec 7, 2015 at 2:41 PM, Theo de Raadt  wrote:
> Your mistake.

Yes, my mistake. Sorry for the noise.