Installed New nic, not accepting old ip

Status
Not open for further replies.

Quiltface

Dabbler
Joined
Mar 18, 2016
Messages
21
I am running freenas 9.10
I just put in a new intel dual port nic, i went into the console and deleted the old interface and setup the new one with the old IP. Now I can only ping the server with the old nic plugged into the switch...

I am not sure why this is happening am I missing some sort of non obvious step when setting up a new nic.

If i give the nic a new IP i can ping that fine but it seems as the system is caching that IP to that old nic.

Let me know what you need to help me troubleshoot this. I am currently trying to get net connectivity back on this and currently only have console.
 

Quiltface

Dabbler
Joined
Mar 18, 2016
Messages
21
Ok so bge0 was the old one which isnt showing up anymore so thats good... but i only need em0 and only .253.

currently the only way i can ping any of these IPs is if i have both ports connected to the switch... and I just got finished resetting all the nic settings in the console so I am not sure why these nics have these settings.

upload_2016-3-31_21-24-34.png


Actually in mid typing this... I unplugged the nic i didnt want to see if it would work and it dropped pings... i plugged it back in and i am still losing pings.

i can ping .125 and .126 but not .253 which is what my webui is.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Try using a new ip for the new NIC. Or you can reboot your router/switch. You have a IP conflict because you have 2 Mac addresses using the same ip in your ARP table.
 

Quiltface

Dabbler
Joined
Mar 18, 2016
Messages
21
yeah i thought about that... i can get new IPs configured but i cant get them to be accessible by the webui.

im going to reboot my switch again, shutoff my server and unplug all the cables... and try again
 

Quiltface

Dabbler
Joined
Mar 18, 2016
Messages
21
how can i get rid of the .125 and .126




upload_2016-3-31_22-2-5.png


upload_2016-3-31_22-2-28.png


Code:
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500                                                         
        options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>                                 
        ether 2c:41:38:87:22:90                                                                                                    
        nd6 options=9<PERFORMNUD,IFDISABLED>                                                                                       
        media: Ethernet autoselect (none)                                                                                          
        status: no carrier                                                                                                         
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500                                                          
        options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>                                 
        ether 00:15:17:bf:75:06                                                                                                    
        inet 192.168.0.253 netmask 0xffffff00 broadcast 192.168.0.255                                                              
        inet 192.168.0.125 netmask 0xffffff00 broadcast 192.168.0.255                                                              
        nd6 options=9<PERFORMNUD,IFDISABLED>                                                                                       
        media: Ethernet autoselect (1000baseT <full-duplex>)                                                                       
        status: active                                                                                                             
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500                                                          
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>                                           
        ether 00:15:17:bf:75:07                                                                                                    
        inet 192.168.0.126 netmask 0xffffff00 broadcast 192.168.0.255                                                              
        nd6 options=9<PERFORMNUD,IFDISABLED>                                                                                       
        media: Ethernet autoselect                                                                                                 
        status: no carrier                                                                                                         
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384                                                                  
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>                                                                      
        inet6 ::1 prefixlen 128                                                                                                    
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4                                                                                 
        inet 127.0.0.1 netmask 0xff000000                                                                                          
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>             


Code:
C:\>ping 192.168.0.253

Pinging 192.168.0.253 with 32 bytes of data:
Reply from 192.168.0.253: bytes=32 time<1ms TTL=64
Reply from 192.168.0.253: bytes=32 time<1ms TTL=64
Reply from 192.168.0.253: bytes=32 time<1ms TTL=64
Reply from 192.168.0.253: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.253:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.0.125

Pinging 192.168.0.125 with 32 bytes of data:
Reply from 192.168.0.125: bytes=32 time<1ms TTL=64
Reply from 192.168.0.125: bytes=32 time<1ms TTL=64
Reply from 192.168.0.125: bytes=32 time<1ms TTL=64
Reply from 192.168.0.125: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.125:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>

C:\>ping 192.168.0.126

Pinging 192.168.0.126 with 32 bytes of data:
Reply from 192.168.0.107: Destination host unreachable.
Reply from 192.168.0.107: Destination host unreachable.
Reply from 192.168.0.107: Destination host unreachable.
Reply from 192.168.0.107: Destination host unreachable.

Ping statistics for 192.168.0.126:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
 

Attachments

  • upload_2016-3-31_22-3-33.png
    upload_2016-3-31_22-3-33.png
    5.9 KB · Views: 199

Quiltface

Dabbler
Joined
Mar 18, 2016
Messages
21
I think I got it...

upload_2016-3-31_22-31-56.png



This is what I did... consolidated as much as i can.

  • Deleted interfaces
  • unplugged ethernet cables
  • i didnt have to do this because my arp cache was clear already but clear the arp cache on the freenas server
  • shut down freenas
  • rebooted switch (i have a dumb switch)
  • deleted any address leases in my DHCP server for the Freenas server
  • cleared arp cache on my dhcp server (or at least for anything pertaining to freenas)
  • cleared arp cache on my dns server (or at least for anything pertaining to freenas... doubt this is necessary but what the hell)
  • rebooted my firewall (doubt this is necessary either... my firewall is not doing my dhcp)
  • booted up my freenas
  • configured my NIC

Im going to do a few more test but i think this is it... arp can be a sob sometimes.
I would have issues where it was pinging just fine and then i plug in another nic and it wouldnt work anymore... then i would unplug the nic i just plugged in and it still wouldnt work.
Or it would be working and then i would reset em1 which wasnt plugged in or configured (it had that dhcp address i was trying to get rid of) and after i reset the nic em0 stopped responding to pings...


going to do a bit more testing to see if i come across any other nuances.
 
Last edited:

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Glad to see you got it fixed.
 
Status
Not open for further replies.
Top