Project

General

Profile

Bug #4015

lost default gateway configuration after reboot

Added by Allen Chan over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Josh Paetzel
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I have been using 9.2.0-RELEASE for weeks.
Everything has been running fine.
I rebooted my server last friday to test UPS worked correctly.
After reboot i have not used the jails tabs.
Now i encounter the error attached.

[root@freenas ~]# ifconfig -a
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO>
ether 00:25:90:4b:f9:c8
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether 00:25:90:4b:f9:c9
inet 10.10.3.108 netmask 0xffffff00 broadcast 10.10.3.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
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 0x6
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:d2:04:85:1b:00
nd6 options=1<PERFORMNUD>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 8 priority 128 path cost 2000
member: igb1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 3 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:5b:18:00:08:0a
inet6 fe80::5b:18ff:fe00:80a%epair0a prefixlen 64 scopeid 0x8
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

[root@freenas ~]# netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
10.10.3.0/24 link#3 U 0 229322494 igb1
10.10.3.108 link#3 UHS 0 169 lo0
127.0.0.1 link#6 UH 0 1508893 lo0

Internet6:
Destination Gateway Flags Netif Expire
::/96 ::1 UGRS lo0
::1 link#6 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::/10 ::1 UGRS lo0
fe80::%lo0/64 link#6 U lo0
fe80::1%lo0 link#6 UHS lo0
fe80::%epair0a/64 link#8 U epair0a
fe80::5b:18ff:fe00:80a%epair0a link#8 UHS lo0
ff01::%lo0/32 ::1 U lo0
ff01::%epair0a/32 fe80::5b:18ff:fe00:80a%epair0a U epair0a
ff02::/16 ::1 UGRS lo0
ff02::%lo0/32 ::1 U lo0
ff02::%epair0a/32 fe80::5b:18ff:fe00:80a%epair0a U epair0a

[root@freenas ~]# ping google.com
PING google.com (74.125.239.132): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
^C
--- google.com ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

It looks like after reboot the server lost the default gateway configuration even though it is set in the UI.

jails screen error.png (69.6 KB) jails screen error.png Allen Chan, 01/25/2014 03:14 AM
Network screen.png (143 KB) Network screen.png Allen Chan, 01/25/2014 03:16 AM
359
360

History

#1 Updated by Jordan Hubbard over 5 years ago

  • Category set to 20
  • Assignee set to Josh Paetzel
  • Target version set to 48

Haven't seen any other reports like this - a freebsd bug causing the loss of the default route after every reboot would result in a lot more reports than just this one. Something must be strange here. Any ideas of anything to try?

#2 Updated by Josh Paetzel over 5 years ago

  • Status changed from Unscreened to Screened

What is the default route set to in the GUI?

#3 Updated by Allen Chan over 5 years ago

10.10.3.100
i posted a screenshot that shows it.

#4 Updated by Josh Paetzel over 5 years ago

Is igb1 getting an ip statically or via dhcp?

Can you attach the output of dmesg -a after the system boots?

#5 Updated by Allen Chan over 5 years ago

I did this to get the default gateway reapplied.
I tried just clicking save on the network page to see if that would apply the default gateway. Did not work.
So i cleared the default gateway field. Clicked save. Re-entered 10.10.3.100 and clicked save.

Now the default gateway is showing up and the jails tab loads correctly

[root@freenas ~]# netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.10.3.100 UGS 0 4 igb1
10.10.3.0/24 link#3 U 0 363513200 igb1
10.10.3.108 link#3 UHS 0 202 lo0
127.0.0.1 link#6 UH 0 1852411 lo0

Internet6:
Destination Gateway Flags Netif Expire
::/96 ::1 UGRS lo0
::1 link#6 UH lo0
::ffff:0.0.0.0/96 ::1 UGRS lo0
fe80::/10 ::1 UGRS lo0
fe80::%lo0/64 link#6 U lo0
fe80::1%lo0 link#6 UHS lo0
fe80::%epair0a/64 link#8 U epair0a
fe80::5b:18ff:fe00:80a%epair0a link#8 UHS lo0
ff01::%lo0/32 ::1 U lo0
ff01::%epair0a/32 fe80::5b:18ff:fe00:80a%epair0a U epair0a
ff02::/16 ::1 UGRS lo0
ff02::%lo0/32 ::1 U lo0
ff02::%epair0a/32 fe80::5b:18ff:fe00:80a%epair0a U epair0a

#6 Updated by Josh Paetzel over 5 years ago

Does it survive a reboot?

#7 Updated by Allen Chan over 5 years ago

John, to answer your question, the interfaces pull dhcp.

I cannot reboot the server at this moment. But looking at the dmesg -a at this point i do see something interesting.

For some reason it believed the route was already in the table.

route: writing to routing socket: File exists
add net default: gateway 10.10.3.100 fib 0: route already in table
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1

System also started the jail properly with the default gateway

jail -c path=/mnt/DATASTORE/Jails/plexmediaserver_1 name=plexmediaserver_1 host.hostname=plexmediaserver_1 allow.raw_sockets=true pe
rsist vnet
Setting IP4 address: 10.10.3.50/24
igb1: link state changed to UP
arp: 10.10.3.50/24: Unknown host
add net default: gateway 10.10.3.100
jexec 1 arp -s 10.10.3.100 c0:c1:c0:45:65:8e
Starting jail with: /etc/rc
jexec 1 /usr/pbi/plexmediaserver-amd64/control start 10.10.3.50 12346
Mounting user-supplied file-systems

#8 Updated by Allen Chan over 5 years ago

I finally got a chance to reboot my server (9.2.1.3 upgrade).
The default gateway remained after the reboot so i guess this is a one time glitch. This ticket can be closed.
Thanks for your attention.

#9 Updated by Josh Paetzel over 5 years ago

  • Status changed from Screened to Resolved
  • Target version changed from 48 to 9.2.1.5-RELEASE

Also available in: Atom PDF