Re: IP bridge was briefly working now is not, OpenBSD 4.8, amd64, bridge from PC wifi to Beagleboard
lo0 localhost localhost UH140 33160 4 lo0 ::127.0.0.0/104localhost UGRS 00 - 8 lo0 ::224.0.0.0/100localhost UGRS 00 - 8 lo0 ::255.0.0.0/104localhost UGRS 00 - 8 lo0 :::0.0.0.0/96 localhost UGRS 00 - 8 lo0 2002::/24 localhost UGRS 00 - 8 lo0 2002:7f00::/24 localhost UGRS 00 - 8 lo0 2002:e000::/20 localhost UGRS 00 - 8 lo0 2002:ff00::/24 localhost UGRS 00 - 8 lo0 fe80::/10 localhost UGRS 10 - 8 lo0 fe80::%nfe0/64 link#2 UC 00 - 4 nfe0 fe80::225:11ff:fe1 00:25:11:1e:44:93 HL 00 - 4 lo0 fe80::%lo0/64 fe80::1%lo0U 00 - 4 lo0 fe80::1%lo0link#4 UHL00 - 4 lo0 fe80::%otus0/64link#7 UC 00 - 4 otus0 fe80::da5d:4cff:fe d8:5d:4c:8e:b8:29 UHL00 - 4 lo0 fec0::/10 localhost UGRS 00 - 8 lo0 ff01::/16 localhost UGRS 00 - 8 lo0 ff01::%nfe0/32 link#2 UC 00 - 4 nfe0 ff01::%lo0/32 localhost UC 00 - 4 lo0 ff01::%otus0/32link#7 UC 00 - 4 otus0 ff02::/16 localhost UGRS 10 - 8 lo0 ff02::%nfe0/32 link#2 UC 00 - 4 nfe0 ff02::%lo0/32 localhost UC 00 - 4 lo0 ff02::%otus0/32link#7 UC 00 - 4 otus0 - -- On the Beagleboard running Angstrom: r...@beagleboard:~# ifconfig usb0 inet 192.168.10.10 netmask 255.255.255.0 r...@beagleboard:~# [ 95.218231] usb0: link up, 100Mbps, full-duplex, lpa 0x41E1 r...@beagleboard:~# route add default gw 192.168.10.12 netmask 255.255.255.0 dev usb0 r...@beagleboard:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default 192.168.10.12 255.255.255.0 UG0 00 usb0 192.168.10.0* 255.255.255.0 U 0 00 usb0 r...@beagleboard:~# ping 192.168.10.12 PING 192.168.10.12 (192.168.10.12) 56(84) bytes of data. 64 bytes from 192.168.10.12: icmp_seq=1 ttl=255 time=6.89 ms 64 bytes from 192.168.10.12: icmp_seq=2 ttl=255 time=0.427 ms 64 bytes from 192.168.10.12: icmp_seq=3 ttl=255 time=0.397 ms ^C --- 192.168.10.12 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.397/2.574/6.898/3.057 ms r...@beagleboard:~# ping 192.168.1.101 connect: Network is unreachable r...@beagleboard:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default 192.168.10.12 255.255.255.0 UG0 00 usb0 192.168.10.0* 255.255.255.0 U 0 00 usb0 - - 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
Re: IP bridge was briefly working now is not, OpenBSD 4.8, amd64, bridge from PC wifi to Beagleboard
I think it's only saying that because your current configuration (static IP) isn't routing through to the network (you'd have to reconfigure both routers more). So, instead of trying to route the packets, you could just bridge them, and use DHCP to get an address from your 192.168.1.0/24 router. --AlanCF On Dec 20, 2010 4:19 PM, brett brett.ma...@gmail.com wrote: 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. r...@beagleboard:~# ping 192.168.1.101 connect: Network is unreachable r...@beagleboard:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.10.12 255.255.255.0 UG0 0 0 usb0 192.168.10.0* 255.255.255.0 U 0 0 0 usb0 - - 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 But since the 192.168.1.0 network is unreachable I don't think the dhcp request would get through anyway
Re: IP bridge was briefly working now is not, OpenBSD 4.8, amd64, bridge from PC wifi to Beagleboard
On Mon, Dec 20, 2010 at 5:45 PM, Jon Simola jsim...@gmail.com wrote: On Mon, Dec 20, 2010 at 3:20 PM, brett brett.ma...@gmail.com wrote: r...@beagleboard:~# route add default gw 192.168.10.12 netmask 255.255.255.0 dev usb0 Don't set a netmask on your default route. You're adding a route for 0.0.0.0/24. r...@beagleboard:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default 192.168.10.12 255.255.255.0 UG0 00 usb0 192.168.10.0* 255.255.255.0 U 0 00 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). 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 static route, or do ARP proxying at the OpenBSD box. All the IRB/CRB nonsense is just distracting. In my opinion, bridging is the most efficient way of accomplishing the task (getting acccess to the wireless network through a computer running OpenBSD) -- Jon --AlanCF
