Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jra3086]

Typing those 3 prompts in separately and in order, I get these responses...

arp: writing to routing socket: Operation not permitted (this shows up twice)

PING 192.168.0.1 (192.168.0.1): 56 data bytes

--- 192.168.0.1 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

? (192.168.0.1) at 0:21:91:da:31:1 on en1 [ethernet]
? (192.168.0.255) at (incomplete) on en1 [ethernet]

[Fatman]

my apologies, I left something out that is a bit crucial to what we are trying to accomplish.  The reason the arp -d -a failed is because that requires super user privilege, which we will grant by performing the below steps instead.

sudo arp -d -a
(It should then ask for your password so that it can perform the arp -d -a with super user privilege [sudo stands for Super User DO])
ping -c 10 192.168.0.1
arp -a

[jra3086]

Okay, I just ran it again and got all this...

Last login: Sat Feb  7 17:11:24 on console
je-imac:~ jesseandersen$ sudo arp -d -a

WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:
192.168.0.1 (192.168.0.1) deleted
192.168.0.101 (192.168.0.101) deleted
192.168.0.255 (192.168.0.255) deleted
je-imac:~ jesseandersen$ ping -c 10 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=127 time=26.561 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=127 time=1.047 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=127 time=1.055 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=127 time=1.269 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=127 time=1.047 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=127 time=1.055 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=127 time=1.058 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=127 time=1.058 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=127 time=1.159 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=127 time=1.053 ms

--- 192.168.0.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.047/3.636/26.561/7.642 ms
je-imac:~ jesseandersen$ arp -a
? (192.168.0.1) at 0:21:91:da:31:1 on en1 [ethernet]

[Fatman]

And you did this while the wireless was failed?

Was the wireless still failed after this?

This makes very little sense, from all appearances during this failure we still have full communication with the router, I bet you can even view the routers config page during a failure given this.

[jra3086]

Yes, it was failed when I ran it, but it was running fine when I finished! Not sure if it just jumped back on, or if it was somehow linked to these prompts.

[Fatman]

If you would be so kind as to run through these steps a couple times and figure out if it fixes the problem, and at which point it is failed or fixed that would be a great boon.

[jra3086]

You bet! Given how much it's been going out, that shouldn't prove a problem to run a couple more tests this aft.

[Fatman]

you're da man!

[jra3086]

No, hopefully YOU'RE the man to help me fix things!

[jra3086]

Round 2... Once again, the connection kicked back on after running this.


Last login: Sat Feb  7 17:11:24 on console
je-imac:~ jesseandersen$ sudo arp -d -a
Password:
192.168.0.1 (192.168.0.1) deleted
192.168.0.255 (192.168.0.255) deleted
je-imac:~ jesseandersen$ ping -c 10 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=127 time=1.086 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=127 time=1.132 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=127 time=1.044 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=127 time=1.040 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=127 time=1.052 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=127 time=0.989 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=127 time=1.147 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=127 time=1.570 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=127 time=1.087 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=127 time=1.259 ms

--- 192.168.0.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.989/1.141/1.570/0.160 ms
je-imac:~ jesseandersen$ arp -a
? (192.168.0.1) at 0:21:91:da:31:1 on en1 [ethernet]
? (192.168.0.255) at ff:ff:ff:ff:ff:ff on en1 [ethernet]

[Fatman]

Can we isolate which step causes the return to normalcy?

[jra3086]

It's the 2nd step, when I ping it. I ran the first prompt, then checked it, and nothing changed, but the instant the 2nd prompt was running, it came back up online.

[Fatman]

that could be deceptive do me a favor and open up 2 terminals, in one run ping 192.168.0.1, this will continue on ad nauseam, to kill it when you are done testing you need to press Ctrl+C (or is it Command+C, its 0800 you will have to forgive me this one).  In the second terminal run the sudo arp -d -a, I expect you will see the pings start responding (and the net up) pretty quick when that command is run.

Do you have 2 Ethernet cards, I notice your Ethernet adapter is listed as en1 (I believe they start at en0, but again its 0800)?  If so could you disable the one not connected to this router and see if your connection still fails.

[jra3086]

I did this and the pings actually timed out before the sudo command kicked the connection back on, but right after I ran the sudo command, the connection did kick back on.

As far as 2 ethernet cards... I'm not sure why it says that. My iMac is a standard configuration so it should just be one, to my knowledge.

[Fatman]

I know this is a little hackish, but it sounds like the problem is that your ARP table is not updating or not referencing correctly, who knows.  The below are troubleshooting steps, not really a liveable long term solution.  That said the below may be of assistance.

If you do the below command it will temporarily add an ARP entry that should be appropriate for your router, this MAY resolve your issue, and will only last till a reboot or you clear the ARP table as I showed you how.

sudo arp -s 192.168.0.1 00:21:91:da:31:01 temp

If this works the permanent version of this hack would be to do this command:

sudo arp -s 192.168.0.1 00:21:91:da:31:01

This can be undone with:

sudo arp -d 192.168.0.1

If that works then the even more devious and hackish solution is to pick a PC (meaning Personal Computer not a Window machine) that will be on (at least for the duration of testing and do the below which will publish that address, which MAY resolve the issue for other computers on the network.

sudo arp -s 192.168.0.1 00:21:91:da:31:01 pub

This can be undone in the same method, with:

sudo arp -d 192.168.0.1

Please reply with how much of this if any resolves your issue.