So, I am using a Raspberry PI Model B (256) with the latest raspbian image as a wireless bridge for an entertainment center with an ethernet port. The Pi connects to the LAN wirelessly and the eth0 port is "shared with other computers" via NetworkManager.

From ps aux | grep dnsmasq, I see that dnsmasq (apparently started by NetworkManager) provides an IP of 10.x.x.x to the entertainment center. The LAN has the usual 192.168.x.x IP space, provided via DHCP from a router.

So far so good, the entertainment center can get internet radio and connects to the internet. From the Pi, I can ping the entertainment center and anyone on the LAN.

But I cannot ping the entertainment center from anyone else on the LAN. What I would like is to drop the NAT on the Pi so that the entertainment center is visible to the entire LAN. Any ideas?

There are google results for achieving this result for various routers, but I'm not sure how to do it with the Pi/using debian and NetworkManager.

Did you set up NAT on the Pi yourself? I don't think it's enabled by default.

Hey, thanks for responding!

I went to NetworkManager and enabled "shared with other computers" on eth0, which apparently starts dnsmasq. I presume that NAT is set up by default.

ps aux | grep dns gives the following:

wheras ifconfig is

So you see I ssh into the pi at 192.168.1.19, where I can ping everyone, including folks on 10.42.0.x and 192.168.1.x, however I can't ping 10.42.0.x from 192.168.1.199 (another computer)

I got the instructions at http://www.raspberrypi.org/phpBB3/vi...25268&p=270912

I tried setting up a bridge in the past on the pi (not on this install) but it didn't work consistently and didn't allow me to ssh in. Obviously I had something not right or my wifi adapter was incapable of bridging, so I used the suggestion above which seems to work great, except for the part where I don't know how to connect the subnets.

You'll need to set the Pi up to be a router and configure the routing tables on your other machines to use 192.168.1.19 as their gateway to access the 10.42.0.0/24 subnet. If you Google around for Linux router or the like, the instructions are pretty easy to find (since you're not doing NAT, it will be easy -- basically just set net.ipv4.ip_forward = 1 in your sysctl variables, IIRC). Then you'll need to use the "route" command on your other machines, something like:

This assumes your other machines are running Linux. The command is slightly different under Windows as per this Microsoft documentation page. If you want to add the route permanently, there are ways to do it (they vary by distro, but you can always just put the route command in your /etc/rc.local script.

Well OK, I'll try again.. the problem is, there are so many different instructions of so many different eras, most using iptables or outdated and not using NetworkManager. I'm kind of a network idiot, and have tried googling and trying a dozen different "solutions" so far without success using iptables... the thing is, most instructions assume the machine will be the router for the network and handling the internet connection, but I have a router that does that job and provides DHCP already. So I was hoping someone had a simple answer to this. [/end of whining]

BTW, I did try adding the route to my main desktop, and it certainly sends the appropriate path to 192.168.1.19 when I try to ping 10.42.0.x, so I tried adding echo "1"> /proc/sys/net/ipv4/ip_forward to my pi, but that didn't help get rid of Destination Port Unreachable. I didn't think it would, as I'm not using iptables. What I'd really like to do is make the 10.42.0.x machine, which is an entertainment center, visible on the network so my iphone's (on 192.168.1.x) app which controls it can see it. So the solution can't involve changing the route on every machine, as that will be impossible on the iphone. The solution has to involve just the pi.

I don't see the need for the Pi to be in between the entertainment center and the rest of your network. Just plug your entertainment center into your switch and plug your Pi into your switch. This will solve half of your problem; the rest of your network will have access to the entertainment center since everything will be in the same broadcast domain.

The second half of the problem is to provide a wireless access point. You could use a commercial AP in bridged mode, your modem/gateway may already have wireless enabled, or you could setup your Pi to be an access point.

'"shared with other computers" via NetworkManager' is starting dnsmasq and configuring NAT. You don't want that for a bridge. The most common mistake I see when people try to setup bridging on Linux is they configure the individual interfaces (eth0, wlan0, or ???) which you should not do. If you must enter something in NetworkManager use all zeros for address/netmask for the physical interfaces (0.0.0.0/0.0.0.0). Create the bridge and include the 2 interfaces. Then configure the bridge interface (ie. br0) to get an address, either via dhcp or statically. I can't help you with the details of NetworkManager as I don't use it, but the fundamental info here should get you started in the right direction.

Thanks for pitching in. However, I'm not sure I explained the problem correctly. The entertainment center is nowhere near the switch, in fact, there is no switch, nor is the router (which could act as a switch) accessible by or relocatable to the entertainment center. The only reason the pi is connected to the entertainment center is to provide a connection to the network, via the only route available, wireless. I'm trying to get the pi to behave like a wireless extender; ie make an existing wireless network available to a wired connection.

I could just buy a wireless extender with a built in switch (eg an Amped wireless extender SR30000), but I have the pi already there; it should be able to do the job... and it is much cheaper.

A wireless access point, which makes a wired network available to wireless devices, is unnecessary; I have a wireless router which already covers the area sufficiently.

The bridge idea using bridge utils and br0 is a good idea; I previously followed the tutorial in LinuxPro that was published a few months ago, but it did not work (i.e. no connection) and gorked up ssh access to the pi also, making diagnosis of the problem difficult. I'm not sure why; I have tried other "simple" tutorials on bridges and none of them work as advertised... perhaps there's an incompatibility with my wireless adapter. That is why I finally used NetworkManager: it actually worked.. except that as you point out, it configures NAT, which I don't want.

If anyone has successfully used a bridge on a pi, and has a link to the instructions on how they did it, let me know. I am running raspbian with xbmc.

[EDIT: I added a static path to 10.42.0.0 to my router; so I can ping the 10.42 network; still no joy on pinging the entertainment center though.]

I'm not familiar with all your hardware but if you're looking for a cheap hardware bridge check out "wireless game adapters." I boolshiat you not. My Netgear setup is via simple web interface, then you just plug into the entertainment center and it'll connect wireless to your PI or AP or whatever device is running your wireless LAN. Works great with IP printers too.