D-Link DIR-825 Client Bridge media sharing problem

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page 1, 2, 3, 4, 5  Next
Author Message
brandonf360
DD-WRT Novice


Joined: 15 Sep 2012
Posts: 14

PostPosted: Sat Sep 15, 2012 6:46    Post subject: D-Link DIR-825 Client Bridge media sharing problem Reply with quote
Hi I have been searching for for a couple weeks now for an answer to this problem and have had no luck, If there is another post pointing toward the fix please redirect me because I can not find it my self.

My problem is Media streaming (dlna on Windows media player/xbox 360, etc.) will not work over the client bridge. It used to work on my old linksys broadcom wireless g running ddwrt and setup as a repeater bridge, but the DIR-825 is filtering this SSDP/Multicast traffic.

The xbox in the living room can not see PC's on the other end of the bridge anymore, and like wise on those PC's I can't see the xbox.

Is there commands I can run to enable this traffic or is it a problem on atheros based hardware?

My Current setup is
AP
Motorola NVG510 AT&T uverse modem

CB
D-Link DIR-825 rev b1 running
DD-WRT v24-sp2 (07/20/12) std - build 19519

Any help would be GREATLY appreciated!!
Sponsor
brandonf360
DD-WRT Novice


Joined: 15 Sep 2012
Posts: 14

PostPosted: Tue Sep 18, 2012 0:23    Post subject: Reply with quote
bump

any ideas on this?
brandonf360
DD-WRT Novice


Joined: 15 Sep 2012
Posts: 14

PostPosted: Fri Sep 28, 2012 3:41    Post subject: Reply with quote
Just an update for anyone else looking into this problem.

When creating a client bridge you are not getting a true transparent hardware bridge.
A program called relayd runs to create your virtual bridge. This part works fine for my DIR-825. The problem is relayd to my knowledge does not pass on IGMP multicast traffic. Another program is supposed to run on DD-wrt called igmprt which from what I can tell is just DD-wrt's version of IGMPproxy. This program allows multicast traffic to pass through your bridge.

This program is running on a default config when I do a 30/30/30 reset, how ever after configuring my wireless to be a client bridge, it gets turned off somehow, that is why SSDP/media sharing is not working over my bridge.

I tried manually adding my own config to jffs2 and running igmprt from a command line with:
igmprt -d /jffs2/etc/igmpproxy.conf
but the program fails saying that I must provide an upstream and a downstream interface, Maybe I didn't use the right interface names in the config I'm not sure, I believe i used ath0 for upstream and br0 for downstream.

So for anyone looking to fix media sharing, you must get igmprt process running after getting the bridge all setup and working. If anyone succeeds please post back with your igmpproxy.config, and likewise if I get it figured out I will post back.
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Wed Oct 03, 2012 22:10    Post subject: Reply with quote
Ahhh brandonf you are right, got it working!!!!
I dont know if all steps are really neccessary, I will try tommorrow but for now it is running!!



My dd-wrt has IP 192.168.5.160.
WLAN interface is ath0 (DLNA-Server 192.168.5.10 connected via 2nd WLAN-router)
Ethernet interface is br0 (Blue Ray player 192.168.5.104 connected to this interface)

What I have done:

1) create virtual interface ath0:0 (dont know if neccessary, used random unused IP 192.168.5.199)
ifconfig ath0:0 192.168.5.199 up

Interfaces look like this now

root@DD-WRT:~# ifconfig
ath0 Link encap:Ethernet HWaddr F8:D1:11:B0:69:F4
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:881810 errors:0 dropped:0 overruns:0 frame:0
TX packets:1153119 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:117683179 (112.2 MiB) TX bytes:1673961786 (1.5 GiB)

ath0:0 Link encap:Ethernet HWaddr F8:D1:11:B0:69:F4
inet addr:192.168.5.199 Bcast:192.168.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br0 Link encap:Ethernet HWaddr F8:D1:11:B0:69:F3
inet addr:192.168.5.160 Bcast:192.168.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1143987 errors:0 dropped:6 overruns:0 frame:0
TX packets:877813 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1629552037 (1.5 GiB) TX bytes:116734233 (111.3 MiB)

br0:0 Link encap:Ethernet HWaddr F8:D1:11:B0:69:F3
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr F8:D1:11:B0:69:F3
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:4

eth1 Link encap:Ethernet HWaddr F8:D1:11:B0:69:F5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1143987 errors:0 dropped:0 overruns:0 frame:0
TX packets:877813 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1645567855 (1.5 GiB) TX bytes:116734233 (111.3 MiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:156 errors:0 dropped:0 overruns:0 frame:0
TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11352 (11.0 KiB) TX bytes:11352 (11.0 KiB)


2) create igmpproxy.conf:

quickleave
phyint ath0:0 upstream ratelimit 0 threshold 1
altnet 10.0.0.0/8
altnet 192.168.5.0/24
altnet 239.255.255.250/24
phyint br0:0 downstream ratelimit 0 threshold 1
phyint br0 downstream ratelimit 0 threshold 1
phyint eth1 downstream ratelimit 0 threshold 1



3) start igmprt
igmprt -vv -d igmpproxy.conf


Now the BD-player can see the DLNA-Server at the other side of the WLAN-Bridge!!!
Please try if also working for you, if needed I will provide a more comprehensive step-by-step instruction...
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Thu Oct 04, 2012 11:44    Post subject: Reply with quote
Sad Sad Sad

rebooted all devices today, applied the same settings...and does not work anymore Sad

This really sucks...

And no, there has not been a cabled connection between DLNA-Server and BR-player....
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Thu Oct 04, 2012 13:48    Post subject: Reply with quote
Now it works again...detection seems to be random event. Once the DLNA-Server is detected by the BR-plyer, igmprt can be turned of again anyway...

I think the problem is, that both interfaces of the dd-wrt are on the same subnet, so igmprt does not know where to send the packets to?


Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.5.104, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
Route activate request from 192.168.5.10 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.5.104 to 192.168.5.10

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.5.10, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
Route activate request from 192.168.5.104 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.5.10 to 192.168.5.104
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Fri Oct 05, 2012 13:15    Post subject: Reply with quote
OK, I think now I got it. Not the nicest solution but it works - configurable with web-interface and autostart Smile
I rebooted all devices several times and DLNA is detected all times without any delay Smile

I think the trick is to send the packets received from the upsteam-interface back to the same interface again...for this purpose I added additional virtual interfaces....


Just go to administration-->Commands.

I misuse the "Custom Script" which can be found under /tmp/custom.sh as configuration file for the igmprt Wink

Just add:
Startup:
ifconfig ath0:0 192.168.5.154 up
ifconfig ath0:1 192.168.5.155 up
ifconfig br0:1 192.168.5.156 up
/usr/sbin/igmprt /tmp/custom.sh

Custom Script
phyint ath0:0 upstream
phyint ath0:1 downstream
phyint br0:1 downstream
phyint br0:0 downstream
phyint br0 downstream

Dont forget that your Network-Number maybe other than 192.168.5.XXX. The IPs I assigned in "Startup" are randomly selected and unused.

If your dd-wrt is not reachable anymore via web-interface after this try all IPs you assigned above...

If not working try to launch command "ps" and look if igmprt is really running. If not try to launch
/usr/sbin/igmprt /tmp/custom.sh
manually

Please try and give feedback...
tingu
DD-WRT Novice


Joined: 20 Jul 2012
Posts: 11

PostPosted: Sat Oct 20, 2012 15:20    Post subject: Does not seems to be working Reply with quote
I tried to configure according to your step, but it does not seems to be working.

Instead of 192.168.5.XXX I have used 192.168.1.XXX

But still My Samsung TV is not able to see my Computer.
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Tue Oct 23, 2012 18:38    Post subject: Reply with quote
hmmm..for me its still working..sometimes igmprt does not autostart, but after starting manually it works...

can you post the output of

a) ifconfig
b) cat /tmp/custom.sh
c) /usr/sbin/igmprt -d -vv /tmp/custom.sh
tingu
DD-WRT Novice


Joined: 20 Jul 2012
Posts: 11

PostPosted: Sat Oct 27, 2012 12:36    Post subject: Reply with quote
predator666 wrote:
hmmm..for me its still working..sometimes igmprt does not autostart, but after starting manually it works...

can you post the output of

a) ifconfig
b) cat /tmp/custom.sh
c) /usr/sbin/igmprt -d -vv /tmp/custom.sh


First of all I apologise for the delayed reply.... and thanks for trying to help me.

After Telnetting I used ps command and saw /usr/sbin/igmprt /tmp/custom.sh in the process list.

Following are the output for
1) ifconfig

root@DD-WRT:~# ifconfig
ath0 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48981 errors:0 dropped:3666 overruns:0 frame:0
TX packets:19077 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:6000535 (5.7 MiB) TX bytes:5445023 (5.1 MiB)

ath0.1 Link encap:Ethernet HWaddr 92:XX:XX:XX:XX:A6
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:32
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ath0:0 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A6
inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

ath0:1 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A6
inet addr:192.168.1.251 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br0 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A5
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10483 errors:0 dropped:0 overruns:0 frame:0
TX packets:34154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:667650 (652.0 KiB) TX bytes:1716099 (1.6 MiB)

br0:0 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A5
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br0:1 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A5
inet addr:192.168.1.252 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A5
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:4

eth1 Link encap:Ethernet HWaddr 90:XX:XX:XX:XX:A7
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10484 errors:0 dropped:0 overruns:0 frame:0
TX packets:34152 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:814472 (795.3 KiB) TX bytes:1716015 (1.6 MiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 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:674 (674.0 B) TX bytes:674 (674.0 B)

mon.ath0.1 Link encap:UNSPEC HWaddr 90-XX-XX-XX-XX-A6-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:886623 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:225655928 (215.2 MiB) TX bytes:0 (0.0 B)


b) cat /tmp/custom.sh
root@DD-WRT:~# cat /tmp/custom.sh
phyint ath0:0 upstream
phyint ath0:1 downstream
phyint br0:1 downstream
phyint br0:0 downstream
phyint br0 downstream
root@DD-WRT:~#


c) /usr/sbin/igmprt -d -vv /tmp/custom.sh
root@DD-WRT:~# /usr/sbin/igmprt -d -vv /tmp/custom.sh
Searching for config file at '/tmp/custom.sh'
Config: Got a phyint token.
Config: IF: Config for interface ath0:0.
Config: IF: Got upstream token.
IF name : ath0:0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 1
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface ath0:1.
Config: IF: Got downstream token.
IF name : ath0:1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface br0:1.
Config: IF: Got downstream token.
IF name : br0:1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface br0:0.
Config: IF: Got downstream token.
IF name : br0:0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface br0.
Config: IF: Got downstream token.
IF name : br0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : 0
buildIfVc: Interface lo Addr: 127.0.0.1, Flags: 0x1049, Network: 127/8
buildIfVc: Interface br0 Addr: 192.168.1.2, Flags: 0x1043, Network: 192.168.1/24
buildIfVc: Interface br0:0 Addr: 169.254.255.1, Flags: 0x1043, Network: 169.254/16
buildIfVc: Interface br0:1 Addr: 192.168.1.252, Flags: 0x1043, Network: 192.168.1/24
buildIfVc: Interface ath0:0 Addr: 192.168.1.250, Flags: 0x1043, Network: 192.168.1/24
buildIfVc: Interface ath0:1 Addr: 192.168.1.251, Flags: 0x1043, Network: 192.168.1/24
Found config for br0
Found config for br0:0
Found config for br0:1
Found config for ath0:0
Found config for ath0:1
MC-Router API already in use; Errno(125): Address already in use
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Sat Oct 27, 2012 13:34    Post subject: Reply with quote
hmmm...at the first sight, the output looks exactly like mine.

Are you sure the DLNA-server is OK? Does everything work when using a wired connection?

How long did you wait for a detection? Tried to keep it running for 30 minutes or so?
tingu
DD-WRT Novice


Joined: 20 Jul 2012
Posts: 11

PostPosted: Sat Oct 27, 2012 14:44    Post subject: Reply with quote
predator666 wrote:
hmmm...at the first sight, the output looks exactly like mine.

Are you sure the DLNA-server is OK? Does everything work when using a wired connection?

How long did you wait for a detection? Tried to keep it running for 30 minutes or so?


Thanks for the prompt reply...
WR740NV4 with stock firmware works with DLNA but when not with dd-wrt. The reason why I changed to dd-wrt was because I had to follow a cretain sequence of changing the IP address of my Samsung TV to get the TV recognise my router(740N is connected to TV using LAN cable) and then after sometime the tv againg gets disconnected.

But there is no such problem with dd-wrt (the connection stays) but then DLNA does not work Very Happy

So basically its a catch 22 situation and my preference is to be with DD-WRT.
predator666
DD-WRT Novice


Joined: 28 Jul 2012
Posts: 14

PostPosted: Sun Oct 28, 2012 8:49    Post subject: Reply with quote
Hmm, sounds strange.

Honestly speaking...I have no idea and I am not an expert for this. Your settings should be the same as mine.

Maybe you can check, that you have disabled your firewall on the dd-wrt (all disabled, nothing checked).

UPNP on the dd-wrt is also disabled in my configuration.
brandonf360
DD-WRT Novice


Joined: 15 Sep 2012
Posts: 14

PostPosted: Wed Nov 07, 2012 0:41    Post subject: Reply with quote
predator666 thank you for the replys!! So Glad to see I wasn't alone on this lol. I ended up giving up on my dir-825 and got a Buffalo Wireless AC router and the matching bridge, This ended up working better for me in the end (500+mbps between 2 houses Very Happy) but now I am going to break out the dir-825 to get it setup as a bridge for the living room PC @ 300mbps (hopefully). I'll post back with my results again thank you!!
neoblaster
DD-WRT Novice


Joined: 07 Dec 2012
Posts: 1

PostPosted: Sun Dec 09, 2012 4:44    Post subject: Reply with quote
predator666, I have to thank you very much for the solution you submitted, it worked perfectly for me, although my configuration is different: PC with PS3 Media Server connected to main router(D-link DIR-655), Sony BDP-S370 connected to AP(TP-Link TP-WA801NDv1) with DD-WRT v24-sp2 (07/20/12) std - build 19519, client bridge mode. Bluray couldn´t see PMS, but after applying startup and custom script instructions it worked like a charm.

Very Happy Very Happy Very Happy
Goto page 1, 2, 3, 4, 5  Next Display posts from previous:    Page 1 of 5
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum