[#4902] ping through vlan on bf518f ezbrd to two ethernel card are both ok while only one is connected

Document created by Aaronwu Employee on Aug 30, 2013
Version 1Show Document
  • View in full screen mode

[#4902] ping through vlan on bf518f ezbrd to two ethernel card are both ok while only one is connected

Submitted By: Mingquan Pan

Open Date

2009-02-13 05:47:08     Close Date

2009-03-03 23:43:55

Priority:

Medium     Assignee:

Graf Yang

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

Category:

N/A     Board:

N/A

Processor:

ALL     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Rejected

Uboot version or rev.:

    Toolchain version or rev.:

4.1 toolchain of Jan 16

App binary format:

N/A     

Summary: ping through vlan on bf518f ezbrd to two ethernel card are both ok while only one is connected

Details:

 

ping through vlan on bf518f ezbrd to two ethernel card are both ok while only one is connected.

 

On host:

 

test@51x:~> /sbin/ifconfig

eth0      Link encap:Ethernet  HWaddr 00:23:AE:5C:A0:AA

          inet addr:10.99.29.80  Bcast:10.99.29.255  Mask:255.255.255.0

          inet6 addr: fe80::223:aeff:fe5c:a0aa/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:8464882 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2804793 errors:1 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1200824115 (1145.1 Mb)  TX bytes:274929467 (262.1 Mb)

          Interrupt:16

 

eth1      Link encap:Ethernet  HWaddr 00:1D:0F:11:AE:04

          inet addr:10.100.4.174  Bcast:10.100.4.255  Mask:255.255.255.0

          inet6 addr: fe80::21d:fff:fe11:ae04/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:33586390 errors:2 dropped:0 overruns:1 frame:0

          TX packets:25417769 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:915142694 (872.7 Mb)  TX bytes:3568324767 (3403.0 Mb)

          Interrupt:18 Base address:0xaf00

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:254 errors:0 dropped:0 overruns:0 frame:0

          TX packets:254 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:22564 (22.0 Kb)  TX bytes:22564 (22.0 Kb)

 

test@51x:~> /sbin/route

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

10.100.4.0      *               255.255.255.0   U     0      0        0 eth1

10.99.29.0      *               255.255.255.0   U     0      0        0 eth0

link-local      *               255.255.0.0     U     0      0        0 eth0

loopback        *               255.0.0.0       U     0      0        0 lo

default         10.99.29.1      0.0.0.0         UG    0      0        0 eth0

test@51x:~>

 

On target:

                      root:/> route

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

10.0.0.0        *               255.0.0.0       U     0      0        0 eth1

10.0.0.0        *               255.0.0.0       U     0      0        0 eth2

11.0.0.0        *               255.0.0.0       U     0      0        0 eth0

root:/> ifconfig

eth0      Link encap:Ethernet  HWaddr 0A:39:0E:5C:AC:8E

          inet addr:11.11.11.11  Bcast:11.255.255.255  Mask:255.0.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:15 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:2630 (2.5 KiB)  TX bytes:518 (518.0 B)

 

eth1      Link encap:Ethernet  HWaddr 0A:39:0E:5C:AC:8E

          inet addr:10.100.4.1  Bcast:10.255.255.255  Mask:255.0.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:7 errors:0 dropped:0 overruns:0 frame:0

          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:502 (502.0 B)  TX bytes:518 (518.0 B)

 

eth2      Link encap:Ethernet  HWaddr 0A:39:0E:5C:AC:8E

          inet addr:10.100.4.2  Bcast:10.255.255.255  Mask:255.0.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:8 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1858 (1.8 KiB)  TX bytes:0 (0.0 B)

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  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:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

 

And only eth1 is connected to the host, the other port is wired to the company switch.

 

When ping from the host:

test@51x:~>

test@51x:~> ping 10.100.4.1

PING 10.100.4.1 (10.100.4.1) 56(84) bytes of data.

64 bytes from 10.100.4.1: icmp_seq=1 ttl=64 time=3.04 ms

64 bytes from 10.100.4.1: icmp_seq=2 ttl=64 time=0.223 ms

^C

--- 10.100.4.1 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1005ms

rtt min/avg/max/mdev = 0.223/1.633/3.043/1.410 ms

test@51x:~> ping 10.100.4.2

PING 10.100.4.2 (10.100.4.2) 56(84) bytes of data.

64 bytes from 10.100.4.2: icmp_seq=1 ttl=64 time=3.11 ms

64 bytes from 10.100.4.2: icmp_seq=2 ttl=64 time=0.233 ms

^C

--- 10.100.4.2 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1005ms

rtt min/avg/max/mdev = 0.233/1.673/3.113/1.440 ms

test@51x:~>                                                       

 

both of them are ok, while the latter one should be not through.     

                                  

 

Follow-ups

 

--- Graf Yang                                                2009-02-27 01:16:57

Please not set the two ethernet card in the same subnetwork.

As I have tested this case on my PC, the result is identical.

 

--- Mike Frysinger                                           2009-02-27 02:14:18

yes, this is expected default Linux behavior.  it will respond to any IP it has

on any interface.

 

--- Mingquan Pan                                             2009-03-03 23:43:55

So close.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes