News: This forum is now permanently frozen.
Pages: [1] 2
Topic: Monowall to Monowall  (Read 4680 times)
« on: December 20, 2012, 14:03:16 »
spinne84 *
Posts: 10

Hello together,

I have a problem to access from the local Lan (Monowall 2) and from the local Lan (Monowall 1) to my WLAN Routers (see pitcture attached).
The green arrow means that this connection is working. The red arrow not.

Now I am not sure if it is a routing problem or a firewall problem.

Thank you!
Spinne84


* Unbenannt.JPG (27.54 KB, 567x197 - viewed 502 times.)
« Last Edit: December 20, 2012, 14:06:04 by spinne84 »
« Reply #1 on: December 20, 2012, 14:18:11 »
tuxfux *
Posts: 32

Hi,

i am not a pro, but i guess with details to the firewall and nat settings would help to find the problem. in addition also over what ip and port you would like to reach the wlan-router. also details about the subnets would be nice. can you include them in the pic? espessialy the settings from m0n02.

like

Code:
                                                 wlan
                                              195....3/24
                                              195....1/24
client                    mono1                    mono2             client
192....3/24          193....1/24           194....1/24       194....3/24



ok not quite good and complete, just that you get what i mean....



cheers
Fliege84  Tongue
« Reply #2 on: December 20, 2012, 14:25:25 »
iridris ***
Posts: 145

The problem is most likely the firewall, as I believe m0n0wall handles the routing of IPsec tunnels automatically.

IPsec connections have their own firewall tab besides LAN/WAN - have you allowed the appropriate IP addresses through?
« Reply #3 on: December 20, 2012, 14:39:46 »
spinne84 *
Posts: 10

Thank you for the fast answers! Also to Fliege84!   Cheesy

Please find attached the rules from the "Monowall 2".


                                                                             wlan
                                                                             172.16.10.15/24
                                                                             172.16.10.240/24
client                             mono1                              mono2                           client
192.168.12.3/24          192.168.12.230/24           192.168.10.240/24       192.168.10.3/24

Thank you for your help!!!


* DMZ Rules.JPG (32.76 KB, 590x294 - viewed 589 times.)

* LAN Rules.JPG (27.92 KB, 580x243 - viewed 539 times.)
« Last Edit: December 20, 2012, 15:32:14 by spinne84 »
« Reply #4 on: December 20, 2012, 15:14:37 »
tuxfux *
Posts: 32

i guess
wlan
172.166.10.15/24

is a typo.

i also guess you crossposted wirth iridris. well he is right. since you come over ipsec you need to configure there. but from lan it should work. what do you get if you trace from lan (192.168.10.3/24) to wlan ( 172.166.10.15/24)? i guess when you ping you gad a bad reply from m0n02...

if you have ssh enabled, what happens if you do it from the shell of the m0n0? (well i use pfsense, so i am not sure if it is the same with it's father m0n0...), well that should def. work. hm... i guess others could suggest something better Smiley

if you did not configure the firewall rulez from ip sec, do that and test it. than we might come closer.
« Reply #5 on: December 20, 2012, 15:32:00 »
spinne84 *
Posts: 10

oh shit, sorry! It was a failure of me!

wlan accesspoint is 172.16.10.15/24

Please find attached the IPsec rules.
I have no possibility to use this monowall with ssh!?
Yes you are right, if I ping from lan (192.168.10.3/24) to wlan ( 172.16.10.15/24) I get a bad response.



* IPsec.JPG (26.74 KB, 585x253 - viewed 489 times.)
« Reply #6 on: December 20, 2012, 15:55:13 »
spinne84 *
Posts: 10

I could solved one problem by myself.

Now I can ping the WLAN Acces Point (172.16.10.15/24) from the monowall2 LAN.

But now I need also access from the monowall 1 LAN...


* LAN.JPG (26.29 KB, 554x180 - viewed 456 times.)

* Captivate portal.JPG (43.34 KB, 570x288 - viewed 471 times.)
« Last Edit: December 20, 2012, 17:02:42 by spinne84 »
« Reply #7 on: December 20, 2012, 21:48:09 »
tuxfux *
Posts: 32

it would be nice to tell why it works the one connection now, in case someone is browsing for a similar problem.

when you trace from lan monowall 1, what do you get?
« Reply #8 on: December 20, 2012, 22:09:58 »
spinne84 *
Posts: 10

Yes, of course thats right! Sorry!
I added the screenshot but no text...
In my last screenshot there is a entry in the Captive portal!
I added the IP Address of the WLAN AccessPoint. After that I got a connection from the monowall 2 and the LAN (192.168.10.0/24) segment to this AccessPoint.

But now I think it is necessary to tell the monowall 1 that there is a segment (172.16.10.0/24) at the monowall 2? I tried to add a rule (the grey one), but is is not working.


* Unbenannt.JPG (29.07 KB, 578x283 - viewed 459 times.)
« Last Edit: December 20, 2012, 22:11:55 by spinne84 »
« Reply #9 on: December 21, 2012, 02:05:28 »
tuxfux *
Posts: 32

ah yes of course. i think this addresses to problem: http://doc.m0n0.ch/handbook/faq-ipsec-multiple-subnets.html
-> in pfsense: system -> static routes

don't forget that in the basic setup, the privat addresses are in default conf blocked. so you need to allow rfc 1918.

i guess you are aware of the fact, that grey rulez are disabled (so you disabled it, because it did not help. right?)

good luck

« Last Edit: December 21, 2012, 02:13:56 by tuxfux »
« Reply #10 on: December 21, 2012, 08:24:28 »
spinne84 *
Posts: 10

Yes, you are right. I disabled the grey rule becuase it was not working.

I do not understand why I must allow rfc 1918? Because the other private addresses 192.168.10.0 to the monowall 2 are already working.

So I tried to add a static rule (see picture).  But without success.


* static route.JPG (42.33 KB, 649x326 - viewed 530 times.)
« Reply #11 on: December 21, 2012, 14:34:44 »
tuxfux *
Posts: 32

to be honest, your pic is a bit unhelpfull here. you should write each ip on the side of the device it is. my "ascii pic" was a bit missleading i guess. sorry about that.

you need to put the other side 192.168.10.? ?? of the interface from monowall2 WAN as gateway. your router knows it's own interfaces. so when you wanna go to an other "unknown" network. you say on m0n01 send it to m0n02. the second m0n0wall knows then the other network an consequently where to send it.

or simpler: tell m0n01 to send it to monowall2 it knows what to do with it.

good luck with it.
« Last Edit: December 22, 2012, 00:42:39 by tuxfux »
« Reply #12 on: December 22, 2012, 09:45:50 »
spinne84 *
Posts: 10

Hello tuxfux,

at first: Thank you very much for yor help!!!

But I am still not able to say to "m0n0 1" that he should send all 172.16.10.0/24 requests to "m0n0 2".

Could it be that there is something wrong with the back route?
Hence I have modifyed my pic again with more information:


* Architektur.png (176.63 KB, 652x1336 - viewed 518 times.)
« Last Edit: December 22, 2012, 09:51:54 by spinne84 »
« Reply #13 on: December 22, 2012, 14:41:08 »
tuxfux *
Posts: 32

hey spinne,

well saidly i couldn't help you so far... i have to admint that i have never done something like that by myselfe.

first of all you need to reactivate the disabled firewall route for the ipsec network. test it then again. if it still does not work:
can you post the output of traceroute (where you made the ping but the other thing Wink ). this might give a clue, the thing is i don't have any Smiley.

@others: any suggestions?

be aware of the fact, that i might not answer very fast in the next 2-3 days.
« Reply #14 on: December 22, 2012, 14:42:33 »
tuxfux *
Posts: 32

oh and one question. the green arrow from mono1 to mono2 is over ipsec. right?
 
Pages: [1] 2
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines