[ale] home networking difficulties

[Andrew Grimmke]

well.  here's what I have:


TCPdump output

05:37:11.991603 arp who-has 192.168.1.1 tell 192.168.1.2
05:37:11.991642 arp reply 192.168.1.1 is-at
0:7:95:ba:e6:e9
05:37:11.991734 192.168.1.2 > 192.168.1.1: icmp: echo
request
05:37:16.222541 192.168.1.2 > 192.168.1.1: icmp: echo
request
05:37:20.722458 192.168.1.2 > 192.168.1.1: icmp: echo
request
05:37:25.222380 192.168.1.2 > 192.168.1.1: icmp: echo
request

Kernel IP routing table
Destination     Gateway         Genmask         Flags
Metric Ref    Use Iface
65.188.226.XXX   *               255.255.255.252 U    
0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0
     0        0 eth1
192.168.0.0     *               255.255.255.0   U     0
     0        0 eth1
192.168.0.0     *               255.255.255.0   U     0
     0        0 eth1
127.0.0.0       *               255.0.0.0       U     0
     0        0 lo
default         dsl-65-188-226- 0.0.0.0         UG    0
     0        0 eth0

Of course the XXX was added by me. 

I have networked on 192.168.0.X and it seems that eth1
is still trying to recognize that subnet. Not sure why 
twice.  

Does anything else jump out?


On Fri, 16 August 2002, Geoffrey wrote:
> 
> Andrew Grimmke wrote:
> Thanks geoffrey,
>  
> I'd suggest firing up tcpdump or ethereal on your
> Redhat box nic that's connected to your internal
> network.
> See if anything is coming from that side.
>  
>  
> I assume something like
> tcpdump -i eth1
> would work
> 
> yes, as long as eth1 is the nic on your inside
network.
> 
> 
> then ping from the windows box.
>  
>  
> Also, what does your routing look like on the Redhat
> box?
> 
>  
>  
> I'm not sure what you mean here?  should I provide the
> output from the route command?
> 
> yes.
> 
> -- 
> Until later: Geoffrey		esoteric at 3times25.net
> 
> I didn't have to buy my radio from a specific company
> to listen
> to FM, why doesn't that apply to the Internet
> (anymore...)?

Andrew Grimmke
Marietta, Georgia

---
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.