[ previous ] [ next ] [ threads ]
 
 From:  "Christopher M. Iarocci" <iarocci at eastendsc 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:  Sat, 16 Dec 2006 17:39:50 -0500
Mehran 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
>   
Sorry to double post, but I thought of one last thing.  You'll probably 
need to add a static route to the Netgear that says:

192.168.1.0/24 -> 192.168.0.133

Not sure how to do that in your Netgear.  You'll need to consult it's 
manual to figure that one out unless someone else here knows that 
particular router.  If you don't do this, it is likely your Netgear will 
not know where to pass the packets coming through it for the 
192.168.1.0/24 network.

Chris