From: Maciej Soltysiak <maciej@soltysiak.com>
To: Justin Madru <justin.jdm64@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] DLNA with wired and wireless devices
Date: Wed, 16 Jan 2013 20:02:18 +0100 [thread overview]
Message-ID: <CAMZR1YAQgn=_acjuMkyVC9h0ZT7GbqWiExcQ6vUJ7H7PNvnVJA@mail.gmail.com> (raw)
In-Reply-To: <CAJ5gi5L2XWr1BXh_2FNyDHVyFqMxyBdu5d-Ckp83AhbzL7tZwA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Wed, Jan 16, 2013 at 10:32 AM, Justin Madru <justin.jdm64@gmail.com>wrote:
> Hi,
>
> I have a wired DLNA server (minidlna) on the wired network, but require
> wireless devices to have access to it. It seems that with the default setup
> (the split of the wired and wireless into separate networks), devices on
> the wireless network are not able to discover the DLNA server.
>
> Is there a way to work around this? Or is the only solution to restore the
> traditional 192.168.x.x single network setup?
>
Yes, you can bridge everything as openwrt does and it should work.
However it was possible for it to work over multiple interfaces using
miniupnpd and minissdpd to forward 239.255.255.250 UDP broadcasts from ge00
to sw00 and sw10 and back. However, last time it worked for me in cero
was 3.3.x.
I was unable to fix it recent with 3.7.x versions yet and having little
time to work on it I'm almost making no progress.
If you have the inclination I would encourage you to try tinkering with it
to help out.
Regards,
Maciej
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
[-- Attachment #2: Type: text/html, Size: 2269 bytes --]
next prev parent reply other threads:[~2013-01-16 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 9:32 Justin Madru
2013-01-16 19:02 ` Maciej Soltysiak [this message]
2013-01-17 19:55 ` Maciej Soltysiak
2013-01-18 5:36 ` Justin Madru
2013-01-18 16:32 ` Dave Taht
2013-01-18 18:45 ` dpreed
2013-01-18 19:01 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMZR1YAQgn=_acjuMkyVC9h0ZT7GbqWiExcQ6vUJ7H7PNvnVJA@mail.gmail.com' \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=justin.jdm64@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox