I should also note my instructions prefer the use of wired interfaces, but in the past I haven't noticed bridging with a wlan is a big problem, other than issues with wireless authorization. It seems like it should be easy, but for some reason it isn't working.

If it helps, please refer to my instructions at http://nincehelser.com/ipwx

The instructions for bridging seem to work fine for older Pi's, but not newer.

Yes. It's Raspbian Wheezy on both the original Pi and the Pi 2.. As far as I know, the hardware shouldn't matter, but I'm wondering if some difference in the kernel is at play. From my understanding it was re-compiled to take advantage of the quad-core processor. Perhaps it was re-compiled with diff...

auto lo br0 iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet manual iface eth1 inet manual iface br0 inet dhcp bridge_ports eth0 wlan0 auto wlan0 allow-hotplug wlan0 iface wlan0 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf Note that I have an eth1 (a wired etherne...

On my older Pi (model B) I had no problems bridging eth0 and wlan0. Worked fine with bridge-utils. It was simple and straightforward. However, when I try to bridge the same way on a new Pi 2, it doesn't work. It looks like the bridge is created, but it can't get an address via dhcp. I'm using the sa...

Oh, a new observation.

If I wait about 2 minutes, the buffers flush and the output I want comes bursting through.

However, I'd like something more real-time. If I could get the buffers to flush every 18 seconds or so, that would be timely enough.

Thanks for the reply. I've also come to the conclusion that it's a buffer issue combined with very low traffic. One possible work-around I've found is if I let tcpdump only a few packets (using -c) , process the output, then loop back and catch a few more. Given the low traffic, I can probably get a...

I'm trying to use tcpdump to monitor network traffic for port 80. I'm passing the output of tcpdump through strings so that I only see the readable text. This all seems to be working fine with this command: sudo tcpdump -ieth0 -s0 -w - tcp dst port 80 | strings The problem is I can't seem to capture...