Cannot access my Draytek Vigor 120 DSL Modem
-
I'll have a look a the Draytek Web GUI, but I would like to get the NAT sorted out, I thought it would have been simple but something doesn't appear to be correct with my setup. My "old" Soekris is proving to be a temperamental little b'stard.
Thanks.
-
Double post!
-
Ok, reading back through this I think you have confused matters by trying to use port 8989. That was only relevant when you were using the port redirection method with 1.2.3.
You should leave the source and destination ports blank (any) in your NAT rule. You should then be able to connect to the modem with any service on any port e.g. ping, telnet, web (port 80) etc.Steve
-
I can now access my Draytek Vigor 120!!
I finally got my little Soekris box up and running and did a clean install of pfSense v2 and started testing, I then added an OPT1 interface and gave it the static IP address of 192.168.1.10 (same as before), this is the IP address that the DHCP server on the Draytek gives out.
I then added a NAT Outbound rule same as before, but this time with your suggestion of removing port 8989 on the LAN subnet and removing port 80 on the Draytek subnet.
I then entered the IP address 192.168.1.1 and (as if by magic) I can now access my modem!
Thanks to both yourselft and Wallabybob!
-
Excellent! ;D
What firmware version are you running?
I tried out many until I settled on this. Seems quite stable.Steve
-
I've just checked on the DrayTek website and we are both running on the most up-to-date firmware:
-
You would think that but I had some problems with mine. It wasn't running that firmware when I got it so I started looking into it and there are many to choose from. They are apparently optimised for different markets but it's hard to find any useful information.
See:```
ftp://ftp.draytek.com/Vigor120/Firmware/V3.2.4.4/Steve -
I've updated my modem about three times and I've always gone for the firmware with 332201, I can't remember where I read this, but I'm sure this specific to the UK region and as you can see from the dates, it was at the end of 2010 that I last updated my modem.
-
Mine started dropping the connection and occasionally locking up which was why I started trying other versions. I think I remember that there was a firmware optimised for bad line quality.
If it aint broke don't fix it! You look to have a good uptime on your modem too.Steve
-
I tried the extra interface method last night. Rather than messing with rules, I just added the vigor as the default gateway for that extra NIC and it worked fine.
