RE: Upgrading to 6.2-RELEASE from 6.2-STABLE



-----Original Message-----
From: illoai@xxxxxxxxx [mailto:illoai@xxxxxxxxx]
Sent: Friday, June 08, 2007 9:12 PM
To: Mark Stout
Cc: freebsd-questions@xxxxxxxxxxx
Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE


On 08/06/07, Mark Stout <mcs@xxxxxxx> wrote:
Hello,

I recently upgraded from 5.4-RELEASE to 6.2-STABLE. Now I'm
having problems
with the TCP stack. I suspect its because of code differences.
I may have
some older 5.4 code that was used during the build world process. For
example, here's a partial ifconfig -a output

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=8<VLAN_MTU>
inet 71.4.48.6 netmask 0xfffffe00 broadcast 71.4.49.255
inet 71.4.48.4 netmask 0xffffffff broadcast 71.4.48.4
inet 71.4.48.7 netmask 0xffffffff broadcast 71.4.48.7
inet 71.4.48.9 netmask 0xffffffff broadcast 71.4.48.9

What's interesting is I can ping 71.4.48.6 from the console.

But I get the following whenever I ping any other aliased IP
from the local
console. I can ping these from other machines.
[root 6]> ping 71.4.48.4
PING 71.4.48.4 (71.4.48.4): 56 data bytes
ping: sendto: Invalid argument
ping: sendto: Invalid argument


Looking up a domain using dig I get similar errors. It
actually returns the
info I want but I still get the errors.
[root 7]> dig www.google.com
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151:
internal_send: 71.4.48.2#53: Invalid argument
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1151:
internal_send: 71.4.48.3#53: Invalid argument

71.4.48.2 and 71.4.48.3 are my DNS.


So what I thought I'd do is move to 6.2-RELEASE. What I wanted to do is
install the source code from

ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/src/* and do a
build world and build kernel. I assume that's really all I
need to build a
new system. Are there any caveats to do an upgrade this way?

Iff you really do want to move back to 6.2-RELEASE,
I would advise building from the security branch, so
in your supfile make sure you have
tag=RELENG_6_2


I'd prefer to remain at 6.2-STABLE but I can't find where the problem is
with these IP errors. I'm figuring I've got a mixed code and that's the
root cause but I'm not sure.


Thank you,
Mark Stout
VPM Global Internet Services, Inc.
530-626-4218 x205 Office
530-626-7182 Fax
530-554-9295 VoIP
916-240-2850 Cell
www.vpm.com <http://www.vpm.com>

This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom they are addressed. If you are
not the intended recipient, you are hereby notified that any use or
dissemination of this communication is strictly prohibited, and asked to
notify us immediately, then delete this email. E-mail transmission cannot be
guaranteed to be secure or error-free and VPM Global Internet Services, Inc.
does not accept liability for any errors or omissions in the contents of
this message. Any views or opinions presented are solely those of the
author and do not necessarily represent those of VPM Global Internet
Services, Inc.

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Upgrading to 6.2-RELEASE from 6.2-STABLE
    ... inet 71.4.48.6 netmask 0xfffffe00 broadcast 71.4.49.255 ... What's interesting is I can ping 71.4.48.6 from the console. ... ping: sendto: Invalid argument ...
    (freebsd-questions)
  • Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
    ... inet 71.4.48.6 netmask 0xfffffe00 broadcast 71.4.49.255 ... What's interesting is I can ping 71.4.48.6 from the console. ... ping: sendto: Invalid argument ...
    (freebsd-questions)
  • Re: Parsing text for IP Addresses
    ... is an invalid IP but will be caught by that regex). ... I can ignore that IP address (there would be no need to ping ... set buffer $expect_out ... ping $ipaddr $port $status ...
    (comp.lang.tcl)
  • RE: Strange routing configuration problem
    ... >Given your netmask, both IP addresses of R are in the same subnet ... >The card in R which is on the same subnet as A should have an IP ... so I could ping R on both the interfaces but still cant ping A. ...
    (freebsd-net)
  • Re: Client Server Broadcast
    ... Ping macht kein 'Broadcast'. ... dann könnte zB. Active Directory domain ... Simple Service Discovery Protocol ...
    (microsoft.public.de.german.entwickler.dotnet.vb)