sam wrote: > Hi... > > I have a laptop that's connected to the rest of the network via the wireless > port. It works. I also have the eth0 port that I use to connect to another > box that's not connected to the network. > > so > > internal box >>>>laptop >>>>> rest of network (internal/internet) > eth0 (eth0) (ath0) > > Internal Box eth0:192.168.2.99 > > laptop > eth0: 192.168.2.33 > ath0: 192.168.1.33 > > Each of the connections work. > > I've set up separate subnets on the laptop, as this appears to be the only > way of being able to be able to have both eth0/ath0 active, and > communicating at the same time. > You can also bridge the two interfaces. The bridge interface then has the IP address, and network traffic passes between eth0 and ath0. This way, everything can be on the same subnet. But the laptop would not be acting as a firewall for the rest of the network. > Using the laptop, I can currently access both the box, and the network at > the same time. > > However, using the box, I can only access the laptop. Pinging to the rest of > the network, results in "host unreachable", which is expected. > > So, I'm trying to figure out what has to be set on: > either the Internal eth0 nic, > or the laptop eth0 nic, > or both the Internal box/laptop > to allow the Internal box to be able to access the rest of the network. > > I've been looking high/low to try to figure this out. I need to accomplish > this, as I'd like to update the internal computer with Fedora update rpms > via yum, which requires internet access. > > Information that I've come across on the 'net refers to > IPTables/Route/IPMasq/etc.... > > I've tried to setup iptables on the laptop, to do ip forwarding based on > articles i've seen. I've implemented: > > iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE > /etc/init.d/iptables save > > when i then use the Internal Box, to try to access a box on my network, or > the internet, i'm still restricted to only being able to access the laptop. > > any thoughts/comments/pointers would be helpful, and appreciated. > > thanks > What is the network setup on the internal box? Does it have 192.168.2.33 as the default gateway? If not, does it have a route for the 192.168.1.0 network that uses 192.168.2.33 as the gateway? If not, then noting you do on the laptop is going to help. (Unless you are running a DHCP server on the laptop, and the internal box is configured by DHCP - you can change the DHCP server to set the proper routes and gateways.) From your description, it sounds like you have a wireless firewall/router on your Internet connection, and you want to use the laptop as a wireless to wired bridge. If this is correct, you may find creating a bridge interface instead of doing NAT will work better for you. I don't have the URL handy, but there are some good bridging HOWTOs if you deside to go that route. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
