On Mon, Apr 6, 2015 at 3:05 PM, Brian J. Murrell <[email protected]>
wrote:

> On a 14.07 TP-Link WDR4300, given the network configuration:
>
> config interface 'loopback'
>         option ifname 'lo'
>         option proto 'static'
>         option ipaddr '127.0.0.1'
>         option netmask '255.0.0.0'
>
> config globals 'globals'
>         option ula_prefix 'fd31:aeb1:48df::/48'
>
> config interface 'lan'
>         option ifname 'eth0.1'
>         option force_link '1'
>         option type 'bridge'
>         option proto 'static'
>         option netmask '255.255.255.0'
>         option ip6assign '60'
>         list ipaddr '10.75.22.253'
>         list ipaddr '10.75.22.254'
>         option defaultroute '0'
>         option peerdns '0'
>         option dns '10.75.22.3'
>         list dns_search 'interlinx.bc.ca ilinx'
>
> config interface 'wan0'
>         option ifname 'eth0.2'
>         option proto 'dhcp'
>         option peerdns '0'
>
> config interface 'wan1'
>         option ifname 'eth0.3'
>         option proto 'pppoe'
>         option username '[email protected]'
>         option password 'xxx'
>         option ppp_redial 'persist'
>         option peerdns '0'
>         option defaultroute '0'
>
> config interface 'wan6'
>         option ifname '@wan'
>         option proto 'dhcpv6'
>
> config switch
>         option name 'switch0'
>         option reset '1'
>         option enable_vlan '1'
>
> config switch_vlan
>         option device 'switch0'
>         option vlan '1'
>         option vid '1'
>         option ports '0t 2 3 4'
>
> config switch_vlan
>         option device 'switch0'
>         option vlan '2'
>         option ports '0t 1'
>         option vid '2'
>
> config switch_vlan
>         option device 'switch0'
>         option vlan '3'
>         option vid '3'
>         option ports '0t 5'
>
> config interface 'pppoe_ether'
>         option ifname 'eth0.3'
>         option proto 'static'
>         option ipaddr '10.0.0.1'
>         option netmask '255.255.255.0'
>         option defaultroute '0'
>         option peerdns '0'
>
> config interface 'henet'
>         option proto '6in4'
>         option peeraddr '216.66.38.58'
>         option ip6addr '2001:123:1c:abc::2/64'
>         option ip6prefix '2001:123:1d:abc::/64'
>         option tunnelid '123456'
>         option username 'xxx'
>         option password 'xxx'
>         option updatekey 'xxx'
>
> config interface 'cogeco'
>         option proto '6to4'
>         option adv_subnet '1'
>         option adv_interface 'lan'
>         option ip6prefix '2002:11b2:ac2a::1/60'
>
> If I try to add another VLAN and have it tagged on a couple of the
> ethernet ports on the router as such:
>
> config switch_vlan
>         option device 'switch0'
>         option vlan '4'
>         option ports '0t 3t 4t'
>         option vid '4'
>
> The router fails to boot.
>
> I know that sounds pretty vague but I want to make sure that there are
> no already known issues with this before I go digging further, and I
> want to ask what further information I could provide to help debug this.
>
> Cheers,
> b.




Hi Brian,

what do you mean by the router doesn't boot? You see no leds blinking after
you power it up?
Do you just mean that it is not reachable after you make that specific
change in the config?
My experience with switch/network config is that if there is something
wrong with the file the file is not read at all and even the right settings
are not loaded
If you have a serial console, connect through it and have a look at the
output of dmesg.

Alex
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to