[ale] home networking difficulties

Andrew Grimmke grimmke at directvinternet.com
Wed Aug 21 17:19:34 EDT 2002


On Wed, 2002-08-21 at 22:05, Adrin wrote:
> Here is a check list for you
> First time I did this it about drove me crazy. ( Short
> drive. )
> 
> I am not sure of your setup.  2 NICS in the Linux box?

yes

> If so.  Ping the first card and see if you get a renounce.
> If so.  Ping the second card and see if you get a renounce.

can ping both IP internally, but not from the windows box.

> 	If no then you don't have IP forwarding on or a rule is set
> to drop the pings.
>       Check this file for a "1" in it
> /proc/sys/net/ipv4/ip_forward

All the files in /proc appear to be empty.

> 
> Another good testing measure is to let your fire wall down
> and test. if you get results with it down then you need to
> rconfig the linux box.
> 
> I got some general firewall rules that I downloaded form
> tldp.org  many moons ago. Interested in the scripts?
> 
> Adrin
> 
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Andrew Grimmke [mailto:grimmke at directvinternet.com]
> > Sent: Wednesday, August 21, 2002 6:39 AM
> > To: Joseph A. Knapka
> > Cc: Atlanta Linux Enthusiasts list
> > Subject: Re: [ale] home networking difficulties
> >
> >
> > arp -a on the linux box
> >
> > dsl-65-188-226-X.telocity.com (65.1188.226.X) at
> > 00:10:E8:0A.....
> > [ether] on eth0
> > ? (192.168.1.2) at 19:02:16:08..... [ether] on eth1
> >
> > on windows box.  Strange, I get
> > no ARP entries found
> >
> > unless I ping 192.168.1.1
> >
> > then I get (for a few minutes after)
> >
> > Interface: 192.168.1.2 on 0x3
> >
> > internet address     physical address    type
> > 192.169.1.1          00-07-95....        dynamic
> >
> > also,
> >
> > I am pretty sure the cabling is right.  I have
> > networked with each of
> > the cards (for dsl and at lan parties), as well.
> > When I ping from linux
> > to windows, if the windows software firewall is
> > up, I get a popup about
> > "unauthorized ICMP attempt from 192.168.1.1"
> >
> > On Wed, 2002-08-21 at 17:51, Joseph A. Knapka wrote:
> > > Andrew Grimmke wrote:
> > > >
> > > > On Wed, 2002-08-21 at 15:52, Joseph A. Knapka wrote:
> > > > > Andrew Grimmke wrote:
> > > > >
> > > > > > Geoffrey wrote:
> > > > > > >
> > > > > > >You machine is not responding to the
> > ping request.
> > > > > > >It's either a routing issue, or you've
> > got a firewall
> > > > > > >running on your Redhat box blocking.
> > What are the ip
> > > > > > >addresses for the two boxes you're trying to ping
> > > > > > >to/from?  Look to see if you
> > > > > > >have /etc/sysconfig/ipchains file.
> > > > > >
> > > > > > I know it has taken a while, but I have
> > been trying to
> > > > > > figure this out and doing some research on my own.
> > > > > >
> > > > > > the linux box router/firewall is 192.168.1.1
> > > > > > the windows box is 192.168.1.2
> > > > > >
> > > > > > IPchains is running, but I have set a
> > rule to allow
> > > > > > traffic from the 192.168.1.X subnet.
> > > > > >
> > > > >
> > > > > Does it work if you totally disable ipchains? (Just
> > > > > flush all the rules - ipchains -F <chain>, for
> > > > > each chain, IIRC.)
> > > >
> > > > Well,
> > > >
> > > > I flushed the rules (ipchains -F).  Then I
> > listed the rules to make sure
> > > > I did it right (ipchains -L).  All that was
> > lest was the default
> > > > policies:
> > > > Chain input (policy ACCEPT):
> > > > Chain forward (policy ACCEPT):
> > > > Chain output (policy ACCEPT):
> > > >
> > > > then I ping the other machine and nothing.
> > > >
> > > > could it be routing?  the routing table
> > looked pretty straightforward.
> > > > I didn't see anything that looked wrong.
> > > >
> > >
> > > What does "arp -a" show you on each machine?
> > (It -should-
> > > work on the Windows box, and definitely will on
> > the Linux
> > > box). The ARP cache should contain each IP address,
> > > along with the associated hardware (MAC) address. If
> > > they don't, then you may have some bad hardware. I've
> > > had several NICs (cheap Netgear cards) where the
> > > receiver failed - I'd still see packets from those
> > > cards on the network, but they'd never receive
> > > anything. The way I figured that out was by seeing
> > > an ARP reply go out on the net via snort, and then
> > > finding that the machine in question didn't have a
> > > corresponding entry in its ARP cache.
> > >
> > > Cheers,
> > >
> > > -- Joe
> > >   "I'd rather chew my leg off than maintain
> > Java code, which
> > >    sucks, 'cause I have a lot of Java code to
> > maintain and
> > >    the leg surgery is starting to get expensive." - Me
> > >
> >
> >
> >
> > ---
> > This message has been sent through the ALE
> > general discussion list.
> > See http://www.ale.org/mailing-lists.shtml for
> > more info. Problems should be
> > sent to listmaster at ale dot org.
> >
> 
> 



---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.






More information about the Ale mailing list