Back to Help and Support
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

All packets dropped, Destination Net Unreachable pinging other Vodafone IP with same default gateway

cf996
4: Newbie

‎19-11-2022 01:51 PM - edited ‎24-11-2022 12:14 PM

My relative and I both have a Vodafone FTTP connection. Until around a month ago we could communicate directly with each other's static IP address.

 

It seems that something has changed and this is now no longer possible. When either IP pings the other, an ICMP "Destination Net Unreachable" packet is received from the default gateway. I notice that we both have the same default gateway (90.247.128.1) whereas previously we did not. I can communicate with either IP from other non Vodafone public IPs without issue, but I don't have access to another Vodafone public IP to try from. I believe that a change of default gateway has occurred and having both connections on the same default gateway is the issue.

 

Is there some kind of routing configuration issue on this gateway or other reason why this communication is no longer working?

0 Thanks
13 REPLIES 13

cf996
4: Newbie
In response to Ripshod

‎26-11-2022 01:07 PM

I wonder if this issue is confined to this gateway or whether it applies to all. Unfortunately it is difficult to co-ordinate, but if we could find two users on the same gateway, different to 90.247.128.1, and who are willing, we could find this out. I don't think this is an insignificant issue as there are plenty of p2p applications requiring direct connection to other users' IPs.

0 Thanks

broadband_user
4: Newbie
In response to cf996

‎26-11-2022 07:52 PM

Best way forward now would be to raise a complaint with VF, as they're throttling network traffic to zero between internet IP addresses on the same subnet, which is not in the contract. Vodafone IPs are the 'internet' as well... that's probably your best way forward with this, as opposed to just raising it as a technical problem.

Might also have to put the VF routers back at your address so they can have a look at what's going on. Just one less thing for them to consider, or they might blame your routers. Up to you though. It shouldn't matter.

 

0 Thanks

Jayach
16: Advanced member
16: Advanced member
In response to cf996

‎26-11-2022 10:56 PM - edited ‎26-11-2022 11:13 PM

@cf996 wrote:

I wonder if this issue is confined to this gateway or whether it applies to all. Unfortunately it is difficult to co-ordinate, but if we could find two users on the same gateway, 

My Gateway is 84.65.64.1 (Surrey Quays). I have switched on Allow Ping to WAN interface, so if anyone on the same gateway wants to try pinging me my address is eighty four. sixty seven.ninety two.eighteen.

It isn't a static address, but it hasn't changed in 63 days so it should still be there for a while.

 

@cf996 wrote:

I don't think this is an insignificant issue as there are plenty of p2p applications requiring direct connection to other users' IPs.

If by P2P applications you mean torrents, the likelihood of needing to connect to someone on the same gateway is remote. (And you would likely be using a VPN, so your Vodafone gateway wouldn't be important.)

0 Thanks

broadband_user
4: Newbie
In response to cf996

‎26-11-2022 12:42 PM

This sounds like a Vodafone (public) router/default gateway configuration oversight/error. It's makes no sense that VF would intentionally block IP traffic directly between hosts on the same subnet, but allow traffic between VF hosts on different subnets (handled by a different router / DG). I think VF are going to have to sort this problem out. Someone at VF is going to have to edit the DG router tables.

0 Thanks