Having written scripts which can be used to configure various aspects of the SAR7x5 (NAT setup, firewall and config backup/restore) I have just been re-evaluating them and have decided to bring them all together into one little "bundle" and have also added a brand new script. They are now all contained in one zip file, along with another script which brings them all together so that they can be launched from one single script. This makes it easier to keep them all updated and to issue updates when needed. Some people were also struggling to find the attachements buried in long threads, so this should also help alleviate this problem.
The new script that has been added is one to help you test your connection using BT's "whoosh" test. Hopefully, it should help people diagnose problems when they are struggling to connect to their ISP's. Details of how it works are contained in the readme file and there are also details of what the test is here.
The zip file containing the scripts is attached and, as with all of the original scripts, you still need Teraterm Pro to run them (get the Windows version here, it's free!). Just download and unzip the files to a directory of your choice.
Again, don't forget to read the readme file before you use any of the scripts as it contains important information on how to use Teraterm Pro to run them and also important information on what they can and cannot do.
Here's a brief summary :
1) Configure the router (using NAT) to allow a connection to your ISP and the internet.
2) Configure the router for the BT 'whoosh!' test. Ideal for diagnosing connection problems and to find out if your line has actually been activated yet.
3) Configure the firewall and add/delete portfilter rules.
4) Back up and restore your router's configuration.
5) View PPP event logs and log events to a file.
If you have any problems running the scripts or if they produce errors when run, please start a new thread with as many details as possible and I (and others, hopefully!) will endeavour to help.
Updates to the scripts will also be posted here.
Last edited by tobyjuggler; 6th May 2003 at 05:41 PM.
Let me be the first to thank you for your efforts in putting the scripts together. Your hard hork has saved a lot of people hours of headache/tears/hair pulling, and is greatly appreciated. Keep up the good work!!
Incredible! After a day of discussion with my ISP (who I have to say tried to be very helpful) and in desperation I came to the forum and tried your script. It was brilliant - thanks a lot.
As a frustrated techie, I was interested to see how the new configuration differed from that advised in the Solwise CD.
Apart from setting up a different WAN address to the one my ISP gave me (they did give me the one that is now in place but told me it was irrelevant), it seems that your configuration has also enabled DNS relay and created a blank IP route.
As I now need to update my configuration for port forwarding etc, I would like to understand my current configuration. Without giving away any trade secrets, can you point me in the right direction?
Originally posted by peterqc Apart from setting up a different WAN address to the one my ISP gave me (they did give me the one that is now in place but told me it was irrelevant)
The WAN IP address is, or at least should be, irrelevant as the router should be able to pick it from your ISP during log in, even if you have a static address.
it seems that your configuration has also enabled DNS relay and created a blank IP route.
DNS discovery and DNS relay are enabled by the script. No IP routes are created, apart from whatever is created by enabling NAT in the router.
As I now need to update my configuration for port forwarding etc, I would like to understand my current configuration. Without giving away any trade secrets, can you point me in the right direction?
The DHCP server is not enabled. I decided not to include it as, to set up the router. you need to give your PC a static address anyway (192.168.7.2) - it is only meant to be a basic setup - ie just enough to get you connected and browsing. The firewall is not enabled by the set up script, but there is another one there for doing that (At the moment it only does tcp and udp filters, but I may update it for other protocols in a future release).
I have tried writing a script for portforwarding, but it is quite complicated. I do intend to give it a go again in the future. The Solwise manual does explain portforwarding easily enough - you can either do it via the web interface (on http://192.168.7.1) or you can use the CLI. For example, to allow connection to a webserver on the LAN (on PC 192.168.7.3) from the outside world you would use :
nat add resvmap myserver interfacename ppp-0 192.168.7.3 tcp 80 (where myserver is a unique name you give to the rule).
If you are really interested in what commands the script actually issues to the router during set up they are :
system config restore factory
system config save
system restart
(Now wait 30 seconds and connect again)
pppoe clear transports
rfc1483 clear transports
pppoa add transport ppp-0 dialout pvc 1 r1483 0 38
pppoa set transport ppp-0 discoverdns primary enabled
pppoa set transport ppp-0 discoverdns secondary enabled
pppoa set transport ppp-0 givedns client enabled
pppoa set transport ppp-0 givedns relay enabled
pppoa set transport ppp-0 headers llc disabled
pppoa set transport ppp-0 username ******
pppoa set transport ppp-0 password ******
pppoa set transport ppp-0 welogin chap
pppoa set transport ppp-0 enabled
system config save
system restart
(Now wait 30 seconds and connect again)
ip add interface ppp-0 0.0.0.0 255.0.0.0
ip attach ppp-0 ppp-0
security enable
security add interface iplan internal
security add interface ppp-0 external
nat enable item0 ppp-0 internal
system config save
system restart
-------------------------------
Wait another 30 seconds or so and your router will reboot then attempt to connect to your ISP.
Replace ****** with the username and password supplied to you by your ISP
Thats great - thanks a lot. I was really interested in the instructions issued, and this has cleared up a lot of points.
On another point, it seems that the main reason why my attempt to configure the router following Solwise's instructions failed, and yours worked is that you enabled the dns client and relaying service whereas there was no mention of this in their 'basic setup' instructions.
Is mine just a unique case, or have other people had similar problems. In which case has anyone told Solwise?
Not sure about that, because I set mine up using Solwise's instructions in the first place. Got it wrong first time, got it right second time, but it was a slightly different interface back then - I do remember something about DNS in those instructions.
I haven't used the web config for my initial set up since writing the script - it's so much easier this way. I think many people have found this, but that's possibly because it requires less user input and you are therefore less likely to make a mistake along the way.
I've just started all over again and reconfigured the router using the manual. It worked without any problems and DNS client/relay were automatically enabled by default.
Have just added a new script to the bundle. There is now a script to view the PPP event logs and save the router output to a log file. See the readme.txt or readme.doc files for more details. If you already have the older bundle of scripts you can unzip this latest version to the same directory - the older files will be overwritten.
Last edited by tobyjuggler; 21st January 2003 at 09:27 PM.
My exchange was enabled last Friday and I'm currently waiting for my line to be activated. However tonight the DSL Link LED went from blinking to solid green despite my ISP telling me that my activation date would be on Sunday.
I tried to configure my SAR715 via the web interface so I could browse to www.bt.net/digitaldemo - with no success. I then tried the bttest script (very helpfull - thanks) and because the browser would not "see" the BT test site either there is a fault on the line or my line isn't activated yet.
I typed all this bobbins into the tera term and it suggests there isn't a fault, am I right?
--> adsl show perf
Downstream :
Noise Margin : 35.5 dB
Attenuation : 44.5 dB
Output Power : 17
Upstream :
Noise Margin : 13.0 dB
Attenuation : 24.0 dB
Output Power : 9
Yes, it could be that the authentication servers haven't been configured for your line yet at a guess. I don't know exactly how many things have to be done before you can get logged in either as yourself or the bt test account.
I'd just keep trying every day or so until the activation day! My Pipex account was switched on several days earlier than they told me
View Profile
View Forum Posts
Reply With Quote
.
Visit Homepage
