Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

FireBrick 2700 Configuration run-through: Difference between revisions

 
=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. For the purpose of this example, let's assume the P-660R is on 192.168.1.2 mask 255.255.255.0.
 
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="192.168.1.1/24"/>
</interface>
</syntaxhighlight>
 
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:
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.
<div style="text-align: left" dir="ltr" class="mw-geshi"><div class="xml source-xml"><pre class="de1"> <span class="sc3"><span class="re1">&lt;interface</span> <span class="re0">name</span>=<span class="st0">"WAN"</span> <span class="re0">port</span>=<span class="st0">"WAN1"</span><span class="re2">&gt;</span></span>
<span class="sc3"><span class="re1">&lt;subnet</span> <span class="re0">ip</span>=<span class="st0">"192.168.1.1/24"</span><span class="re2">/&gt;</span></span>
<span class="sc3"><span class="re1">&lt;/interface<span class="re2">&gt;</span></span></span></pre></div></div>
<br>'''Static routes'''
 
The previous config will put the FB on 192.168.1.1, and allow the FB to route IP packets between your LAN subnet and the 192.168.1 subnet. However, at this stage, you may find you are still unable to ping the modem on the WAN port. THis is because although packets from your 81.x.x.x address are correctly routed to the modem, the modem itself knows no route back to 81.x.x.x. It know nothing of the FB. SO we need to tell it by setting a static route.
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, hit the 'Apply' button, and that's it done.
 
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' ->&gt; '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, hit the 'Apply' button, and that's it done.
On the Vigour 120, you need to telnet in to the CLI to set the route.
The commands to set a route back to 81.x.x.0 via the FB at 192.168.1.1 are:
 
On the Vigour 120, you need to telnet in to the CLI to set the route. The commands to set a route back to 81.x.x.0 via the FB at 192.168.1.1 are:
>ip route status
 
&gt;ip route status<br>&gt;ip route add 81.x.x.0 255.255.255.192 192.168.1.1 static<br>&gt;ip route status
 
Once this is confirmed working, you should do a:
>ip route status
 
>&gt;sys commit
Once this is confirmed working, you should do a:
 
to save it to flash, otherwise it's lost on power-down.
>sys commit
 
The Draytek CLI reference may be found here: ftp://ftp.draytek.com/Document/Telnet_Commands_V1.11.zip
to save it to flash, otherwise it's lost on power-down.
 
The Draytek CLI reference may be found here:
ftp://ftp.draytek.com/Document/Telnet_Commands_V1.11.zip
 
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.
49

edits