Static IP address not being routed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I've had a terrible time getting multipel static IPs set up with my 2701HGV-C.For reference, here is my static IP info (I have 5 static IPs), as given by BT:
network address: 81.142.95.216
router/Hub address: 81.142.95.222
subnet mask: 255.255.255.248
Here's the procedure I've followed:
Settings -> Broadband -> Link Configuration
Under Public Ip Address:
Check Enable, set router address to 81.142.95.222, set subet mask to 255.255.255.248, check auto firewall open.
Settings -> LAN -> NAT & Address Allocation
I choose the device I want to give a static IP, set fireall to Disabled, set address assignment to static IP, and set WAN IP mapping to 81.142.95.217.
On the computer with a static IP, which is connected via an ethernet cable to the hub, I give it the static IP 81.142.95.217, set the default router to 81.142.95.222, and set the netmask to 255.255.255.248. I can ping the gateway (81.142.95.222), but any tracerouteI perform stops at the gateway.
This *was* working a few days ago, but every few days my internet connection would "get stuck," and when I tried to ping the gateway it would drop packets like crazy. Usually I could get things working again by rebooting the BT Hub several times, re-inputting some settings etc. Now the static IP stuff just doesn't work at all. I can still connect from other computers, both wired and wireless, via NAT and the 192.168 network.
Any ideas how to get static IPs working? I called tech support and was told the people who handle static IP problems would call me back. They haven't.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
The 2701GV-C is very clever, it is much clever than any human who may try to use t and knows what you should be doing unfortunately it can't well more like won't tell you.
It works very poorly with static IP's on the server, It seems to be designed to be used with DHCP.
You seem to have to specify a static local ip on the server (say 192.168.3.3) it seems to notice this and adds it to the list of configurable interfaces, you can then pick this and map it to an external address.
I was trying to configure it to pass the 2 static ip's to one NIC, it would let me then it would forget, very frustrating.
For what I was doing I found it easier to implement PPP on my server and let that do the connection to the static IP's, unfortuntely the 2701GV-C was clever enough to know I didn't want to do that really, eventually I had to use an old modem I had been using before I changed to BT.
If you opt for this solution you need to purchase your modem carefully as many like the 2701GV-C do not pass the PPPoE packets through, the Vigor 2900G has a pass through PPPoE option which is what is needed.
Having said all that my system seems to have stopped working today, and as my config is non standard talking to BT will be pointless.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
thats interesting i had nothing but problems last week, and still have, with static ip's
I have just brought a netgear DGN2200m to replace my netgear dg834 as i needed a failover for whn the adsl is down. The DGN2200M is very buggy and i have a couple of support tickets open with netgear at this moment and one is the problem with static ip's
For some reason if i set my static ip exactly the same way as i have in my DG834 then it will not connect to the internet. If i leave it as assigned by isp then i get a dynamic ip that is not anything like my group of statics but it connects to the internet fine. Now today i decided to have another play and go through everything. and strange enough i set static to my router ip and it has connected but i still have an ip that is not mine.
But reading this im wondering if there is something a miss with BT's ip assignment and not all a router problem.
I wish i could us dyndns but some things just need my static ip's. dyndns actually works well, as i turn off nat in the modem and use a fvs336g to creat vpn tunnels and use dydns for fqdn.
sorry i cant offer and help but would be interested if you guys find a solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Hello, it looks like http://81.142.95.217/ can now be accessed. Can you please give the steps taken to get the problems
resolved. We have a similar problem with 5 static ip on BT Business Infinty.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
BT infinity + 5 statics.
BT2701
We run our own VPN server.
PPPoE on infinity and it gets a dynamic Public IP.
There is config option to add your 5+ static and the network mask and which IP you want to use as the additional router IP from your statics.
eg 81.138.250.80 / 255.255.255.248 Network assigning 81.138.250.86 to the router to act as gateway for the network.
Problem is with the firewall and IP assignment.
You can only assign/map one Public Staic IP (WAN) per Private IP (LAN).
Assigning multiple Private IPs to one network card in windows wont work with the 2-wire.
Our server hosts files for the LAN and VPN/HTTP/SMTP/POP for the WAN.
eg1.
server 192.168.0.1
Just use NAT on the dynamic address.
Port forward PPTP to 192.168.0.1.
This works fine, but the problem is the dynamic address.
We have our own domains and dynamic IP is not an option.
eg2.
server 192.168.0.1
Assign choice 81.138.250.81~85.
Wouldnt VPN though this.
Wouldnt let me assign a Public static to this Private static.
So got a 2nd network card for the server.
Server now has 192.168.0.1 for LAN & 81.138.250.81~85 for WAN....[fictional adresses]
Now even this muti static setup didnt work.
Until I looked through the firewall logs and noticed protocol 47 (GRE) was being dropped.
Basically port forwarding does not work (GRE busted) unless you are using NAT with the dynamic IP.
Stupid thing wont let you build custom packets to pass tcp yes, udp yes, protocol no.
Only fix is to place 81.138.250.81~85 in the DMZ plus zone.
Now that not an issue with win2003 server as I can firewall the routing and remote access,
kill everything apart from tcp80 tcp25 tcp110 tcp1723 protocol47 inbound
