Dan, Thanks for the reply. The client is a laptop running Windows XP Home EditionI'. Server is a tower running Gentoo 2006.1, shorewall 3.0.8.
The client is setup as follows: IP address: 192.168.1.2 Netmask: 255.255.255.0 Gateway: 192.168.1.1 DNS: 192.168.1.1 I've changed my /etc/conf.d/net to: # Interface Handler modules=( "ifconfig" ) # eth0 (WAN) config config_eth0=( "dhcp" ) # eth1 (LAN) config config_eth1=( "192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255" ) Amongst many other things, shorewall dump shows: Shorewall has detected the following iptables/netfilter capabilities: NAT: Available Packet Mangling: Available Multi-port Match: Available Extended Multi-port Match: Available Connection Tracking Match: Available Packet Type Match: Available Policy Match: Available Physdev Match: Not available IP range Match: Available Recent Match: Available Owner Match: Available Ipset Match: Not available CONNMARK Target: Not available Connmark Match: Available Raw Table: Available CLASSIFY Target: Available FORWARD Mangle Chain: Available So, I think I have all that I need compiled into my kernel (2.6.19-r1). I'll be home in a bit, and I'll get on the Windows computer and run ipconfig and route to find out what the IP info and routing table looks like on the client and post that. Thanks again for your help. Shawn On 2/2/07, Dan Farrell <[EMAIL PROTECTED]> wrote:
On Fri, 2 Feb 2007 12:07:59 -0500 "Shawn Singh" <[EMAIL PROTECTED]> wrote: > Hello list, > > I've got my /etc/conf.d/net setup as follows: > > # Interface Handler > modules=( "ifconfig" ) > > # eth0 (WAN) config > config_eth0=( "dhcp" ) > > # eth1 (LAN) config > config_eth1=( "192.168.1.1 netmask 255.255.255.0 broadcast > 192.168.1.255" ) routes_eth1=( "192.168.1.0 via 192.168.1.1" ) # the > idea here is that I wish to have all traffic intended for hosts on > 192.168.1.0 pass through 192.168.1.1. all on the 'server' right? The 'server' doesn't need a route to 192.168.1.0 through 192.168.1.1. That's going to be automatic on the server's end because of the line > 192.168.1.0 * 255.255.255.0 U 0 0 0 eth1 in route. A route through eth1 to the subnet eth1 is on will automatically be added. But does the 'client' computer have such a default route through 192.168.1.1? The command to set up such a route (again, on the client) would be route add default gw 192.168.1.1; > Here's the output from ifconfig eth1: looks fine. > This is my routing table: looks fine, as long as it's from the server and not the client. > One odd thing is, if I run mii-tool eth1, I get: > eth1: no link > eth1 is connected to my client machine via crossover cable (the wire > scheme A end is plugged into eth1, and the wire scheme b end is > plugged into the client machine) You clearly know the difference between a patch and a crossover, but i don't see why the interfaces arent' registering a conection. > I'm experiencing difficulty where my client can't get to the Internet > (the pages just time out) you need ip forwarding enabled to pull that off. > I can't ping the gateway (192.168.1.1) > from the client. Also, from the firewall, I can't ping the client > machine ( 192.168.1.2). This should be working right now, though. Can you post the ipconfig and route output from the 'client' ? > Pings from the firewall to the client result in Destination > Unreachable, and if I remember correctly, pings from the client to > the firewall just time out. sounds like the client is not actually 'connected'. Although, clearly the physical connection is there. > I'm running shorewall (v 3.0.8), so I've tried shutting it down > (shorewall clear) to eliminate that as an option, but still not > getting anywhere. oh oh. shorewall can really confuse things. Stop shorewall and have it save your iptables output, then I would suggest flushing > .config has the following entries in it, please let me know if there > are others that you need to see. > > CONFIG_IP_ADVANCED_ROUTER=y you don't need this. > CONFIG_NETFILTER=y > CONFIG_IP_NF_NAT=y you will need this. But only oce you get connected to 192.168.1.1 ! remember, the client needs a default route set. The server _isn't_ going to need a route to 192.168.1/24 explicitly set in conf.d/net > Thanks, > > Shawn I'm on comcast too: 20: c-71-xxx-144-1.hsd1.fl.comcast.net (71.203.144.1) asymm 21 167.516ms reached Resume: pmtu 1500 hops 20 back 21 only 1 country's width and 20/21 hops away from you! I mangled your ip address even though you provide it yourself, to allow you to be the one invading your privacy and not me . ps, if you have a switch around, i bet it would work if you plugged in both to switch (/ hub) via patch cable. I bet your crossover is bad. -- gentoo-user@gentoo.org mailing list
-- "Doing linear scans over an associative array is like trying to club someone to death with a loaded Uzi." Larry Wall
