Modify

Opened 12 years ago

Closed 12 years ago

#226 closed defect (duplicate)

Even More Information For Ticket #219

Reported by: twiddlebits@… Owned by: developers
Priority: normal Milestone:
Component: base system Version: 2.0
Keywords: vlan0 vlan1 defective Cc:

Description

Updated to kamikaze version #3013 selecting only kernel version 2.6 build option and wiped the wgt634u FLASH. The ifconfig shows no DHCP assigned ip address to vlan1 similar to previous ticket #219 problem. The br0 device shows a static address of 192.168.1.1.

Really weird symptom - I connected Linux at91rm9200 running version 2.6 to the wgt634u LAN port #1 and received a DHCP address of 192.168.127.144. The weird part is that according to the ifconfig from the wgt634u device it should be handing out 192.168.1.x addreses. The wgt634u device is connected via the WAN interface to my home LAN which is 192.168.127.x. The DHCP server is the verizon supplied DSL modem. The dnsmasq process is running using the standard config file which is all commented out. The route table shows only the 192.168.1.1 default entry for Iface br0

Here is output from at91 after reboot:

Welcome to AT91RM9200EK!
# ifconfig
eth0 Link encap:Ethernet HWaddr 12:34:56:78:9A:BC

inet addr:192.168.127.144 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:894 (894.0 B) TX bytes:1180 (1.1 KiB)
Interrupt:24 Base address:0xc000

Manually assigning the 192.168.1.11 address to the at91 eth0 interface still does not allow pinging to be successful.

It appears the wgt634u VLAN0 and VLAN1 are defective - yet the ifconfig TX and RX packet counts are increasing, they packets don't seem to be forwarded to the protocol stacks.

I manually assigned an ip address, added a route table entry and tried to ping the WAN interface, note the RX packet count is zero. I did notice the ifconfig eth0 RX count climbing with the ping count.

vlan1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx

inet addr:192.168.127.200 Bcast:192.168.127.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:39572 (38.6 KiB)

eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx

UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:769 errors:0 dropped:0 overruns:0 frame:0
TX packets:275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:73597 (71.8 KiB) TX bytes:58718 (57.3 KiB)
Interrupt:4

Stopping the pinging from the WAN side, stopped the RX packet count from climbing.

root@OpenWrt:/etc# cat /etc/config/network
#### VLAN configuration
vlan0hwname=et0
vlan1hwname=et0
vlan0ports="1 2 3 4 5*"
vlan1ports="0 5"

#### LAN configuration
lan_proto="static"
lan_ifname="br0"
lan_ifnames="vlan0 eth1"
lan_ipaddr="192.168.1.1"
# lan_dns="192.168.1.1"
# lan_gateway="192.168.1.1"

#### WAN configuration
# wan_proto: WAN protocol, available protocols:
# none: disable
# dhcp: DHCP
# static: Static IP
# pppoe: PPP over Ethernet
# pptp: Point-to-Point tunneling Protocol
# for pppoe and pptp you need to use wan_ifname="ppp0"

wan_proto=dhcp
wan_ifname="vlan1"
wan_device="vlan1"
# wan_ipaddr="192.168.0.2"
# wan_netmask="255.255.255.0"
# wan_gateway="192.168.0.1"
# wan_dns="192.168.0.1"

Notice that the vlan2 seems to be enabled as well

root@OpenWrt:/etc# cat /proc/switch/eth0/vlan/0/ports
1 2 3 4 5t*
root@OpenWrt:/etc# cat /proc/switch/eth0/vlan/1/ports
0 5t
root@OpenWrt:/etc# cat /proc/switch/eth0/vlan/2/ports
4 5u

Attachments (0)

Change History (1)

comment:1 Changed 12 years ago by nbd

  • Resolution set to duplicate
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.