Hi @misc,
I have a Beagleboard-xM with Ansgtrom Linux and a PC running OpenBSD 4.8, AMD64 version. My PC is connected via TP-Link wifi to household router (my otus0 internet address for this connection is 192.168.1.101). The beagleboard is connected to the PC via ethernet.
On the Beagle I configured the ethernet device (which shows up as usb0 on Angstrom):

# ifconfig usb0 inet 192.168.10.10 netmask 255.255.255.0
# route add default gw 192.168.10.12 netmask 255.255.255.0 dev usb0
Also, in /etc/resolv.conf I added nameservers 203.12.160.35 & 203.12.160.36

On the OpenBSD PC I created a bridge:

# ifconfig nfe0 inet 192.168.10.12 netmask 255.255.255.0
# ifconfig bridge0 create
In /etc/hostname.nfe0 is the single word: up
In /etc/hostname.otus0 is the single word: up
In /etc/bridgename.bridge0 is: add nfe0 add otus0 up
In /etc/sysctl.conf I uncommented: net.inet.ip.forwarding=1

I have also tried uncommenting net.inet6.ip6.mforwarding=1 but it did not help.

I can ping 192.168.10.12 from the Beagle, and 192.168.10.10 from the PC, but I cannot ping 192.168.1.101 (the PC's wifi connection from the Beagle, "network is unreachable").
The first time I set this up (a few days ago), I could ping the outside world from the Beagle running Angstrom. I loaded Ubuntu onto the Beagle tried the setup again, and could not reach the outside internet. Now I've gone back to Angstrom and cannot get the connection to come back up. I am not sure why it worked before and not now but it seems like my OpenBSD bridge0 is not working. When it was working, typing ifconfig (as below) I seem to remember the output for bridge0 was longer than it is now, but am not sure. Probably it is some simple forgotten command but I do not know what it could be.

Thanks for any help!
Brett.

More detailed output:

------------------------------------------------------------------------
On the OpenBSD pc:

# ifconfig nfe0 inet 192.168.10.12 netmask 255.255.255.0
# ifconfig bridge0 create
# ifconfig                           ...
[ message continues ]

AMD64 version. My PC is connected via TP-Link wifi to household router (my
otus0 internet address for this connection is 192.168.1.101). The beagleboard
I cannot ping 192.168.1.101 (the PC's wifi connection from the Beagle,
world from the Beagle running Angstrom. I loaded Ubuntu onto the Beagle tried
the setup again, and could not reach the outside internet. Now I've gone back
to Angstrom and cannot get the connection to come back up. I am not sure why
it worked before and not now but it seems like my OpenBSD bridge0 is not
working. When it was working, typing ifconfig (as below) I seem to remember
the output for bridge0 was longer than it is now, but am not sure. Probably it
0x075ce6504c26846e32c144a71a0f7840988b9a8e9d4a7593243d4dfae845032e wpaprotos
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------

If a DHCP server is on the 192.168.1.0/24 block, you could configure
your beagleboard to get an address through DHCP, since you set up the
bridge.

If you're using a bridge, you don't need to set
"net.inet.ip.forwarding" to 1, as you aren't actually routing packets,
you're bridging them.
(see http://www.openbsd.org/faq/faq6.html#Bridge)

--AlanCF

[ message continues ]

But since the 192.168.1.0 network is unreachable I don't think the dhcp
request would get through anyway....

[ message continues ]

Don't set a netmask on your default route. You're adding a route for
usb0

Shows up right there on the "default" line.

A default route should have a Genmask of 0.0.0.0 (says so in the man page).

All the IRB/CRB nonsense is just distracting.

--
Jon

[ message continues ]

If you were to do routing, and wanted to use a seperate block of
addresses (from 192.168.1.0/24), besides the Linux box's config, and
the OpenBSD box's config, you'd have to modify the configuration in
192.168.1.0/24 's router with static routes to the OpenBSD box (most
SOHO routers don't support this). If you were to try to use some
addresses under the 192.168.1.0/24 block, you'd have to either add a
In my opinion, bridging is the most efficient way of accomplishing the
task (getting acccess to the wireless network through a computer

--AlanCF

[ message continues ]

You must use either WDS or hostap to bridge 802.11 interfaces
to wired interfaces, there are not spaces for enough MAC addresses
in the standard 802.11 frames to handle bridging. (OpenBSD doesn't
support WDS).

Some commercial wireless devices support a 'client-bridge' mode
without WDS; this uses something which can basically be described
as a layer-2 NAT.

To do this using OpenBSD I would suggest just doing standard

Nor am I.

[ message continues ]

Thanks for the help, everyone. I am traveling so will try these
suggestions in a week or two when I get home. Silence means successful
execution, otherwise I'll be back!
Merry xmas to question answerers and the OpenBSD team!

[ message continues ]