Allow LAN to LAN, not routing
-
@lewis said in Allow LAN to LAN, not routing:
I had added a virtual (alias) IP with the IP of the storage device. I wanted to point out that I can already ping the storage device on their LAN.
The ping will not reach the device in the other network if the destination IP is on your own router!
Edit: Okay, KOM has the same idea and was faster.
-
Please guys, I appreciate the help, don't get impatient with me. I know you explained but this is not my network to break so am counting on you guys to help me do the right thing.
It makes sense that I can ping the IP if I added it on the local router. I had not thought about that.
Changing to hybrid won't break anything that is running now? I mean, will it require a reboot or something? Pfsense is always highly reliable and never need to reboot it but I'm asking since we are changing a 'mode'.
-
Changing the outbound NAT mode from automatic to hybrid does nothing. The automatically added rules are still in place and you're able to add manual rules.
-
NAT > outbound. Switch into the hybrid mode
Done.
save and add a new rule:
interface: LAN2The above is not clear to me. I've not create d a new interface and don't see one. I only see the usual WAN and LAN in Interface so I'm missing something before I can add rules next.
-
So the neighbours LAN is really not on an separate interface? It's connected directly to your LAN as John assumed?
-
The pfsense box has two interfaces only, WAN and LAN.
Our LAN subnet is 10.0.0.1/24.
On the LAN side, there are many other segments and I need to connect to a neighbors LAN and a storage device at 10.100.100.12.
They too route their own 10.100.100.1/24 subnet, have their own DHCP service, etc so I don't want to break anything on either subnet. -
As John mentioned above: That is never a good way to do anything.
However, you can give it a try.
At first your pfSense need an IP in the neighbours subnet. (IP Alias). Ensure to set the correct mask.
After you have added this you can select it at translation address in the outbound NAT rule.
At network select this one the NFS storage is connected to, guess LAN. -
Well, it's why I asked in the forums, because I don't want to do this in the wrong way :). So, what way should I do it or should I explain a bit more about what I am trying to accomplish?
-
As we already mentioned 15 posts ago, the correct way is to set up an separate transit network where you connect pfSense and the NFS to. This may also be a VLAN, so that there is no further hardware needed.
However, even with that you will need either a static route on the NFS storage or the Outbound NAT rule.
-
15 posts ago was different than what I just added about there being only two interfaces. I already explained this is beyond my level of knowledge with pfsense and you keep telling me it's simple, do this, do that but I've never done it before so cannot follow such advise.
-
It sounds like it's easy but it's not something I've ever had to deal with. At most, I've had to set up multiple WAN interfaces and route those which wasn't very hard but this is something different since I don't own that network yet it's on the same LAN as many other private subnets are so I don't want to break anything on our or anyone else's subnet.
Could someone please explain the steps, one by one. Once I see how this works, it will be another thing I've learned and will not have to ask about. Right now, there were a lot of replies and clarification so I really don't know what do do next.
-
So, can someone please give me the steps?
-
@lewis said in Allow LAN to LAN, not routing:
Yes, our traffic is allowed, it's me that is not sure what to do on our end as I don't want to break something.
I already explained this is beyond my level of knowledge with pfsense and you keep telling me it's simple, do this, do that but I've never done it before so cannot follow such advise.
Could someone please explain the steps, one by one.
So, can someone please give me the steps?
Please don't be offended, but it really sounds like you need to hire someone who knows what they're doing.
-
That's not very nice. I already explained that this kind of setup is new to me. I've been using pfsense for many years but I simply cannot mess this up since it's not my network to practice or learn on.
What's the point of a 'community' helping each other when they only help those who already know how.
-
Thing is, you have been told several times what steps are necessary. You are asking someone to spend at least a good part of an hour outlining the steps one by one for you.
Why should someone do that and not be compensated?
There is a difference between asking a question and demanding someone be your personal, uncompensated, consultant.
That is why you do not yet have a list of exact steps to take.
-
Demanding??????
There is no 'thing is'. I've never done this before and I added something that had not been mentioned/asked about in my original post so now I'm not sure what is what.
You help each other all the time, don't give me this nonsense about not being paid, you replied. I'm not asking for the world here, I'm asking for a little help from kind human beings which is what forums are all about.
What kind of stupid world are we building anyhow? I help people all the time and now I ask for a little help and you come back with this garbage that is said all the time in forums.
Just don't respond then and let someone help find the kindness to instead of motivating others not to. I've been struggling with this all day, I sure don't need your high and mighty hate friend.
Very nice community friend, very nice.
-
@lewis Please don't overreact. We're empathetic to your issue and you have received lots of replies and guidance. Derelict was being straight-forward even if it wasn't easy to hear.
If you want to go the static route method, you would need to know the network you want to connect to, possibly 10.0.1.0/24, and the address of their gateway. You can't create a route without it. Also, they would have to modify their firewall rules to allow you to talk to that NFS server or nothing will work.
I can't seem to find it here, but did you mention what the other network is connected to? Your diagram makes it look like they're connected directly to your pfSense instance and that probably isn't right.
-
You can try to justify your online friends behavior all you want but it's far from being straight forward. It's just unfriendly, rude and it's mean as the person receiving it.
There is no excuse for high and nightly behavior and only helping those who are already experts. Don't freaking help if you feel your help is worth too much that you cannot help those who are still learning.No one needs to be told these things in forums, it's absolutely insulting when you can clearly tell when someone is trying. I've been in forums long enough to tell when someone just wants the answers and is not willing to learn and this is not the case.
I said many times, I've never done this before, it's a live network that I cannot mess up.
I don't need any help at this point. I had to hire someone to do this tomorrow. Thanks so much for the help that was NEVER demanded. Such childish behavior in what I would have thought were professional forums.
-
huh? Just at a loss to how this got to you saying help and advice to you is offensive..
Your drawing looks like that 10.0.1 network is attached to your pfsense directly.. Which as already mentioned seems highly unlikely if your in a data center.
Your saying you have an interface on pfsense, a physical interface or vlan that is actually in the 10.0.1 network? And pfsense has an IP on this interface that is in this network? So all your devices are on the same L2? In a DC, and you just run whatever IP ranges you want? Again highly unlikely... I would not be in such a DC with my stuff that is for damn sure..
If you want to share data with another customer in the DC, then the DC would have to connect your networks, or provide a transit network between, etc..
As to your concern about routing? Sorry but its not possible for 2 different networks to talk to each other with out routing.. I have to concur with the other comments, you seem to be over your head.. And its prob best to hire the DC or someone that works with the DC where your stuff is located on how you and another customer there can share data..
-
Don't twist my words, I never said that.
I'm done with this thread if you're all going to try to justify shitty behavior. Talk to yourselves, get the lat word in if it means that much to you at this point because I'm not going to respond.
