× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Orbi WiFi 7 RBE973
Reply

Re: GC752XP Floods Network With SSDP Packets When Configured With Static IP

Gedruspax
Star

GC752XP Floods Network With SSDP Packets When Configured With Static IP

I have 9 GC752XP switches in my network feeding network drops throughout the building.

 

When I reset one to the factory defaults it will come up and grab an IP address from my DHCP server.  I can then add it to my insight dashboard either via the web portal or the mobile app and it shows up as connected and reports the IP it has been given by the DHCP server correctly.

 

When I dump the diagnostic output and look at the config I see the following three interfaces:

 

dtl0 Link encap:Ethernet HWaddr 8C:3B:AD:6F:72:A4
inet addr:176.100.201.27 Bcast:176.100.255.255 Mask:255.255.0.0
inet6 addr: fe80::8e3b:adff:fe6f:72a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3507597 errors:0 dropped:0 overruns:0 frame:0
TX packets:286493 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1618259181 (1.5 GiB) TX bytes:43817718 (41.7 MiB)

 

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:178322 errors:0 dropped:0 overruns:0 frame:0
TX packets:178322 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39234075 (37.4 MiB) TX bytes:39234075 (37.4 MiB)

 

rfc5549if Link encap:Ethernet HWaddr 12:6F:FC:DD:44:49
inet addr:250.0.0.1 Bcast:250.0.0.3 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2703 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:447603 (437.1 KiB)

 

So thats all well and good - first one is my network, 2nd is loopback, third is network discovery interface no issues there.

However I obviously want to set the IP statically as these are access and core layer switches in the building.  As soon as I try to change the IP to the static address within either the insight dashboard or through the mobile app the following things happen:

 

First the switch reassigns a zero-config/bogus ip to the dtl0 link and creates a 4th "rt_v1" interface with my actual IP as shown below.

 

The interface config changes to the following:

dtl0 Link encap:Ethernet HWaddr 8C:3B:AD:6F:72:A4
inet addr:169.254.0.239 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::8e3b:adff:fe6f:72a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3548835 errors:0 dropped:0 overruns:0 frame:0
TX packets:287470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1638824236 (1.5 GiB) TX bytes:44216465 (42.1 MiB)

 

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:182934 errors:0 dropped:0 overruns:0 frame:0
TX packets:182934 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:40445521 (38.5 MiB) TX bytes:40445521 (38.5 MiB)

 

rfc5549if Link encap:Ethernet HWaddr 12:6F:FC:DD:44:49
inet addr:250.0.0.1 Bcast:250.0.0.3 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2767 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:457573 (446.8 KiB)

 

rt_v1 Link encap:Ethernet HWaddr 8C:3B:AD:6F:72:A7

inet addr:176.100.1.148 Bcast:176.100.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82042 errors:0 dropped:0 overruns:0 frame:0
TX packets:44295 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:24093582 (22.9 MiB) TX bytes:18220108 (17.3 MiB)

 

2nd - in the actual switch logs I see the following start happening - TONS AND TONS of bad arp requests to 0.0.0.0 IPs.  And I mean TONS to the point that it starts bogging the switch down.

 

<12>1 2022-04-13T12:16:12.287-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 87015 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 7e:82:d1:67:55:9f.
<12>1 2022-04-13T12:14:27.848-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86872 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 00:10:40:d2:c8:87.
<12>1 2022-04-13T12:13:08.520-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86738 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5e:b9:d9:7c:14:2d.
<12>1 2022-04-13T12:13:00.818-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86737 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 00:10:40:58:99:e5.
<12>1 2022-04-13T12:12:49.173-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86733 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5e:b9:d9:7c:14:2d.
<12>1 2022-04-13T12:12:36.966-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86678 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 26:8e:d3:e2:75:22.
<12>1 2022-04-13T12:11:48.783-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86615 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is de:cd:b6:72:ee:f8.
<12>1 2022-04-13T12:11:28.935-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86593 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5a:83:45:9b:06:0f.
<12>1 2022-04-13T12:11:27.035-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86592 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is de:cd:b6:72:ee:f8.
<12>1 2022-04-13T12:11:10.532-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86534 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is de:cd:b6:72:ee:f8.
<12>1 2022-04-13T12:11:00.497-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86515 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5a:83:45:9b:06:0f.
<12>1 2022-04-13T12:10:51.157-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86511 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is de:cd:b6:72:ee:f8.
<12>1 2022-04-13T12:10:47.472-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86508 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5a:83:45:9b:06:0f.
<12>1 2022-04-13T12:10:33.946-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86488 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is de:cd:b6:72:ee:f8.
<12>1 2022-04-13T12:10:27.840-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86468 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is a6:4a:9f:e2:a9:86.
<12>1 2022-04-13T12:10:23.723-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86467 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5a:83:45:9b:06:0f.
<12>1 2022-04-13T12:10:03.194-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86453 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 00:10:40:58:7e:88.
<12>1 2022-04-13T12:09:55.586-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86427 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 7e:0b:0d:7f:ca:63.
<12>1 2022-04-13T12:09:40.710-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86395 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 7e:0b:0d:7f:ca:63.
<12>1 2022-04-13T12:09:40.265-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86394 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is a6:4a:9f:e2:a9:86.
<12>1 2022-04-13T12:09:13.338-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86376 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is a6:4a:9f:e2:a9:86.
<12>1 2022-04-13T12:08:58.490-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86310 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 5a:83:45:9b:06:0f.
<12>1 2022-04-13T12:08:56.293-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86309 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 26:8e:d3:e2:75:22.
<12>1 2022-04-13T12:08:47.745-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86288 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 32:1f:a2:10:d9:e6.
<12>1 2022-04-13T12:08:09.030-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86211 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 7e:0b:0d:7f:ca:63.
<12>1 2022-04-13T12:08:02.609-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86198 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 06:60:41:3a:82:8e.
<12>1 2022-04-13T12:07:27.263-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86146 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 06:60:41:3a:82:8e.
<12>1 2022-04-13T12:07:09.462-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86101 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 26:8e:d3:e2:75:22.
<12>1 2022-04-13T12:07:04.618-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86076 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 32:1f:a2:10:d9:e6.
<12>1 2022-04-13T12:06:50.647-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86050 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 26:8e:d3:e2:75:22.
<12>1 2022-04-13T12:06:30.021-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86029 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 06:60:41:3a:82:8e.
<12>1 2022-04-13T12:06:28.759-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86028 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:06:26.399-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 86026 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:06:17.192-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85998 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 7e:0b:0d:7f:ca:63.
<12>1 2022-04-13T12:06:13.272-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85989 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 26:8e:d3:e2:75:22.
<12>1 2022-04-13T12:05:47.238-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85967 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:05:29.924-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85930 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:05:20.053-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85924 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:05:09.667-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85921 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:04:52.608-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85905 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 7e:82:d1:67:55:9f.
<12>1 2022-04-13T12:04:51.641-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85900 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 1e:1a:36:cb:d2:a2.
<12>1 2022-04-13T12:04:45.369-4:00Z WHOLE-SWITCH-001-1 ARP ipMapForwarding - :ipmap_arp_api.c(1149) 85879 %% Received ARP Request on interface vlan 1 with bad target IP address 0.0.0.0. Sender IP is 0.0.0.0, sender MAC is 26:8e:d3:e2:75:22.

 

3rd - I run up wireshark on a workstation on the local network and the switch is absolutely HAMMERING the network interface with SSDP discovery packets originating from the main MAC address of the switch and from the IP 169.254.0.239.  I mean to the point where the svchost -netsvcs process in windows just keeps growing and growing and growing in memory usage until i literally have to restart the machine because it runs out of memory.

 

I've already seen the posts that were similar to this issue with these switches.  I've removed them from insight - reset them to factory defaults, added them back, didn't re-import the old config etc etc.  All the bad stuff only starts happening when I try to set the static IP.

 

What is the deal here?  Is this just a bug in the operating system for these switches that will never get fixed?  Am I just going to have to let them run on DHCP addressing or have my network flooded with garbage traffic?  Is there a way to correct this stuff in the CLI for the switch because obviously when you have it in insight mode you have little to no configuration options in the actual GUI of the switch you have to do it all through insight.

 

Other Notes:

All switches are on latest available firmware revision

Switches do reply to ping and web GUI opens up on the new static IP after I change it.

 

Model: GC752XP|Insight Managed 52-Port Gigabit PoE+ Ethernet Smart Cloud Switch with 2 SFP and 2 SFP+ 10G Fiber Ports
Message 1 of 3
DaneA
NETGEAR Employee Retired

Re: GC752XP Floods Network With SSDP Packets When Configured With Static IP

@Gedruspax,

 

Since you have already run Wireshark and you got a packet capture as well as you have a copy of the logs you have posted here, I suggest you to open a support ticket with NETGEAR Support here at anytime in order for the logs and packet capture to be analyzed.  

 

 

Regards,

 

DaneA

NETGEAR Community Team 

Message 2 of 3
Gedruspax
Star

Re: GC752XP Floods Network With SSDP Packets When Configured With Static IP

Well my problem is that its been more than 90 days so apparently they want to charge me for support but I'm not going to pay for help trying to fix something that is clearly a defect on the part of NetGear having to do with this specific model switch as they are all exhibiting the exact same behavior.

 

What do you suggest I do at this point?

 

 

Message 3 of 3
Discussion stats
  • 2 replies
  • 1502 views
  • 1 kudo
  • 2 in conversation
Announcements