[ previous ] [ next ] [ threads ]
 
 From:  krt <kkrrtt at gmail dot com>
 To:  Mehran <error at exemail dot com dot au>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Bridge problem
 Date:  Fri, 15 Dec 2006 07:21:45 -0800
Since your m0n0wall can ping 192.168.0.1, I can assume that the wifi
link is working.


Do the hosts on the 192.168.0.0/24 network know how to get to the
192.168.1.0/24 network?

If not:

1) The Ideal (network) route is for each host to route 192.168.1.0/24
to 192.168.0.33 (the 192.168.0.0/24 interface of the m0n0wall
firewall)

2) The Netgear should, at a minimum, route 192.168.1.0/24 to
192.168.0.33.  If any hosts on the 192.168.0.0/24 network utilize the
Netgear for packet forwarding of 192.168.1.0/24 packets, then there is
an assymetric routing issue, where the packet from the 192.168.0.0/24
host will go to the netgear, to the m0n0wall and to the
192.168.1.0/24.  The reply packet will go from the 192.168.1.0/24 host
to the m0n0wall and back to the 192.168.0.0/24 client, without ever
traversing the Netgear on the return.  This shouldn't pose an issue
with the Netgear, but it could for other stateful firewall products
out there, and at a minimum does suck away some performance.



On 12/14/06, Mehran <error at exemail dot com dot au> wrote:
> Hi,
>
>
>
> I'm trying to create a bridge network
>
>
>
> Netgear DSL/router IP 192.168.0.1 /24 (DHCP) Wireless
>
>
>
> Through m0n0Wall (bridge) Wireless
>
>
>
> Connect to PC (Wired) IP 192.168.1.  /24
>
>
>
> ==========
>
>
>
> This is how I configured m0n0Wall
>
>
>
> 1.      Click on Interfaces -> WAN. Change Type to static. In Static IP
> Configuration set the IP to an unused IP in the Home AP's range
> (192.168.0.133). Under Wireless Configuration, set Mode to BSS, SSID to the
> Home AP's SSID (netgear).
> 2.      Uncheck "Block private networks" at the bottom of that page. Click
> Save.
> 3.      In Interfaces -> LAN, change the IP to reflect the local subnet
> desired. E.g. 192.168.1.1. In Services -> DHCP, update the allocated range
> to match your LAN IP (e.g. 192.168.1.100 - 192.168.1.199). Click Save.
> 4.      Go to Diagnostics -> Reboot System.
>
>
>
>
>
> Problem is that I can not ping the router 192.168.0.1 or access the web on
> the PC.  Through HyperTerminal (Monowall box) I can both ping 192.168.0.1
> and google.com.
>
>
>
> PC has an IP of 192.168.1.100 no problem pinging monowall box.
>
>
>
>
>
> Can you please let me know if I'm doing something wrong..
>
>
>
>
>
> Cheers,
>
>
>
> Mehran
>
>
>
>
>
>
>
>
>