This won't be an issue if you're running 1.2.3-release, as the block
RFC1918 option is only on the WAN interface.
Adam Thompson wrote:
(Going from memory here...)
Check the "Block RFC1918 addresses" checkbox on the Interface configuration
pages. It should be set on WAN but not OPT1 or LAN.
-
(Going from memory here...)
Check the "Block RFC1918 addresses" checkbox on the Interface configuration
pages. It should be set on WAN but not OPT1 or LAN.
-Adam Thompson
Sent from my BlackBerry device on the Rogers Wireless Network
-
On Sun, Jun 13, 2010 at 8:52 PM, Josh wrote:
> Here's my setup:
> WAN - dhcp via cable modem
> LAN - to switch with gigabit wired connections 192.168.1.x
> OPT1 - to linksys WAP 192.168.2.x
>
> Any devices on subnet 2 cannot access subnet 1, and vice versa, even though
> I have rules which allow i
Here's my setup:
WAN - dhcp via cable modem
LAN - to switch with gigabit wired connections 192.168.1.x
OPT1 - to linksys WAP 192.168.2.x
Any devices on subnet 2 cannot access subnet 1, and vice versa, even
though I have rules which allow it. The problem is that I have a print
server on subnet 1
