Message from @Zuihou

Discord ID: 495655571865731076


2018-09-29 17:54:33 UTC  

yeah

2018-09-29 17:54:48 UTC  

Will not cause eth0 to drop

2018-09-29 17:54:50 UTC  

basically if your config is correct, then it seems like it doesnt matter

2018-09-29 17:54:59 UTC  

but your config might be incorrect

2018-09-29 17:55:12 UTC  

what router do you have?

2018-09-29 17:55:18 UTC  

It is a dhcp mode to pick up ip from the modem

2018-09-29 17:55:24 UTC  

@Grenade123 unifi usg

2018-09-29 17:55:52 UTC  

have you tried restarting it by chance?

2018-09-29 17:55:57 UTC  

Yes

2018-09-29 17:56:21 UTC  

Now get this, isp modem showed a restart on the same time as my eth0 goes down

2018-09-29 17:56:28 UTC  

tried resetting the dhcp?

2018-09-29 17:56:39 UTC  

>but random restart is not indicative of hardware failure

2018-09-29 17:56:55 UTC  

@Grenade123 you mean the modem dhcp server

2018-09-29 17:57:02 UTC  

It gotnpower cycled

2018-09-29 17:57:30 UTC  

Wan is having issie

2018-09-29 17:57:33 UTC  

Not lan

2018-09-29 17:57:36 UTC  

Different

2018-09-29 17:57:47 UTC  

Dhcp is to correct lan issues

2018-09-29 17:57:53 UTC  

But wan is handled by modem

2018-09-29 17:58:17 UTC  

Otherwise you will have modem acting as router and router being router, you will get 2 routers

2018-09-29 17:58:32 UTC  

It does look like a DHCP client issue involving eth0.

2018-09-29 17:58:49 UTC  

Not really

2018-09-29 17:59:20 UTC  

Their modem gives a private ip on startup, then gives a public ip on link establish with internet

2018-09-29 17:59:35 UTC  

"?Looks like the dhcp client under eth0 made zebra thinking the broadcast address wasn't right. If WAN/Internet access is fine then there isn't much to worry about. You can try renew dhcp for eth0 see if the message would occur again, also you can check "show interface ethernet eth0", "show ip route", and "show ip route forward" outputs see if anything doesn't look right"

2018-09-29 17:59:42 UTC  

It is still routing fine since internet worked for days on end

2018-09-29 17:59:43 UTC  

that was from the post i linked earlier

2018-09-29 18:00:29 UTC  

but on a different note, have you tried power cycling the modem?

2018-09-29 18:00:52 UTC  

and any other routers on the network

2018-09-29 18:04:31 UTC  

Yes

2018-09-29 18:04:51 UTC  

The error was after the power cycle, about 1 hr after

2018-09-29 18:06:59 UTC  

Where on earth is it getting '255.255.255.255/24 != 82.xx.xxx.xxx'? The IP settings on eth0 must be jacked up.

2018-09-29 18:18:26 UTC  

Dhcp from isp is stupid

2018-09-29 18:18:34 UTC  

It goes from private to public

2018-09-29 18:18:39 UTC  

I read that as ICP

2018-09-29 18:18:43 UTC  

I'm like

2018-09-29 18:18:48 UTC  

the fuck do juggalos have to do with this

2018-09-29 18:19:11 UTC  

DHCP is standard for ISP's.

2018-09-29 18:22:39 UTC  

Not when they go from private ip to public ip

2018-09-29 18:24:00 UTC  

That doesn't matter for the DHCP configuration of the public interface on the home router.

2018-09-29 18:24:46 UTC  

NAT lies above the physical interface configuration.