Upgrade Network Woes


#1

After upgrading my networking is hosed:

% ping 4.2.2.1
PING 4.2.2.1 (4.2.2.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host

% ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=85259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
ether 48:4d:7e:f9:c5:72
inet 130.101.185.252 netmask 0xffffff00 broadcast 130.101.185.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT )
status: active
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 0x2
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: lo

% about

General information

boot environment now (N) … 12.0-CURRENT-up-20180402_064139 NR 2018-04-02
after restart ® … 12.0-CURRENT-up-20180402_064139 NR 2018-04-02
boot loader …………………………………… BSD
type ……………………… BIOS
CPU ………………………………………………………… Intel® Core™ i7-6700 CPU @ 3.40GHz
number of cores ……………… 8
host ……………………………………………………… webteam3.uakron.edu
memory ………………………………………………… 8192 MB available, 6148 MB free
OS git branch ……………………………………………………………………………………… trueos-stable-18.03
OS git revision ………………………………………………………………………………… fa797a5a3
OS kernel build time ………………………………………………………… Mon 2018 Mar 26 00:24:47 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… STABLE
TrueOS version …………………………… TrueOS-Desktop-201803131015
uptime ………………………………………………… 1:05
user …………………………………………………… mjanosi

More (TrueOS Desktop):

desktop environment …… Lumina
sound card driver ………… pcm0: <Realtek ALC255 (Rear Analog Line-out)> (play) default
wireless driver ……………… 
X11 drivers ………………………… vesa_drv.so

#2

So it looks like your machine got an IPv4 address of 130.101.185.252, does that sound correct?
What does your routing table look like?
Is this setup as DHCP or STATIC network config?
What is the next hop from your machine? If you reboot into the previous boot environment, I’m assuming things work, so what IP and routing do you have in a working configuration?

Networking issues typically require a bit more information, specificially related to network topology to figure out.


#3

Yes, this machines IP is 130.101.185.252.

% netstat -r
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 130.101.185.1 UGS em0
localhost link#2 UH lo0
130.101.185.0/24 link#1 U em0
130.101.185.252 link#1 UHS lo0

Internet6:
Destination Gateway Flags Netif Expire
::/96 localhost UGRS lo0
localhost link#2 UH lo0
::ffff:0.0.0.0/96 localhost UGRS lo0
fe80::/10 localhost UGRS lo0
fe80::%lo0/64 link#2 U lo0
fe80::1%lo0 link#2 UHS lo0
ff02::/16 localhost UGRS lo0

The setup is STATIC.

The difference between the working version and the upgrade version is:

default 130.101.185.1 UGS em0

even though defaultrouter is set in both rc.conf and rc.conf.preUpgrade. So:
route add default 130.101.185.1 worked, but why isn’t it being set by rc.conf?

Oh, and, of course, thanks!!!


#4

It looks like both working and non working have

Can you ping that from 130.101.185.252?

Are you saying that defaultrouter is set correctly in rc.conf for both working and nonworking but the route table in nonworking does not have it added, but when you add it by hand everything works?


#5

Yes, that’s correct and, of course, I can ping that after manually adding the default route.


#6

Ok. I’m not in front of my machine right now, I have a similar STATIC ip with defaultrouter defined. Upgraded over the weekend and did not have any issues.
rc-status show any errors or any crashed services?
/etc/init.d has the init scripts, maybe a quick grep will tell you which one is actually doing the work of applying the defaultrouter.


#7

Only cups_browsed, but I did noticed Evolution also crashes with a Segmentation fault. I also get messages to Apply Updates, which I did, but I still have to manually add the default route, after reboot, and the messages continue to persist. So, I guess something is failing and I’m stuck in an infinite update loop.


#8

webteam3.cc.uakron.edu. 1800 IN A 130.101.185.252

Is this You, or is it not?


#9

nope, I’m 130.101.185.252


#10

Then, why do You have this in Your first posting?

% ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=85259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
ether 48:4d:7e:f9:c5:72
inet 130.101.185.252 netmask 0xffffff00 broadcast 130.101.185.255

#11

Because that’s correct. Your post asked if I was 130.101.185.25, then you edited it.


#12

Yes, I edited it, because final digit was not copied.

Do You know the difference between private and public addresses? Sorry, but I have to ask.


#13

Yes, it’s a University of Akron IP.


#14

Thanks for the data.


#15

defaultrouter in rc.config is of type STRING. Did You enclose it within DoubleQuotes?

And did You try this?

static_routes
(str) Set to the list of static routes that are to be added
at system boot time. If not set to NO'' then for each whitespace separated element in the value, a route_<element> variable is assumed to exist whose contents will later be passed to aroute add’’ operation. For example:

	 static_routes="ext mcast:gif0 gif0local:gif0"
	 route_ext="-net 10.0.0.0/24 -gateway 192.168.0.1"
	 route_mcast="-net 224.0.0.0/4 -iface gif0"
	 route_gif0local="-host	169.254.1.1 -iface lo0"

	 When an element is in the form	of name:ifname,	the route is
	 specific to the interface ifname.

#16

Yes, it’s enclosed with double quotes. The only difference between the two:

% diff /etc/rc.conf /etc/rc.conf.preUpgrade
20a21

kldload_i915kms=""

Where do I try your suggestion, at the loader prompt?


#17

It’s for rc.conf:

Source of suggestion:

https://www.freebsd.org/cgi/man.cgi?query=rc.conf&manpath=FreeBSD+11.1-RELEASE+and+Ports

or

https://www.freebsd.org/cgi/man.cgi?query=rc.conf&manpath=FreeBSD+12-current


#18

Nope, same thing. I have to manually run add net default after a
boot.


#19

How many Network Interface Cards does Your machine have?

Maybe, Your kernel has two or more routing tables, and You’re using the wrong default.

Else, let’s wait for forum member ‘mer’. Maybe, he has a new idea.


#20

Nope, just 1 card.