search

goalmarketing / vigor2130

Automatically exported from code.google.com/p/vigor2130
0 stars 0 forks source link

No IPTVWan ip... #46

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Q)What steps will reproduce the problem?

A)I simply need to enable DHCP on iptv vlan and the problem arises: no dhcp 
lease is received.

Q) What is the expected output? What do you see instead?

A) When issuing: root@Vigor2130:/# uci -P/var/state show network.iptvwan

...a lease was supposed to be given, but its not:

network.iptvwan=interface
network.iptvwan.ifname=eth1.105
network.iptvwan.proto=dhcp
network.iptvwan.hostname=Vigor2130
network.iptvwan.disable=0
network.iptvwan.device=eth1.105

...but if i do this on the internet/voip vlan interface(s) it shows a lease:

network.voipwan=interface
network.voipwan.ifname=eth1.101
network.voipwan.proto=dhcp
network.voipwan.hostname=Vigor2130
network.voipwan.disable=0
network.voipwan.device=eth1.101
network.voipwan.ipaddr=10.xx.xx.xx
network.voipwan.broadcast=+
network.voipwan.netmask=255.255.128.0
network.voipwan.dns=xx.xx.xx.xx xx.xx.xx.xx
network.voipwan.up=1
network.voipwan.uptime=51.56
network.voipwan.lease_gateway=10.xx.xx.xx
network.voipwan.gateway=10.xx.xx.xx
network.voipwan.lease_server=xx.xx.xx.xx
network.voipwan.lease_acquired=1315707232
network.voipwan.lease_lifetime=3600

Q) What version of the product are you using?

A) I'm using a Draytek Vigor 2130vn with 1.5.2 beta firmware

Q) Please provide any additional information below.

A) If i downgrade to 1.5.1 firmware, the dhcp lease is shown on the iptvwan 
interface.

Additional information regarding the interface configuration:

root@Vigor2130:/# cat etc/config/network 

config interface wan
        option ifname eth1.100
        option proto dhcp
        option hostname  Vigor2130
        option domain    
        option disable   0
        option detect    0
        option type      'bridge'

config interface voipwan
        option ifname 'eth1.101'
        option proto dhcp
        option hostname  Vigor2130
        option domain    
        option disable   0

config interface iptvwan
        option ifname 'eth1.105'
        option proto dhcp
        option hostname  Vigor2130
        option domain    
        option disable   0

root@Vigor2130:/# cat /etc/config/wan_tag 

config wan_tag config
        option enabled   1
        option vid       100
        option voip_wan  1
        option voip_vid  101
        option iptv_wan  1
        option iptv_vid  105
        option mngt_wan  0
        option mngt_vid  9
        option br1       0,3,0,1,0,0
        option br2       0,4,0,0,1,0
        option br3       0,105,0,0,0,0

root@Vigor:/# ifconfig eth1.105
eth1.105  Link encap:Ethernet  HWaddr 00:xx:xx:xx:xx:xx  
          inet6 addr: fe80::250:7fff:fecb:edf5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:770 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:320046 (312.5 KiB)

Original issue reported on code.google.com by Keepe...@gmail.com on 11 Sep 2011 at 2:33

GoogleCodeExporter commented 8 years ago 
Okey, i've it figured out partially...

If i do a factory reset and configure the iptvwan to DHCP, it starts 
working...but if for some reason, i change iptvwan connection type to "none" 
when it has an ip, and the multi-vlan is set, the interface "dies" - no matter 
how many reboots are done.

To sort this out there's two options: set the iptvwan to "none" and untick the 
"Enable IPTV WAN Setup". Reboot. Set the iptvwan to "dhcp", press ok. tick the 
"Enable IPTV WAN Setup". Reboot again OR do a factory reset.

Original comment by Keepe...@gmail.com on 12 Sep 2011 at 8:43

GoogleCodeExporter commented 8 years ago 
correction: setting the "connection type" to "DHCP" BEFORE enabling the IPTV 
WAN (and rebooting the router), makes the vlan interface die too.

Correct procedure so to make the iptvwan work normally:

1) tick "Enable IPTV WAN Setup"
2) reboot
3) set iptvwan connection type to DHCP.
4) done.

Original comment by Keepe...@gmail.com on 12 Sep 2011 at 9:28

GoogleCodeExporter commented 8 years ago 
Can you try the latest RC firmware ?
http://code.google.com/p/vigor2130/downloads/detail?name=v2130_r2384.all&can=2&q
=#makechanges

Original comment by jht...@gmail.com on 13 Sep 2011 at 10:24

GoogleCodeExporter commented 8 years ago 
Well that firmware has some serious bugs...not only the IPTV dhcp interface 
doesn't get an ip (see attached pic), but also my wan vlan is changed by the 
router HIMSELF when i modify a port bridging ID:

WRONG:

root@Vigor2130:/etc/config# cat network

config 'interface' 'wan'
        option 'proto' 'dhcp'
        option 'hostname' 'Vigor2130'
        option 'disable' '0'
        option 'detect' '0'
        option 'type' 'bridge'
        option 'ifname' 'eth1.2'
...
...
...

CORRECT:

root@Vigor2130:/etc/config# cat network

config 'interface' 'wan'
        option 'ifname' 'eth1.100'
        option 'proto' 'dhcp'
        option 'hostname' 'FireAngel'
        option 'disable' '0'
        option 'detect' '0'
        option 'type' 'bridge'

...To sort this issue out, i have to edit with vi the network file and delete 
the eth1.2 vlan interface...after that, the eth1.100 appears by himlsef and i 
get an IP on Wan.

Do note that i've tested the 1.5.2 Beta (build 2168); 1.5.2_RC1 (build 2384) 
and 1.5.2_RC1 (build 2385).

From all three, only the build 2384 is making this problem with the WAN 
interface (modifying the eth1.105 to eth1.2 by himself) AND the IPTV wan ip 
issue.

Both other builds (2168 & 2385) still have the IPTV Wan ip issue.

Besides all this, all three releases have a problem with IGMP which constantly 
crashes with an error code (4). It's only observable on my part, when i'm lucky 
and can get an ip on iptv interface:

...
...
...

About to call timeout 2 (#0)
SENT Membership query   from 77.xx.xx.xx     to 224.0.0.1
Sent membership query from 77.xx.xx.xx to 224.0.0.1. Delay: 10
SENT Membership query   from 10.xx.xx.xx    to 224.0.0.1
Sent membership query from 10.xx.xx.xx to 224.0.0.1. Delay: 10
SENT Membership query   from 192.168.xx.xx   to 224.0.0.1
Sent membership query from 192.168.xx.xx to 224.0.0.1. Delay: 10
Created timeout 4 (#0) - delay 10 secs
(Id:4, Time:10) 
Created timeout 5 (#1) - delay 21 secs
(Id:4, Time:10) 
(Id:5, Time:21) 
RECV Membership query   from 77.xx.xx.xx     to 224.0.0.1
RECV Membership query   from 10.xx.xx.xx    to 224.0.0.1
RECV Membership query   from 192.168.xx.xx   to 224.0.0.1

RECV V2 member report   from 192.168.xx.xx    to 239.195.7.2
Should insert group 239.195.7.2 (from: 192.168.xx.xx) to route table. Vif Ix : 3
Updated route entry for 239.195.7.2 on VIF #3

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.195.7.2, Age:1, St: I, OutVifs: 0x00000008
#1: Src: 0.0.0.0, Dst: 239.196.1.10, Age:2, St: I, OutVifs: 0x00000008
#2: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000008
-----------------------------------------------------
RECV V2 member report   from 192.168.xx.xx   to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.xx.xx   to 239.255.255.250
Should insert group 239.255.255.250 (from: 192.168.xx.xx) to route table. Vif 
Ix : 3
Updated route entry for 239.255.255.250 on VIF #3

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.195.7.2, Age:1, St: I, OutVifs: 0x00000008
#1: Src: 0.0.0.0, Dst: 239.196.1.10, Age:2, St: I, OutVifs: 0x00000008
#2: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000008
-----------------------------------------------------

RECV V2 member report   from 10.xx.xx.xx    to 224.0.0.2
The IGMP message was from myself. Ignoring.

select() failure; Errno(4): Interrupted system call
Got a interupt signal. Exiting.
clean handler called
Removing route entry for 239.195.7.2
Route is not active. No kernel updates done.
Leaving group 239.195.7.2 upstream on IF address 10.xx.xx.xx
leaveMcGroup: 239.195.7.2 on eth1.105
Removing route entry for 239.196.1.10
Route is not active. No kernel updates done.
Leaving group 239.196.1.10 upstream on IF address 10.xx.xx.xx
leaveMcGroup: 239.196.1.10 on eth1.105
Removing route entry for 239.255.255.250
Route is not active. No kernel updates done.
Leaving group 239.255.255.250 upstream on IF address 10.xx.xx.xx
leaveMcGroup: 239.255.255.250 on eth1.105
All routes removed. Routing table is empty.
Shutdown complete....
root@Vigor2130:/etc# 

Do note that i DO NOT interrupt the igmp process with ctrl+c or anything else: 
it simply stops.

Original comment by Keepe...@gmail.com on 19 Sep 2011 at 12:21

Attachments:

GoogleCodeExporter commented 8 years ago 
i dont see this verion 1.5.2_RC1 (build 2385).

Original comment by ele.b...@gmail.com on 21 Sep 2011 at 3:29

GoogleCodeExporter commented 8 years ago 
I'm sorry, i forgot to mention - i didn't get it from here, which leads me to a 
question:

 I still haven't exactly understood if this is a open source community who is developing/compiling firmware builds based on the gpl, or if the project leaders in here are draytek employees (programming team), testing new builds...

Original comment by Keepe...@gmail.com on 21 Sep 2011 at 7:45

GoogleCodeExporter commented 8 years ago 
what i mknow is that the new beta firmware here  ar from th edevolopers from 
Draytek.

Could please share the firmware you got from th eother channel, Maybe it fixes 
some erors for me.

Original comment by ele.b...@gmail.com on 22 Sep 2011 at 2:03

GoogleCodeExporter commented 8 years ago 
I'm sorry but i do believe i'm not authorized to do that. Anyway, there's new 
builds coming which are more stable.

Original comment by Keepe...@gmail.com on 22 Sep 2011 at 7:09

GoogleCodeExporter commented 8 years ago 
do you know when? and is this on this site?

Original comment by ele.b...@gmail.com on 22 Sep 2011 at 7:27

GoogleCodeExporter commented 8 years ago 
No, it isn't. It ain't public.

anyway, on build 2398, it's possible to notice more specificaly what's going on 
with IGMP and why is it dropping out with "select() failure; Errno(4): 
Interrupted system call":

rootﾧVigor2130:/sbin# logread
...
...
...
Sep 22 23:35:45 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:35:47 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:35:48 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:35:50 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:35:55 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:36:00 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:36:06 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:36:10 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:36:15 daemon.err syslog: udp_send: could not send message using 
socket 11
Sep 22 23:36:21 user.info syslog: check igmpproxy status ... stop igmpproxy !
Sep 22 23:36:22 user.info : killall: igmpproxy: no process killed
rootﾧVigor2130:/sbin# 

Regarding the iptv wan interface it seems that you cannot undo it all in one 
click via webpage...i'll explain what i mean: if you have an ip on IPTVWAN and 
you bridge it with say, port 4/VLAN 105, it will work well. BUT if for some 
reason you untick the bridge, it will "crash" the IPTV interface. To sort this 
out, you'll need to:

1)untick the "Enable IPTV WAN Setup"
2)go into "IPTV WAN Setting" and set it from "DHCP" (that's what my isp uses so 
to get an ip on iptv vlan interface) to "NONE".

3)go into "IPTV WAN Setting" again and set the interface from "NONE" to "DHCP"
4) tick "Enable IPTV WAN".

after all this, i can get an ip again.

Original comment by Keepe...@gmail.com on 22 Sep 2011 at 10:50