News: This forum is now permanently frozen.
Pages: [1]
Topic: Apple Home Sharing on bridged NICs not working  (Read 2244 times)
« on: December 20, 2013, 23:56:24 »
weust **
Posts: 54

Not 100% sure I should post this here, but since I am running a beta version I'd figure I post here first.

I am running version 1.8.1b546 and am trying to get Apple Home Sharing to work.

My Soekris 6501 has Opt1 and Opt2 bridged to LAN.
On LAN a Apple Airport Extreme is connected, which is set to Bridge Mode.

The Mac Mini (with iTunes, which I want to connect to via Remote on the iPad or iTunes on another Mac) is connected on Opt2.
From another Mac that is connected to a port on the Airport Extreme, I can share the Mac Mini's screen.
This also works with a Remoter app on the iPad just fine.

Connecting the Mac Mini to the Airport Extreme makes the Mac see the shared library in iTunes from the Mac Mini.
But when I want to connect to shared library when the Mac Mini is on the Opt2 connection, I get a timeout.
The Firewall log shows a Deny from the Mac Mini on TCP 3689 (one of the two ports needed from Home Sharing) to the Mac on a much higher port number (dynamic).

That to me seems kind of weird, as the Rules show that on LAN anything if passed to anything.
Same goes for Opt1 and Opt2.

I tried setting up some rules, but that didn't work.
So I probably did something wrong there, but just got no clue what.

Really hope someone can help me out here.
« Reply #1 on: January 03, 2014, 07:11:47 »
weust **
Posts: 54

I plugged in a computer to OPT2 that needs to get a IP address via DHCP from the DHCP server on OPT1, but isn't allowed too.

Lines I see in the Firewall log are:
Code:
If Source Destination Proto
OPT2 0.0.0.0, port 68 255.255.255.255, port 67 UDP
« Reply #2 on: January 03, 2014, 18:06:26 »
Fred Grayson *****
Posts: 994

Have you enabled any rules on any interfaces that might be needed to pass the required traffic?

--
Google is your friend and Bob's your uncle.
« Reply #3 on: January 08, 2014, 15:31:33 »
weust **
Posts: 54

No, I haven't because the default rules on each port allows all incoming and outgoing traffic.
If I would need to set up rules to allow something, I would need to set up a rule for allowing VNC traffic too.
Yet, that one works fine.
« Reply #4 on: January 08, 2014, 15:32:24 »
weust **
Posts: 54

Btw, I updated to build 556 but haven't tested yet.
And since there is no changelog on 556 yet I don't know if it might resolve anything.

« Reply #5 on: January 08, 2014, 15:41:48 »
Fred Grayson *****
Posts: 994

I am not sure, but it may be that broadcast traffic can't be passed across interfaces.

--
Google is your friend and Bob's your uncle.
« Reply #6 on: January 08, 2014, 16:16:30 »
weust **
Posts: 54

That would explain why DHCP won't work, but not normal TCP or UDP traffic.
Or specific TCP and UDP traffic.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines