5 Eth ports and Bridge issue
-
I can help with the switch…
plug in the power.
run a cat5 cable from your pfsense lan to any cat5 port on the switch.
plug all your computers and laptops and stuff into any of the remaining switch ports you like in any order.
Yep - That should do it...
-
It's a disease.
-
I can help with the switch…
plug in the power.
run a cat5 cable from your pfsense lan to any cat5 port on the switch.
plug all your computers and laptops and stuff into any of the remaining switch ports you like in any order.
Yep - That should do it...
excellent! you made my day 8)
-
Completely broken. You have 4 interfaces on the same subnet.
- Assign the BRIDGE to LAN, not individual interfaces. All those LAN emX should be set up as IPv4/IPv6 - None/None
- Go to System - Advanced - System Tunables and flip net.link.bridge.pfil_member to 0 and net.link.bridge.pfil_bridge to 1
- Reboot
I'd suggest reset to factory defaults and restarting from scratch.
Alternatively, get a $20 switch and stop wasting interfaces. Stick everything but the TP Link on the switch, set up a separate OPT interface (in a different subnet!!!) for the AP, connect it to the LAN port of the AP and turn off any DHCP there.
I appologize for double post, i got almost everything to work, except i cannot access opposing subnet:
interfaces i got:
1. WAN
2. LAN
3. ROUTER
Firewall NAT:
192.168.1.0 – LAN
192.168.2.0 -- ROUTERHelp :)
-
Where are you testing from? How are you testing?
What firewall rules do have?
Do you see hits in the firewall logs when you try to access the other subnet?Steve
-
Where are you testing from? How are you testing?
What firewall rules do have?
Do you see hits in the firewall logs when you try to access the other subnet?Steve
I was pinging it from windows side, win 7 and other win 8 it was time out. I managed to get it working, by adding 2 firewall rules. I attached 2 pics. Thank you for you help. I love when things starting to work out!!!!!
**EDIT
I got excited…. I cant access my NAS server with //192.168.1.3, but I can access web gui, any ideas?
-
By '//192.168.1.3' you mean access it as a Windows share? And you can access it that way from within the 192.168.1.0/24 subnet?
Does your NAS have any restrictions? It may not allow traffic from outside its own subnet. It may not be able to respond if it doesn't have a route back, so bad subnet mask or gateway.
Does the NAS have any logs you can look at?Steve
-
By '//192.168.1.3' you mean access it as a Windows share? And you can access it that way from within the 192.168.1.0/24 subnet?
Does your NAS have any restrictions? It may not allow traffic from outside its own subnet. It may not be able to respond if it doesn't have a route back, so bad subnet mask or gateway.
Does the NAS have any logs you can look at?Steve
yes I meant windows side, and yes I can access it within the 192.168.1.0/24 subnet. Its a FreeNAS. Im trying to find the logs but I don't see any, but here is network summary I got on freeNas:
Name IPv4 Address IPv6 Address
em0 192.168.1.3/24
Nameserver
192.168.1.1
192.168.2.1
Default route
192.168.1.1 -
This could also be windows firewall getting in the way. It will see the NAS as being in a different network zone so may not allow the traffic deppending how you have it set.
Steve
-
This could also be windows firewall getting in the way. It will see the NAS as being in a different network zone so may not allow the traffic deppending how you have it set.
Steve
thanks bud, ill play around with it more, if not ill connect my wifi router to my switch :)
-
Yes if your going to route all traffic out a specific gateway, your vpnv4 then you have to allow rules to get to your other networks. You can use the aliases for the network in the dropdown list, ie lan and rtn66u
See how your lan rules show lan net for the source.
-
Yes if your going to route all traffic out a specific gateway, your vpnv4 then you have to allow rules to get to your other networks. You can use the aliases for the network in the dropdown list, ie lan and rtn66u
See how your lan rules show lan net for the source.
ahh i see, so add another rule for LAN : source LAN net Destination RTN66U net and for RTN66U: source RTN66U net and destination LAN net. Im beeing retarted, just woke up :) Thanks again for your help
-
I would not expect that to make any difference since those aliases are what you already had in place; LAN net = 192.168.1.0/24 and RTN66U net = 192.168.2.0/24. Unless I've misread something.
Steve
-
doesn't make any difference to the rule.. but just makes it look cleaner ;)
-
Yep, also means you don't have to change the firewall rules if you change the interface subnet.
Steve
-
doesn't make any difference to the rule.. but just makes it look cleaner ;)
I like things to look clean ;) btw im going rethink my whole network, sketch it first. Thank you guys for you time and help
