FireBrick 2700 Configuration run-through: Difference between revisions

← Older edit Newer edit →

Content deleted Content added

Inline

@@ Line 364: / Line 364: @@
 =Other Things=
 ==Accessing the Modem==
-The modem, or ADSL router in bridge mode, will also have a LAN IP that you can use to get to it's config pages etc. eg, the ZyXEL P660-R will still have a LAN setting, with an IP set.
+The modem, or ADSL router in bridge mode, will also have a LAN IP that you can use to get to it's config pages etc. eg, the ZyXEL P660-R will still have a LAN setting, with an IP set.   For the purpose of this example, let's assume the P-660R is on 192.168.1.2 mask 255.255.255.0.
 In order to talk to the Modem from the LAN side of the FireBrick, a Subnet on the FireBrick needs to be made.
 This subnet would be on the WAN Interface, eg:
 <syntaxhighlight>
    <interface name="WAN" port="WAN1">
-      <subnet ip="198.51.100.2/24"/>
+      <subnet ip="192.168.1.1/24"/>
    </interface>
 </syntaxhighlight>
-And the assuming the Modem is on 198.51.100.1, you'll be able to access it from the LAN side of the FireBrick.
+This will put the FB on 192.168.1.1, and allow the FB to route IP packets from your LAN interface *to* the Modem on the WAN interface.   However, at this stage, you may find the modem does not have a *return* route to your LAN addresses, so no packets return.  You'll be unable to ping the modem yet.   We need to set a static route on the modem, pointing back to the FB.
+For example, on the ZyXel P-660R, you will have configured the IP and Netmask on the 'LAN' tab.   But there's no 'Gateway', so we must go to 'Advanced' -> 'Static Routes' tab, and create one.   Enter it as follows:  IP, Mask = base address of your internal LAN; eg: 81.xx.xx.0, 255.255.255.192.  The 'Gateway' address is pointing back at the FB, eg 192.168.1.1.   Check the box to Activate the route, and that's it done.
+Now, the assuming the Modem is on 192.168.1.2, you'll be able to access it from the LAN side of the FireBrick.