Date: Mon, 13 May 2019 20:44:06 -0700 From: "Kurt Buff - GSEC, GCIH" <kurt.buff@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: dhclient question Message-ID: <CADy1Ce6AkoP%2BQ=aK=J0KCRJbrXo0Ja1DAFZ9tomcXZ0W9qStng@mail.gmail.com> In-Reply-To: <CADy1Ce6Xj46hNMTJ%2B_VnnVHTg3iM_9WOsDUZyJ34A=sKqVViDw@mail.gmail.com> References: <CADy1Ce4i%2BvAFbxwHQdWHdjrK6WpuBnaEPuzgPAo1vvP4m3tabg@mail.gmail.com> <20190514043640.afe58701.freebsd@edvax.de> <CADy1Ce6Xj46hNMTJ%2B_VnnVHTg3iM_9WOsDUZyJ34A=sKqVViDw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh, and BTW, the default route doesn't change either - this is kind of screwy. I'd think that moving to a new subnet would refresh the IP address and the default gateway, at least. $ netstat -r Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.1.1 UGS em0 localhost link#2 UH lo0 172.31.255.0/24 link#1 U em0 172.31.255.60 link#1 UHS lo0 192.168.1.0/24 link#1 U em0 192.168.1.19 link#1 UHS lo0 On Mon, May 13, 2019 at 8:34 PM Kurt Buff - GSEC, GCIH <kurt.buff@gmail.com> wrote: > I completely forgot about that. > > Here's the output of ifconfig - the bolded line is the address from the > previous network, and the one after that is the address from the current > network > > Kurt: > > em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > > options=81009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWFILTER> > ether 00:0c:29:9c:f6:a1 > inet6 fe80::20c:29ff:fe9c:f6a1%em0 prefixlen 64 scopeid 0x1 > *inet 192.168.1.19 netmask 0xffffff00 broadcast 192.168.1.255* > inet 172.31.255.60 netmask 0xffffff00 broadcast 172.31.255.255 > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> > > > On Mon, May 13, 2019 at 7:36 PM Polytropon <freebsd@edvax.de> wrote: > >> On Mon, 13 May 2019 18:45:15 -0700, Kurt Buff - GSEC, GCIH wrote: >> > This seemed to work. However, ifconfig reveals something unexpected >> > [image: image.png] >> > >> > After I saw that, [...] >> >> This list strips binary attachments. You should either >> include the content of the image as text in the message >> body (best solution to preserve that information for >> future reference in the mailing list archives) or upload >> the image somewhere and provide a link. >> >> >> >> -- >> Polytropon >> Magdeburg, Germany >> Happy FreeBSD user since 4.0 >> Andra moi ennepe, Mousa, ... >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADy1Ce6AkoP%2BQ=aK=J0KCRJbrXo0Ja1DAFZ9tomcXZ0W9qStng>