[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Sun Fire V210 NIC's don't work

On 11/14/2012 03:32 PM, Frans van Berckel wrote:

On Wed, 2012-11-14 at 15:04 +0000, Kaya Saman wrote:

Actually the gateway for eth0 is: 192.168.1.1/24 and the gateway for
eth1 is 192.168.140.1/30; two completely different subnets.....

Interfaces file:

auto eth0
iface eth0 inet static
address 192.168.1.116
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

Looks okay to me.


auto eth1
#iface eth1 inet dhcp
iface eth1 inet static
address 192.168.140.2
netmask 255.255.255.252
network 192.168.140.0
broadcast 192.168.140.3
gateway 192.168.140.1

Why is broadcast set to 192.168.140.3? With a gateway set to 140.1
you've got to be able to ping 192.168.140.1, true.
For a subnet which is /30 CIDR or 255.255.255.252 you should get 4 IP's: network, broadcast, + 2 usable - this is a kind of pseudo point-to-point interface. 




# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window irtt
Iface
192.168.140.0   *               255.255.255.252 U         0 0          0
eth1
192.168.1.0     *               255.255.255.0   U         0 0          0
eth0
default         192.168.140.1   0.0.0.0         UG        0 0          0
eth1
default         cisco857w.optip 0.0.0.0         UG        0 0          0
eth0


If however I run ping -I eth1 192.168.140.1 nothing happens and hence
dmesg is claiming the link isn't ready... the green lights on the back
of the system are on and so are the ones on the switch.

I think the eth1 link is up, because ifconfig show it is.


Also just now I reconfigured eth1 and took out the config from the eth0
in the interfaces file. However, after setting my switch to the proper
vlan on eth1 port I am still not getting any connectivity?

eth1      Link encap:Ethernet  HWaddr 00:14:4f:5d:1e:80
            inet addr:192.168.1.116  Bcast:192.168.1.255 Mask:255.255.255.0
            UP BROADCAST MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
            Interrupt:31

Now eth1 is set for 1.116 instead of 140.2? ... please reload networking
or reboot to get the settings okay.
All reloaded, sorry for the confusion but I rearranged things to test and see if eth1 became primary. Again no link :-( I will also try with eth2 and eth3 but I have my doubts; I even changed the cable and no joy. Something is definitely hinky! 



# service networking reload


ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
  From 192.168.1.116 icmp_seq=1 Destination Host Unreachable
  From 192.168.1.116 icmp_seq=2 Destination Host Unreachable

Read up above ...

If reloading the settings doesn't help, maybe someone els with more vlan
experiences, will step in here.


I'm sure it's the driver or kernel bug.... though I could be wrong.



Thanks,


Frans van Berckel




Regards,


Kaya
Reply to: