Eth1 problems again [ Solved - for the moment]

[Craig White]

On Thu, 2007-10-04 at 15:00 +1000, david walcroft wrote:
> Craig White wrote:
> > On Thu, 2007-10-04 at 10:59 +1000, david walcroft wrote:
> >   
> >> Timothy Murphy wrote:
> >>     
> >>>   
> >>>       
> >> Eth0 is dhcp,Ethe1 is static 192.168.0.1
> >>     
> >>> What does "ifconfig eth1" say?
> >>>   
> >>>       
> >> [david at reddwarf ~]$ ifconfig eth1
> >> eth1      Link encap:Ethernet  HWaddr 00:E0:4C:14:1B:09
> >>           inet6 addr: fe80::2e0:4cff:fe14:1b09/64 Scope:Link
> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >>           RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> >>           TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
> >>           collisions:0 txqueuelen:1000
> >>           RX bytes:747 (747.0 b)  TX bytes:578 (578.0 b)
> >>           Interrupt:22 Base address:0x8c00
> >>     
> > ----
> > nope - ip address doesn't show...there's an error
> > ----
> >   
> >> [david at reddwarf ~]$
> >>     
> >>> What does "route" say?
> >>>   
> >>>       
> >> [david at reddwarf ~]$ route
> >> Kernel IP routing table
> >> Destination     Gateway         Genmask         Flags Metric Ref    Use 
> >> Iface
> >> 121.208.32.0    *               255.255.248.0   U     0      0        0 eth0
> >> 169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
> >> default         121.208.32.1    0.0.0.0         UG    0      0        0 eth0
> >> [david at reddwarf ~]$
> >>     
> >>> What is in /etc/sysconfig/network-scripts/ifcfg-eth1?
> >>>   
> >>>       
> >> # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
> >> DEVICE=eth1
> >> ONBOOT=yes
> >> BOOTPROTO=none
> >> HWADDR=00:e0:4c:14:1b:09
> >> NETMASK=255.255.255.0
> >> IPADDR=192.168.0.1
> >> GATEWAY=192.168.0.0
> >> TYPE=Ethernet
> >> USERCTL=no
> >> IPV6INIT=no
> >> PEERDNS=yes
> >>     
> > ----
> > GATEWAY is a bad address... that's a network address
> >
> > comment out GATEWAY...you already have a GATEWAY address per above
> > (121.208.32.1)
> > comment out PEERDNS...that's for BOOTPROTO=dhcp
> > comment out BOOTPROTO
> >
> > after you change these settings...
> >
> > try...
> >
> > ifup eth1
> > ----
> >   
> >> [david at reddwarf ~]$ sudo ping -c 5 192.168.0.2
> >> PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
> >> ping: sendmsg: Operation not permitted
> >> ping: sendmsg: Operation not permitted
> >> ping: sendmsg: Operation not permitted
> >> ping: sendmsg: Operation not permitted
> >> ping: sendmsg: Operation not permitted
> >>
> >> What do I do to get ping to work  and is it part of this problem overall.
> >> 192.168.0.2 is on the other end of my crossover cable
> >>     
> > ----
> > should work
> >
> > Craig
> >
> >   
> Thanks Craig It's up and running and 192.168.0.2 is on the net
> But pinging only provides me with lost packets to 192.168.0.2
> I can ping 192.168.0.1 and 121.208.32.1 my gateway.
> 
> Thanks a lot Craig
----
My guess is that you have some firewall software on your Windows box
preventing ping.

Windows XP SP2? Look at Control Panel Windows Firewall. Turn if off
temporarily.

Craig