<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> That is because the computers on your network do not know where the internal box is. A quick scenario: 192.168.1.1 wants to connect to 192.168.2.13 it looks inside its network settings, and sees that 192.168.2.13 is not on his subnet it checks for other routes that maybe lead to 192.168.2.13, nope, nothing then it sends the packet to the default gateway, hoping the gateway knows what to do with the packet I've never really checked what happens with such a packet at the gateway, but it will most likely drop it. Either way, the packet get's lost. The best way is to setup your DHCP to push a default route for 192.168.2.13 to 192.168.1.33. If you do not have a DHCP server, you will have to set a route manually on each client on the network. Something like this: route add -host 192.168.2.13 gw 192.168.1.33 This will let the other clients know where the internal box is. Hope this works. Regards bruce wrote: <blockquote cite="mid:005001c82ec1$e6812bd0$0301a8c0@tmesa.com" type="cite"> <pre wrap="">hi tim... basically, a laptop connecting via ath0 to my network (and the internet). the setup is internal box ------> laptop (wireless) -----> network/internet eth0 eth0 ath0 eth0 in order to have multiple ports, the eth0/ath0 are on different subnets. laptop eth0 192.168.2.33 ath0 192.168.1.33 internal eth0 192.168.2.13 the setup has to allow the internal box, to communicate with the laptop, as well as the rest of the network. the solution (at least for me) on the internal box -setup a route command to allow the laptop (eth0) to be the default gw on the laptop -setup iptables to pass/masquerade from eth0 to ath0 this allows me to ping systems from the internal box. however, i still can't seem to access the internal box, from any other system in my network... so something in the iptables/masquerade isn't working correctly.. -----Original Message----- From: <a class="moz-txt-link-abbreviated" href="mailto:fedora-list-bounces@redhat.com">fedora-list-bounces@redhat.com</a> [<a class="moz-txt-link-freetext" href="mailto:fedora-list-bounces@redhat.com">mailto:fedora-list-bounces@redhat.com</a>]On Behalf Of Timothy Murphy Sent: Saturday, November 24, 2007 9:20 AM To: <a class="moz-txt-link-abbreviated" href="mailto:fedora-list@redhat.com">fedora-list@redhat.com</a> Subject: Re: ip masquerading bruce wrote: </pre> <blockquote type="cite"> <pre wrap="">i have a situation where i have a system with two connections, one wireless, one eth connetion. i can currently connect with the wireless ath0 to my network/internet/etc... however, when i activate the eth0 at the same time, i can't access the network via ath0. as far as i can tell, i need to implement ip masquerade to have eth0 map, to ath0... my test ip addresses are: ath0 - 192.168.1.33 eth0 - 192.168.2.33 any thoughts/comments/pointers... </pre> </blockquote> <pre wrap=""> I don't really understand your setup. Is this a laptop connecting to a desktop which connects to the internet? If so, I can't believe that you need ip masquerade to connect via ethernet. I'm sure the problem is much simpler. Maybe it's a dhcp problem? Or maybe you are running a firewall on the desktop that does not allow access from your first LAN (192.168.1.*)? -- fedora-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:fedora-list@redhat.com">fedora-list@redhat.com</a> To unsubscribe: <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/fedora-list">https://www.redhat.com/mailman/listinfo/fedora-list</a> </pre> </blockquote> </body> </html>