Eth0: Link is down

What does

ip addr

return?

1: lo: <loopback,up,lower_up> mtu 65536 qdisc noqueue state unknow
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/0 scope host lo
inet6 :: 1/128 scope host
valid_lft forever preferred_lft forever

2: eth0: <broadcast,multicast> mtu 1500 qdisc noop state down qlen 1000
link/ether 00:13:21:d5:ae:e5 brd ff:ff:ff:ff:ff:ff

3: eth1 <broadcast, multicast, up, lower_up> mtu 1500 qdisc pf ifo_fast state unknow qlen 1000
link/ether 00:10:b5:82:09:ca brd ff:ff:ff:ff:ff:ff
inet 192.168.1.117/24 brd 192.168.1.255 scope global eth1
inet6 fe80::210::b5ff:fe82:9ca/64 scope link
valid_lft forever preferred_lft forever

in addition. I can ping google from the server with success.

Eth0 is an hp hardware and disconnected
Eth1 a accton , presumably the add in card but it’s state is inknown, check your cableing and see if you have any traffic on it

tcpdump -i eth1

If nothing try another nic

whole bunch of stuff.
please don’t make me type it all out. :slight_smile:
request who-has 192.168.1.1 tell 192.168.1.106
arp, request
arp, reply
google-public-dns-a.google.com.domain >
soooo much stuff…

Make sure your gateway is using eth1

route

where? how? Please! Thank you. :slight_smile:

netstat -rn

192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

All looks good, Now

iptables -L
traceroute 8.8.8.8
ping www.yahoo.com

iptables give fail2ban stuff
chain forward , chain output, chain fail2ban-sip much other…

traceroute succeeds with 15 hops at google-public-dns

ping yahoo also succeeds.

However, I can still not ping the machine, no softphones connect to it and inbound calls ring three times then get busy signal

Also. I can not ping other computers on the same network.

If you are using Windows from cmd do

tracert 192.168.1.106

Post what you get.

Microsoft Windows [Version 10.0.14393]
© 2016 Microsoft Corporation. All rights reserved.

C:\Users\John>tracert 192.168.1.106

Tracing route to DESKTOP-7BLJ1PT [192.168.1.106]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms DESKTOP-7BLJ1PT [192.168.1.106]

Trace complete.

C:\Users\John>

192.168.1.106 is another computer on my network
how did you know that?

192.168.1.117 is the pbx machine. Here’s the result

C:\Users\John>tracert 192.168.1.117

Tracing route to 192.168.1.117 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * ^C
C:\Users\John>

I just changed the ifg-eth1 file. I changed from static to dhcp and removed the IPADDR line. it drew ip 192.168.1.107 on reboot and I was able to ping the machine. I also got GUI. I’ve just replaced previous settings and waiting on reboot now. Fingers crossed!

edit
that did not work. trying change to static ip of 107
fingers crossed!

Ok! So I have set the new static IP and everything expect for inbound calls is working. I can access GUI, soft phones are connecting, outbound calling works…

Inbound calls ring three times then go to busy signal.

All help is appreciated. I need to be awake in 6 hours to start answering phone calls…

Thank You,
John

Somehow a reboot from GUI miraculously has this system working! I’ll have to give it some time to see if the original failure is a thing of the past, but for now - it’s working.

well about an hour and still no issues. we’ll see what happens after sleeping for a few hours… Oh please God help this machine.

Thank you all for all of your help through this very difficult time.

Best Regards,
John

Nope! It was working at 8:30 no problems. Now I called inbound at 11am and again, rings three times then I get busy signal. Again. An outbound call has inbound working again.

When this is happening I still have access via GUI and can still ping the server. I’m guessing that it has nothing to do with the network card. There must be another problem. Maybe something getting hung up in asterisk itself. Any ideas?

Thank You,
John

The kernel message appears again?