"with a static IP set through the TP-Link"
What? So the way I am picturing your setup
internet -- pfsense (lan) --- (lan)tp-link(lan)-- linuxserver
Then wireless your TV and other clients connect to your tp-link which is being used as switch and wireless AP.
So your pfsense is on 192.168.0.1 on its LAN, your choice of default gateway a bit confusing there - lan interfaces would not have a gateway set. So I take it this is the IP of your lan inteface on your wan.. Other devices on your network use this .0.1 address as the default gateway to get to the internet.
So your TV is at 188.8.131.52 and wireless, and this is how? Static? With gateway of .0.1
Now your linux box is set how? dhcp or static? And its address is 192.168.0.? with a gateway of .0.1
And meaningless info is your tp-link IP for management of wireless is .0.2, but its dhcp server is OFF!!
Now I would assume your dns points to your pfsense .0.1 address?
What server is not starting your linux box? When the pfsense is unplugged? That makes little sense, why would it not start just because its gateway is not available - does it need the internet for something to start, dns maybe?
Notice in your sniff - that multicast is sent to mac of 01: which is correct its a multicast, so mac would first have to end in 1 to say hey I am multicast. I would really check to see if your wireless clients are seeing this traffic sent to this sort of address?
I am going verify with a wireless laptop when I get home, I run the same sort of setup - but old linksys router running tomato as my AP. But don't do anything with multicast on my network, and normally have igmp snooping enabled on my core switch to block the traffic - because on my network its just noise that I don't need to see.
But if devices are assigned statically - I don't see why they wouldn't work just because your gateway is not there. What do these services do that they need to get off the network for? If they hang because not talking to dns, have seen this before - then just bring up a dns server on your local network and point to that for the testing.. Your using local domain?? For example I use local.lan for all my devices dns. Serve that up off say your linux box if dns is needed for stuff to start.
No, I would only use the static IP if something were to happen to my pfSense box, and I needed to set it back up to be a router again, instead of a Wireless AP and switch. (I don't trust the onboard networking on the pfSense box that far). The setup goes like this:
Linksys CM100 (Cable) ---> Nvidia nForce 430 Onboard LAN Adapter (WAN in this setup) ---> Rosewill RC100 PCI LAN Adapter (LAN in this setup) ---> Port #1 on the TP-LINK WR841ND (that used to function as a Wireless Router, now functions as both a Wireless AP and switch) and then my computer (Fedora 17 desktop) connects to port #2 on the TP-LINK WR841ND.
Right, pfSense's default gateway is 192.168.0.1, and if I pull up ifconfig on Fedora, it shows a default gateway of 192.168.0.1, and I set the TP-LINK as 192.168.0.2 (as per the "Using pfSense with an existing router" how-to).
All devices on the network (my computer (currently 192.168.0.100), 2 wireless desktops (currently 192.168.0.103 and 192.168.0.104 respectively), a Samsung Galaxy Tab 7 (currently 192.168.0.105) and the TV (currently 192.168.0.106) are all set up through DHCP.
Exactly, default DNS shows as 192.168.0.1 in ifconfig and in the Windows IP Configuration.
PS3 Media Server (the one I've used for streaming since I got the TV last year) refused to start at all. No errors or anything. Just sat there and did nothing. When I reconnected pfSense after trying to test just the TV and my computer on the TP-LINK (set up at that point through static addresses because the DHCP server is disabled over there as per the "Using pfSense with an existing router" how-to", I reset the connection to use DHCP, and it started again. It was weird.