News: This forum is now permanently frozen.
Pages: [1]
Topic: [INTERFACES] Can't add clients  (Read 4085 times)
« on: October 22, 2008, 18:46:57 »
bouyafa *
Posts: 11

I ve just set up my m0n0wall, i had configuring WAN, LAN, and it's working great. After i had to want add a new pc on the LAN. So i had bridge vr2 to the LAN interface (vr0), and add a new rule on the Firewall/Rules on the configuration page. All is open, this is identical to LAN.
M0n0wall can ping this new computer, but this one can't ping anyone. In the logs page, i can see that firewall is blocking this ip as : 18:42:06.718707      vr2      192.168.1.4, port 54948      192.168.1.1, port 53      UDP

I don't know what can i do more to set up a simple client :/ Anyone can help me ?

Thanks
« Reply #1 on: October 22, 2008, 19:13:55 »
Fred Grayson *****
Posts: 994

Why aren't you using a switch connected to your LAN interface and plugging all your PCs into the switch?

--
Google is your friend and Bob's your uncle.
« Reply #2 on: October 22, 2008, 19:40:41 »
bouyafa *
Posts: 11

Because i have 8 ethernet ports on my soekris.
« Reply #3 on: October 22, 2008, 22:36:54 »
bouyafa *
Posts: 11

Ok, i had just to change a things in my firewall rule ... the proto ... (erf) before i had TCP/UDP ... and just 'any' works ... :

*      *      *      *      *


It's very strange because my LAN interface have this to firewall rule :

TCP/UDP      *      *      *      *        


Suggests ?

« Reply #4 on: November 01, 2008, 15:29:36 »
bouyafa *
Posts: 11

Hello again ...

Sorry, but now i want to add a 3rd client machine on the vr3 interface. I ve tried to bridged vr3 with LAN, but a message say :
* Optional interface 1 (vr2) is already bridged to the specified interface.

In effect that true but how can i add simply client machine on the interfaces ?
« Reply #5 on: November 02, 2008, 13:38:35 »
bouyafa *
Posts: 11

Ok i ve just understand that I had to add new subnet for each interfaces, and it's works, all the machine connected to 192.168.3.0 and 192.168.4.0 have net access.

But now I want all the machines on 192.168.3.x subnet (for example), can access to 192.168.x.x subnet. How can I do ?
« Reply #6 on: November 02, 2008, 16:18:09 »
Fred Grayson *****
Posts: 994

For IP networking, every network interface in a machine has to define and belong to a unique network. You can not have two or more interfaces defining or belonging to the same network. That's just the reality of it - to have it any other way would be ambiguous and just not be capable of working.

Now that you have every interface defining a different network, you are going to have to have rules to allow traffic between interfaces. After all, this is a firewall. Not hard to do for the first extra interface, but as you add more, each and every interface is going to need rules to allow traffic between each and every other interface.

A cheap hub or switch would greatly simplify things if you don't require the isolation separate interfaces provides, but that idea was already suggested.
« Last Edit: November 02, 2008, 17:24:29 by fredg »

--
Google is your friend and Bob's your uncle.
« Reply #7 on: November 02, 2008, 19:15:03 »
bouyafa *
Posts: 11

Yes in effect, when you suggest to me to add a switch to simplify my network, i had not understood yet what each interface MUST be configured for differents subnets.
So now i understand better your proposition, and add a switch Smiley
But a little question persist, how a 192.168.1.x can see/ping a 192.168.2.x  ?  I must change the netmask perhaps ?

Thanks for all
« Reply #8 on: November 03, 2008, 19:56:08 »
Fred Grayson *****
Posts: 994

The default behavior on interfaces is to deny traffic. You have to have one or more rules in place to allow traffic. Therefore, for an interface to be usable, it must have at least one firewall rule. Try looking at the rule(s) in place for a LAN interface that works, then use that as an example to create rules for the other LAN interfaces. You may or may not be able to use a broad netmask with a single rule rather than multiple narrower rules.

As I am sure you have noticed by now, turning a firewall into a switch isn't an especially easy thing or a good idea.

--
Google is your friend and Bob's your uncle.
« Reply #9 on: November 05, 2008, 23:23:20 »
bouyafa *
Posts: 11

Yes I did. Big thanks for all.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines