Re: Fn key events in Devd
On Mon, Feb 15, 2010 at 3:42 PM, Anselm Strauss wrote: > Hi, > > is there a way to see all events going through devd? cat /var/run/devd.pipe should work for what you need too see from devd. See the documentation for more details: man 8 devd > I have loaded the acpi_asus module, but the default devd rules in > /etc/devd/asus.conf don't seem to match for my Fn keys. How can I find out > what Fn key produces which event in devd? Good Luck. --_Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Source of closed port RST responses
On Sun, Dec 20, 2009 at 2:37 PM, DAve wrote: > I am routinely seeing these entries in one of my servers logs. > > Limiting closed port RST response from 373 to 200 packets/sec > > The server sits behind a PIX firewall, so I am suspicious of what is > trying to connect to a closed port. I don't see in any other logs what > port is being hit, or what IP is causing these log entries. > > Any way to tell what the source IP of these is? > > Try using tcpdump. You can redirect the decoded output to a log file as well. Make sure to replace "em0" in my example with the appropriate interface name. If the server is very busy, try just running it for a short period of time to make sure that it does not interrupt operations, then leave it running for whatever time period you want to monitor if all goes well. tcpdump -np -i em0 'tcp[13] & 4 != 0' The 'tcp[13] & 4 !=0' will cause the filter to only capture packets with the tcp flag RST set. man tcpdump or google for more examples of filters. Good Luck. ---Dave Horn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis driver: invalid argument (freebsd 8.0)
On Mon, Dec 7, 2009 at 12:28 AM, Anh K. Huỳnh wrote:
>
> Hi,
>
> On Sun, 6 Dec 2009 22:05:33 -0500
> Glen Barber wrote:
>
> > Hi
> >
> > On Sun, Dec 6, 20309 at 9:17 PM, Anh K. Huỳnh
> > wrote:
> > > Hi all,
> > >
> > > I compiled `bcmwl5` module by `ndisgen` then loaded that module
> > > successfully, but I get the `invalid argument` error:
> > >
> > > $ ifconfig ndis0 ssid TOM-and-JERRY
> > > ifconfig: SIOCS80211: Invalid argument
> > >
> > > What's wrong to my ndis driver? I read /usr/src/UPDATING and
> > > wireless section in the Handbook but found nothing special. So I
> > > post here for your helps.
> > >
> >
> > 1.) Are your kernel and userland in sync?
> >
> > 2.) What is the output of 'uname -a'? If 8.X, read the 20080420
> > entry in src/UPDATING.
> >
>
> I am using 8.0-RELEASE (upgraded from 7.2-RELEASE). I've read the 20080420
> entry and configured my card successfully. (I read that section before asking
> in list but I confused.)
>
If you have your /usr/src/ and kernel in sync (when you generated your
ndis module), then try something like:
ifconfig wlan0 create wlandev ndis0
ifconfig wlan0 ssid TOM-and-JERRY
via rc.conf:
wlans_ndis0="wlan0"
ifconfig_wlan0="ssid TOM-and-JERRY"
>From wlan(4) man page:
Drivers provide 802.11 functionality through wlan interfaces that are
created at runtime using interface cloning. This is done with the
ifconfig(8) create command or using the wlans_IFX variable in rc.conf(5).
Some drivers support the creation of multiple wlan interfaces that share
the same underlying device; this is the way by which ``multi-bss sup-
port'' is provided but it can also be used to create WDS links and other
interesting applications.
If you use WPA wireless security and DHCP on your wireless network,
you should also look at wpa_supplicant(8) and wpa_supplicant.conf(5)
and use something like:
wlans_ndis0="wlan0"
ifconfig_wlan0="WPA DHCP"
and setup your /etc/wpa_supplicant.conf file as required with
something like (entries vary based upon exact setup of your wireless
network. See wpa_supplicant.conf man page):
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="TOM-and-JERRY"
key_mgmt=WPA-PSK
psk="very secret passphrase"
}
and of course make sure that the generated ndis module is loaded (via
kldload or via /boot/loader.conf) before attempting to clone the
interface with "ifconfig wlan0 create wlandev ndis0" See kldstat(8)
man page and utility if you are unsure if your generated ndis kernel
module is loaded.
Good Luck.
--Dave Horn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: device hint -> disable firewire or sbp driver
> And if I'm reading the SVN commit right, it went to -STABLE (aka > RELENG_8) but not head (aka "."). It still won't fix all of FreeBSD 7 > install mediums, right? or is that "to come", maybe in 7.3? > > > Also, if I'm reading the commit right, 8.0-RELEASE is going to have > sbp(4) enabled in GENERIC too. Can someone make sure I'm reading that > right? > Just so that this is crystal clear: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/amd64/conf/GENERIC As of this moment, device sbp is commented out of the GENERIC kernel configuration for RELENG_8_0 branch *and* tagged with the RELENG_8_0_0_RELEASE tag, so the release build will have sbp disabled in the default GENERIC kernel configuration. (In other words, you should not have boot hangs by default due to firewire in 8.0 release) As far is 7.x is concerned, the current RELENG_7 branch (as of this moment) still has device sbp enabled. As far as 7.3 or future MFC to RELENG_7 of a fix or workaround, that remains to be seen, but the best thing to do is to make certain that the PR has all the necessary information provided, and to occasionally test with the latest -current (9.0) source and provide any debugging information if asked. 9.0 (aka -current) specifically left device sbp enabled so that people can continue to test and fix this bug (gives better exposure to the code). Make sense ? Good Luck. --_Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: device hint -> disable firewire or sbp driver
On Sat, Nov 21, 2009 at 2:15 PM, Tim Judd wrote: > On 11/21/09, Chris Whitehouse wrote: >> Tim Judd wrote: >>> Any way via tunables, environment, sysctl or device hints that one can >>> disable firewire on the install medium of recent (7.2 and newer) >>> Install CD/DVDs? >>> >>> more than one person is having problems with kernel panics on startup >>> due to firewire, and I can't google my way out of this one. >>> >>> >>> >>> Any advice from the pros? >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscr...@freebsd.org" >>> >> Tim, >> >> I've got one of the affected motherboards if this is the problem you mean: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=136327 >> >> The things that have worked for me are disabling firewire in the BIOS >> and using a GENERIC kernel or building a kernel with device sbp disabled >> and having firewire enabled in the BIOS. > > See though, the guys coming to FreeBSD from $another-OS gets a panic > from the install medium, which isn't speaking very well of our > quality. > > I got caught with this because the guy I was helping online had an > amd64-capable system, to which I don't. I can't build a install CD or > kernel to help him. I have a PCI firewire card that runs sbp, but the > livecd doesn't panic when i was booting from it. > > > I tried all sorts of disabling hints, tried to go upstream (see it's > dependencies and disable it's dependencies) and it still gave me a sbp > when the system finished booting. > > > Thought about asking him to run the memstick and disabling it from > there, but he still can't get past it booting to tweak anything. He > didn't have an option to disable firewire in the BIOS, and there was > no bios update from Sony for his Vaio. > > > I got stuck, and it started to wear thin that we have such a major > panic on install CDs. My mentality is to offer disk, cd and network > support in the kernel on the install CD/DVDs, but the generic kernel > that's installed has everything. > > > If others would like to offer suggestions, I'm still open for them. > > >> >> hint.sbp.0.disabled="1" in /boot/device.hints with GENERIC kernel - >> still get a panic >> >> sbp_load="YES" in /boot/loader.conf with sbp disabled in the kernel - >> get panic. >> >> It seems ok to kldload sbp after the system is up, ie the machine >> doesn't panic, but I don't have anything firewire to test with. >> >> Would it be an option to have sbp disabled by default in the install >> CD's? Those without the problem can put sbp_load in loader.conf, those >> with the problem will have to kldload it later but at least they will be >> able to install. As per svn and cvs: r199112 | kensmith | 2009-11-09 16:39:42 -0500 (Mon, 09 Nov 2009) | 11 lines Changed paths: M /stable/8/sys/amd64/conf/GENERIC M /stable/8/sys/i386/conf/GENERIC M /stable/8/sys/ia64/conf/GENERIC M /stable/8/sys/powerpc/conf/GENERIC M /stable/8/sys/sparc64/conf/GENERIC Comment out the sbp(4) entry for GENERIC config files that contain it. There are known issues with this driver that are beyond what can be fixed for 8.0-RELEASE and the bugs can cause boot failure on some systems. It's not clear if it impacts all systems and there is interest in getting the problem fixed so for now just comment it out instead of remove it. Commit straight to stable/8, this is an 8.0-RELEASE issue. Head was left alone so work on it can continue there. Reviewed by:Primary misc. architecture maintainers (marcel, marius) Looks like sbp(4) is disabled on the 8.0 branch already. --Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: DHCP client questions
On Sun, Sep 20, 2009 at 3:19 PM, stan wrote: > We have been bought out, and the new powers that be, are changing things. > They have decreed that there shall be no static entries in their DNS > servers. They are using $MS DHCP/DNS servers. I have a corporate supported > Win XP laptop, which I can plug in at various places in the network. It > gets different IP addresses, based upon where it physically is, but always > comes up with the same name. The question is whether by the "same name" you are referring to a dns lookup, a wins lookup, or a nbns broadcast query, or all of the above ;) > > I have several machines (such as a mailserver) which _MUST_ have fixed > names. I have played around with /etc/dhcllient.conf, but not managed to > get this working. I can get IP addresses, and various things such as > default routers, and DNS servers, but I have not managed to get the > suggested name put in their DNS. try running: tcpdump -r filename.pcap -vvv port bootpc in order to get a nice decode of your dhcp session. This will contain by the client discover/request/ack, and the server offer packets. > > I have captured packet traces with wireshark from the laptop, and from the > FreebSD client, and I am putting these up at http://beachcave.net/pdumps. > > I would really appreciate it if someone more familiar with DHCP that I > could take a look at theses. Your windows capture clearly shows a dhcp option 12 with the short name, and dhcp option 81 with FQDN Hostname Option 12, length 10: "CHSLSBROWN" FQDN Option 81, length 31: "CHSLSBROWN.kapstonepaper.com" Vendor-Class Option 60, length 8: "MSFT 5.0" Parameter-Request Option 55, length 11: Subnet-Mask, Domain-Name, Default-Gateway, Domain-Name-Server Netbios-Name-Server, Netbios-Node, Netbios-Scope, Router-Discovery Static-Route, Classless-Static-Route-Microsoft, Vendor-Option END Option 255, length 0 Your freebsd captures show dhcp option 12 with the FQDN. You need to try using option 12 and option 81 just like in windows land. You may even need to put in the Vendor-Class and/or others to duplicate the windows request, but try one item at a time. Try adding these to your dhclient.conf as needed. Take the time to look at the man page for dhclient.conf, and dhcp-options, and also take a look at the full defined option numbers here: http://www.iana.org/assignments/bootp-dhcp-parameters/ Good Luck. --Dave H ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Possible bug with IPv6 ICMPv6 handling
On Fri, Aug 21, 2009 at 1:55 AM, Doug Hardie wrote: > I have found what to me seems like a bug with ICMPv6 handling in IPv6. > However, before submitting a PR I wanted to check to be sure that its not a > misunderstanding on my part. > > The network setup. A host (A) connected to a router (B) connected to > another host (C) on a separate network. When all are up and running, A can > ping6 to C and gets a response. If you power off C and then do the ping > again, tpcdump on A shows an ICMPv6 destination unreachable datagram > received from B. However ping6 does not report that back to the user. A > ktrace of ping6 shows that it does not receive the ICMPv6 response. Its my > understanding that it should and the ping6 code seems to imply that also. Is > this a bug? > ___ What version of FreeBSD are you using ? Did you try the -v parameter to ping6 to display non-echo responses ? (man ping6) In a similar test I ran, I was able to get the icmp6 host unreachable message from ping6 -v on my FreeBSD 7.2 box. (I pinged a non-existent address/machine off an upstream router) uname -a FreeBSD dhorn-bsd 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 dh...@dhorn-bsd:~> ping6 -v 2001:470:7:584::3 PING6(56=40+8+8 bytes) 2001:470:8:584:20e:cff:: --> 2001:470:7:584::3 64 bytes from 2001:470:7:584::1: Destination Host Unreachable Vr TC Flow Plen Nxt Hlim 6 00 0 0010 3a 3e 2001:470:8:584:20e:cff::->2001:470:7:584::3 ICMP6: type = 128, code = 0 The other thing to potentially look at would be firewall rules, but that is unlikely if you can see the icmp6 response in tcpdump. Good Luck. --Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FYI, portsnap problems
On Mon, Jan 5, 2009 at 6:39 PM, Colin Percival wrote: > Hi all, > > For the benefit of those of you who are noticing problems with portsnap > right > now: The release of FreeBSD 7.1 has resulted in a very large amount of > traffic > to update1.freebsd.org, which is hosted by the same box as > portsnap-master... > so the portsnap mirrors are having some trouble syncing right now. If you > find > that portsnap doesn't work, please be patient -- once the flood of people > upgrading systems to 7.1-RELEASE has subsided things should get back to > normal. > > (Before people ask: update2.freebsd.org is going to exist soon. No, I'm not > looking for more mirrors right now.) Both freebsd-update and portsnap seem to be very fast for me at the moment. It looks like we have update2 in the dns rotation (at least when I queried): ;; QUESTION SECTION: ;_http._tcp.update.freebsd.org. IN SRV ;; ANSWER SECTION: _http._tcp.update.freebsd.org. 1707 IN SRV 1 25 80 update2.FreeBSD.org. _http._tcp.update.freebsd.org. 1707 IN SRV 1 30 80 update4.FreeBSD.org. _http._tcp.update.freebsd.org. 1707 IN SRV 1 10 80 update1.FreeBSD.org. _http._tcp.update.freebsd.org. 1707 IN SRV 1 10 80 update3.FreeBSD.org. Keep up the good work. Non quia difficilia sunt non audemus, sed quia non audemus, difficilia sunt. > > -- > Colin Percival > Security Officer, FreeBSD | freebsd.org | The power to serve > Founder / author, Tarsnap | tarsnap.com | Online backups for the truly > paranoid > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Kernel messages redirection
On Wed, Jan 7, 2009 at 10:52 AM, chris.scott wrote: > > hi > > Does anyone know howto redirect/stop kernel messages from displaying on > ttyv0? Look at conscontrol(8) as one option. ( There may be other ways that work better for your case, but I have used conscontrol on my 7.0-RELEASE machine before with success ) You can use conscontrol(8) to either mute, or redirect kernel messages to another virtual console. Good Luck. ---Dave Horn > > eg when you plug in a usb disk you get a load of messages to the 1st screen > console > > I am writing a custom installer and its a pain as every time I label and > geom provider it spams a load of stuff and messes up my nice display. This > is nothing to do with syslog as I have already turned off logging to > /dev/console, ive tried a few curious looking sysctl varibles but not found > anything that works yet. > > > k > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD update warns about 7.0 end of life
On Wed, Dec 24, 2008 at 9:18 PM, Tait wrote: >> > When running freebsd-update on FreeBSD 7.0, I noticed this message: >> > >> > WARNING: FreeBSD 7.0-RELEASE is approaching its End-of-Life date. >> >> Key concept: "RELEASE". >> >> Robert Huff > > I'm not trying to be dense, but what is that supposed to mean? > > I see this on http://www.freebsd.org/releases/7.0R/announce.html: > "The FreeBSD Security Team currently plans to support FreeBSD 7.0 until > February 28th, 2009." > > As far as I can tell, 7.1 hasn't even undergone RC2 build yet, much yet > the actual -RELEASE build. > > So what am I supposed to do about this warning and the impending cessation > of security support? Will the Security Team actually support 7.0R longer > than originally expected? If so, can freebsd-update be made to understand > that and stop issuing worrisome warnings? I have only ever personally seen the 7.0-RELEASE EoL warning when running an non updated kernel. I can not speak for the security team support horizon, but 7.1 RC is working very well on my test machine, so I personally will be updating my production box to 7.1-RELEASE shortly after the bits are frozen solid. What is the output of: uname -a Are you running -p7 already or not ? If not, then run: freebsd-update fetch install And do not forget to reboot your system to actually use the latest kernel after install succeeds. On my 7.0-RELEASE machine (that is already updated to -p7) I do not see EoL warnings. YMMV. Good Luck. --_Dave Non quia difficilia sunt non audemus, sed quia non audemus, difficilia sunt. > If the Security Team will stop > supporting 7.0R, what _will_ they be supporting come Feb? Assuming 7.1R > makes it out the door soon, will I really only have seven or so weeks > to upgrade? The Security Team is apparently supporting 6.4R well into 2010; > should I downgrade to keep receiving security updates? > > Thanks, > Tait > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: smbfs 2 GB file size limit
On Thu, Nov 20, 2008 at 7:07 AM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
> At 12:50 PM 11/18/2008, David Horn wrote:
>
> On Tue, Nov 18, 2008 at 7:06 AM, Derek Ragona
> <[EMAIL PROTECTED]> wrote:
>> At 12:23 AM 11/18/2008, David Horn wrote:
>>
>> On Mon, Nov 17, 2008 at 8:36 PM, Derek Ragona
>> <[EMAIL PROTECTED]> wrote:
>>> I have FreeBSD 7.0 Release and if I mount_smbfs a network NTFS share I
>>> have
>>> a 2 GB size limit on files. I checked the handbook and list archives but
>>> have not found a solution.
>>
>> I just ran a quick test, and was not able to reproduce this issue with
>> the mount_smbfs from FreeBSD 7.0. I tried against a Windows 2003
>> Server SP2, Windows XP SP3, and Samba 3.0 {on FreeBSD 7} with a 3.5GB
>> file.
>>
>> Was your issue with reading from or writing to a SMB share ?
>>
>> It was writing to a smb share.
>>
>>
>> What is the server software and OS version ?
>> (if Microsoft Windows, please include Service Pack number as well, as
>> it might make a difference)
>>
>> Windows 2003 server 32bit.
>>
>> How much disk space is left on your server volume ?
>>
>> Over a terabyte free
>>
>> Are there disk quotas enabled on the server ?
>>
>> None
>>
>> What error message are you getting from your FreeBSD client (if any) ?
>>
>> No error message, it just stopped writing at 1 Gb. I was doing this using
>> scp.
>
> Whoa, hopefully you just made a few typos here, or we are going down
> the wrong path of investigation.
>
> Did you really mean to say scp or cp ?
> scp(1) - secure copy (remote file copy program)
> cp(1)- copy files
>
> If you really meant scp, then the problem is not mount_smbfs, but
> instead likely a buggy scp client or server (which does not use smb
> for transport, but ssh)
>
> What is the exact byte count that your write stops at ? You
> originally stated 2GB, then 1GB.
>
>>
>> Can you check the smb server logs and see if you are getting any error
>> messages there ?
>>
>> Well I'm just mounting the volume to FreeBSD from the Windows server so
>> not
>> sure I'll find much in the logs besides the system log, but I will look.
>>
>> You may want to get a Wireshark trace and see if you can capture the
>> SMB error message/error code.
>>
>> I have heard of people running into similar problems when running
>> against older server software (NT 4.0/old samba) when the SMB session
>> did not negotiate large file/large write support (a function of the
>> SMB server capabilities session negotiation)
>>
>> I saw posts to that effect and that you needed samba 3.x to support large
>> files sizes, and the lfs option. But the mount_smbfs doesn't offer any
>> large file option.
>>
>
> Only bother with this next bit if you are morbidly curious as to how
> things work rather than just want to solve your problem, as it gets
> into the nitty gritty details of smb:
>
> mount_smbfs will allow for lfs (CAP_LARGE_FILE) automatically by
> specifying it's dialect capabilities in the smb negotiation.
>
> If you umount your smb share, then start a tcpdump you can capture the
> smb negotiation "Capabilities" bitmask to see if CAP_LARGE_FILE is
> being negotiated - the server specifies this capability. The client
> just sends the dialects of smb supported.For example:
>
> tcpdump -vvv -s 1500 -i em0 host server.example.com | grep Capabilities
>
> { where em0 is the network interface in use on FreeBSD and
> server.example.com is the hostname/ip address of your smb server }
>
> Then do a mount of the smb share (while tcpdump is running) and you
> should capture the Capabilities negotiated.
>
> For example:
>
> Capabilities=0x1F3FD
>
> If you decode the bitmask by using this reference :
> http://msdn.microsoft.com/en-us/library/aa302230.aspx {hint: only
> look at the last four bytes of the Capabilities line (e.g. F3FD in my
> example)} Or if you have kernel source installed, you can look in
> /usr/src/sys/netsmb/smb.h for the details.
>
>- Capabilities: 0x0001F3FD
> RawMode:(...1) Supports
> SMB_COM_READ_RAW and SMB_COM_WRITE_RAW (CAP_RAW_MODE)
> MpxMode:(..0.) No
> Support for SMB_COM_READ_MPX or SMB_COM_WRITE_MPX (CAP_MPX_MODE)
> Unicode:(.1..) Supports
> Unicode Strings (CAP_UNICODE)
> LargeFiles: (..
Re: smbfs 2 GB file size limit
On Wed, Nov 19, 2008 at 7:37 AM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
> At 12:50 PM 11/18/2008, David Horn wrote:
>
> On Tue, Nov 18, 2008 at 7:06 AM, Derek Ragona
> <[EMAIL PROTECTED]> wrote:
>> At 12:23 AM 11/18/2008, David Horn wrote:
>>
>> On Mon, Nov 17, 2008 at 8:36 PM, Derek Ragona
>> <[EMAIL PROTECTED]> wrote:
>>> I have FreeBSD 7.0 Release and if I mount_smbfs a network NTFS share I
>>> have
>>> a 2 GB size limit on files. I checked the handbook and list archives but
>>> have not found a solution.
>>
>> I just ran a quick test, and was not able to reproduce this issue with
>> the mount_smbfs from FreeBSD 7.0. I tried against a Windows 2003
>> Server SP2, Windows XP SP3, and Samba 3.0 {on FreeBSD 7} with a 3.5GB
>> file.
>>
>> Was your issue with reading from or writing to a SMB share ?
>>
>> It was writing to a smb share.
>>
>>
>> What is the server software and OS version ?
>> (if Microsoft Windows, please include Service Pack number as well, as
>> it might make a difference)
>>
>> Windows 2003 server 32bit.
>>
>> How much disk space is left on your server volume ?
>>
>> Over a terabyte free
>>
>> Are there disk quotas enabled on the server ?
>>
>> None
>>
>> What error message are you getting from your FreeBSD client (if any) ?
>>
>> No error message, it just stopped writing at 1 Gb. I was doing this using
>> scp.
>
> Whoa, hopefully you just made a few typos here, or we are going down
> the wrong path of investigation.
>
> Did you really mean to say scp or cp ?
> scp(1) - secure copy (remote file copy program)
> cp(1)- copy files
>
> If you really meant scp, then the problem is not mount_smbfs, but
> instead likely a buggy scp client or server (which does not use smb
> for transport, but ssh)
>
> What is the exact byte count that your write stops at ? You
> originally stated 2GB, then 1GB.
>
> This problem occurs under the following scenario:
>
> I have a windows share mounted on a FreeBSD 7.0 release (i386) using
> mount_smbfs.
>
> I was trying to scp from another server on the LAN to this share a 30GB
> file. The scp only copied 2 GB of that 30 GB file. This was using the scp
> on FreeBSD 7.0.
>
> I will try another scp application to determine if it is the scp, or
> mount_smbfs.
You may want to just do single variable tests to determine for certain
if you are having a problem with scp or with smb.
- First test:cp >2GB file directly from the FreeBSD local disk
file system to a mounted smbfs file system
- Second test: scp >2GB file from remote (other server) to FreeBSD local disk
Once you figure out which one is the problem, you can try changing
variables within that scope.
For example, if the issue seems to be scp, try using sftp (both use
ssh transport). You could also try updating ssh on both machines. If
you are running OpenSSH prior to 4.4 on any machine, there was a known
bug with scp and large files that only affects some platforms. (ssh -v
will show your version)
See ftp://ftp.ca.openbsd.org/pub/OpenBSD/OpenSSH/portable/ChangeLog
under 20060318
If the problem seems to be smbfs, then try a smbclient test.
That's about all I can think of at the moment.
Good Luck.
--_Dave
>
> I know the server I was coping from via SCP is not an issue. I was able to
> transfer that 30 GB file from that source server to another *nix server on
> the LAN.
>
>
>
>>
>> Can you check the smb server logs and see if you are getting any error
>> messages there ?
>>
>> Well I'm just mounting the volume to FreeBSD from the Windows server so
>> not
>> sure I'll find much in the logs besides the system log, but I will look.
>>
>> You may want to get a Wireshark trace and see if you can capture the
>> SMB error message/error code.
>>
>> I have heard of people running into similar problems when running
>> against older server software (NT 4.0/old samba) when the SMB session
>> did not negotiate large file/large write support (a function of the
>> SMB server capabilities session negotiation)
>>
>> I saw posts to that effect and that you needed samba 3.x to support large
>> files sizes, and the lfs option. But the mount_smbfs doesn't offer any
>> large file option.
>>
>
> Only bother with this next bit if you are morbidly curious as to how
> things work rather than just want to solve your problem, as it gets
> into the nitty gritty details of smb:
>
> mount_smbfs will allow for lfs (CAP_LARGE_FILE) automatically by
> s
Re: smbfs 2 GB file size limit
On Tue, Nov 18, 2008 at 7:06 AM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
> At 12:23 AM 11/18/2008, David Horn wrote:
>
> On Mon, Nov 17, 2008 at 8:36 PM, Derek Ragona
> <[EMAIL PROTECTED]> wrote:
>> I have FreeBSD 7.0 Release and if I mount_smbfs a network NTFS share I
>> have
>> a 2 GB size limit on files. I checked the handbook and list archives but
>> have not found a solution.
>
> I just ran a quick test, and was not able to reproduce this issue with
> the mount_smbfs from FreeBSD 7.0. I tried against a Windows 2003
> Server SP2, Windows XP SP3, and Samba 3.0 {on FreeBSD 7} with a 3.5GB
> file.
>
> Was your issue with reading from or writing to a SMB share ?
>
> It was writing to a smb share.
>
>
> What is the server software and OS version ?
> (if Microsoft Windows, please include Service Pack number as well, as
> it might make a difference)
>
> Windows 2003 server 32bit.
>
> How much disk space is left on your server volume ?
>
> Over a terabyte free
>
> Are there disk quotas enabled on the server ?
>
> None
>
> What error message are you getting from your FreeBSD client (if any) ?
>
> No error message, it just stopped writing at 1 Gb. I was doing this using
> scp.
Whoa, hopefully you just made a few typos here, or we are going down
the wrong path of investigation.
Did you really mean to say scp or cp ?
scp(1) - secure copy (remote file copy program)
cp(1)- copy files
If you really meant scp, then the problem is not mount_smbfs, but
instead likely a buggy scp client or server (which does not use smb
for transport, but ssh)
What is the exact byte count that your write stops at ? You
originally stated 2GB, then 1GB.
>
> Can you check the smb server logs and see if you are getting any error
> messages there ?
>
> Well I'm just mounting the volume to FreeBSD from the Windows server so not
> sure I'll find much in the logs besides the system log, but I will look.
>
> You may want to get a Wireshark trace and see if you can capture the
> SMB error message/error code.
>
> I have heard of people running into similar problems when running
> against older server software (NT 4.0/old samba) when the SMB session
> did not negotiate large file/large write support (a function of the
> SMB server capabilities session negotiation)
>
> I saw posts to that effect and that you needed samba 3.x to support large
> files sizes, and the lfs option. But the mount_smbfs doesn't offer any
> large file option.
>
Only bother with this next bit if you are morbidly curious as to how
things work rather than just want to solve your problem, as it gets
into the nitty gritty details of smb:
mount_smbfs will allow for lfs (CAP_LARGE_FILE) automatically by
specifying it's dialect capabilities in the smb negotiation.
If you umount your smb share, then start a tcpdump you can capture the
smb negotiation "Capabilities" bitmask to see if CAP_LARGE_FILE is
being negotiated - the server specifies this capability. The client
just sends the dialects of smb supported.For example:
tcpdump -vvv -s 1500 -i em0 host server.example.com | grep Capabilities
{ where em0 is the network interface in use on FreeBSD and
server.example.com is the hostname/ip address of your smb server }
Then do a mount of the smb share (while tcpdump is running) and you
should capture the Capabilities negotiated.
For example:
Capabilities=0x1F3FD
If you decode the bitmask by using this reference :
http://msdn.microsoft.com/en-us/library/aa302230.aspx {hint: only
look at the last four bytes of the Capabilities line (e.g. F3FD in my
example)} Or if you have kernel source installed, you can look in
/usr/src/sys/netsmb/smb.h for the details.
- Capabilities: 0x0001F3FD
RawMode:(...1) Supports
SMB_COM_READ_RAW and SMB_COM_WRITE_RAW (CAP_RAW_MODE)
MpxMode:(..0.) No
Support for SMB_COM_READ_MPX or SMB_COM_WRITE_MPX (CAP_MPX_MODE)
Unicode:(.1..) Supports
Unicode Strings (CAP_UNICODE)
LargeFiles: (1...) Supports
large files with 64-bit offsets (CAP_LARGE_FILES)
NTSMBs: (...1) Supports
SMB NTLM 0.12 dialect commands (implies CAP_NT_FIND) (CAP_NT_SMBS)
RPCRemoteAPIs: (..1.) Supports
remote API requests using RPC over named pipe connections
(CAP_RPC_REMOTE_APIS)
NTStatus: (.1..) Can
respond with 32-bit NT status codes in Status (CAP_NT_STATUS)
LevelIIOplocks: (1...) Supports
Level II oplocks ( CAP_LEVEL_II_OPLOCKS)
LockAndRead:
Re: smbfs 2 GB file size limit
On Mon, Nov 17, 2008 at 8:36 PM, Derek Ragona
<[EMAIL PROTECTED]> wrote:
> I have FreeBSD 7.0 Release and if I mount_smbfs a network NTFS share I have
> a 2 GB size limit on files. I checked the handbook and list archives but
> have not found a solution.
I just ran a quick test, and was not able to reproduce this issue with
the mount_smbfs from FreeBSD 7.0. I tried against a Windows 2003
Server SP2, Windows XP SP3, and Samba 3.0 {on FreeBSD 7} with a 3.5GB
file.
Was your issue with reading from or writing to a SMB share ?
What is the server software and OS version ?
(if Microsoft Windows, please include Service Pack number as well, as
it might make a difference)
How much disk space is left on your server volume ?
Are there disk quotas enabled on the server ?
What error message are you getting from your FreeBSD client (if any) ?
Can you check the smb server logs and see if you are getting any error
messages there ?
You may want to get a Wireshark trace and see if you can capture the
SMB error message/error code.
I have heard of people running into similar problems when running
against older server software (NT 4.0/old samba) when the SMB session
did not negotiate large file/large write support (a function of the
SMB server capabilities session negotiation)
> Supposedly there is an smbmount as part of the
> standard samba, but that doesn't seem to install from any of the samba
> ports.
smbmount is not included in the FreeBSD port of samba, as it is Linux
kernel specific. mount_smbfs(8) is the correct userland app.
You could always try the samba smbclient(1) to access SMB shares using
an FTP-like environment.
>
> Any help would be appreciated.
Sorry I do not have a good solution for you. Perhaps someone else
will give you better advice.
Good Luck!
-_Dave Horn
>
>
>-Derek
>derek at computinginnovations.com
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: host -6 failure
On Mon, Nov 10, 2008 at 10:31 AM, mdh <[EMAIL PROTECTED]> wrote: > --- On Sun, 11/9/08, David Horn <[EMAIL PROTECTED]> wrote: >> From: David Horn <[EMAIL PROTECTED]> >> Subject: Re: host -6 failure >> To: [EMAIL PROTECTED] >> Cc: freebsd-questions@freebsd.org >> Date: Sunday, November 9, 2008, 8:34 PM >> On Sun, Nov 9, 2008 at 3:13 AM, mdh >> <[EMAIL PROTECTED]> wrote: >> > --- On Sat, 11/8/08, David Horn >> <[EMAIL PROTECTED]> wrote: >> >> From: David Horn <[EMAIL PROTECTED]> >> >> Subject: Re: host -6 failure >> >> To: [EMAIL PROTECTED] >> >> Cc: freebsd-questions@freebsd.org >> >> Date: Saturday, November 8, 2008, 8:10 PM >> >> On Sat, Nov 8, 2008 at 7:55 PM, mdh >> >> <[EMAIL PROTECTED]> wrote: >> >> > --- On Sat, 11/8/08, David Horn >> >> <[EMAIL PROTECTED]> wrote: >> >> >> From: David Horn >> <[EMAIL PROTECTED]> >> >> >> Subject: Re: host -6 failure >> >> >> To: [EMAIL PROTECTED] >> >> >> Cc: freebsd-questions@freebsd.org >> >> >> Date: Saturday, November 8, 2008, 7:25 PM >> >> >> On Fri, Nov 7, 2008 at 2:18 PM, mdh >> >> >> <[EMAIL PROTECTED]> wrote: >> >> >> > Howdy folks, >> >> >> > I'm having a little trouble >> understanding >> >> a >> >> >> problem that the `host` command in >> RELENG_7_0 >> >> (very recent) >> >> >> is having. >> >> >> The '-6' on the command line for >> host(1) >> >> forces an >> >> >> IPv6 only >> >> >> connection to your nameserver, not >> necessarily a >> >> >> "" query for the >> >> >> hostname in question. In this case, your >> >> nameservers >> >> >> listed in the >> >> >> warnings are IPv4 nameservers that >> host(1) is >> >> attempting to >> >> >> connect to >> >> >> using an ipv4 mapped ipv6 address (which >> by >> >> default is >> >> >> disabled in the >> >> >> kernel) In other words, don't use >> host -6 for >> >> this >> >> >> scenario. >> >> > >> >> > Yet as I pointed out, the second nameserver >> in my >> >> resolv.conf is ::1 - so shouldn't it work with >> that? >> >> It's clearly trying to contact the first and >> third >> >> nameservers listed. If the behavior I'm >> experiencing is >> >> the proper behavior, then let me pose this >> question: when >> >> would anyone conceivably want to use the -6 >> option, and why >> >> does it exist? My intent was to force a query to >> hit the >> >> nameserver on ::1 rather than 127.0.0.1. >> >> >> > >> >> >> > domain mydomain >> >> >> > search mydomain >> >> >> > nameserver 127.0.0.1 >> >> >> > nameserver ::1 >> >> >> > nameserver IP.IP.IP.8 >> >> >> > >> >> >> > The DNS server running on localhost >> is >> >> authoritative >> >> >> for mydomain. I can ping it via >> localhost using >> >> both v4 and >> >> >> v6, and I can also ping the external v4 >> and v6 >> >> addresses >> >> >> just fine remotely. >> >> >> > >> >> >> > As I said, I'm new to IPv6, but >> this >> >> behavior >> >> >> seems to be counterintuitive. Am I just >> doing it >> >> wrong? >> >> >> > >> >> >> >> >> >> For diagnosing your own nameservers, you >> are >> >> better off >> >> >> using the >> >> >> dig(1) utility. >> >> >> >> >> >> Example: >> >> >> >> >> >> dig ipv6.google.com @::1 >> >> >> >> >> >> This causes a dns query for an IPv6 >> address (aka >> >> >> "" query) for the >> >> >> hostname of "ipv6.google.com" >> using the >> >> >> nameserver on the IPv6
Re: host -6 failure
On Sun, Nov 9, 2008 at 3:13 AM, mdh <[EMAIL PROTECTED]> wrote:
> --- On Sat, 11/8/08, David Horn <[EMAIL PROTECTED]> wrote:
>> From: David Horn <[EMAIL PROTECTED]>
>> Subject: Re: host -6 failure
>> To: [EMAIL PROTECTED]
>> Cc: freebsd-questions@freebsd.org
>> Date: Saturday, November 8, 2008, 8:10 PM
>> On Sat, Nov 8, 2008 at 7:55 PM, mdh
>> <[EMAIL PROTECTED]> wrote:
>> > --- On Sat, 11/8/08, David Horn
>> <[EMAIL PROTECTED]> wrote:
>> >> From: David Horn <[EMAIL PROTECTED]>
>> >> Subject: Re: host -6 failure
>> >> To: [EMAIL PROTECTED]
>> >> Cc: freebsd-questions@freebsd.org
>> >> Date: Saturday, November 8, 2008, 7:25 PM
>> >> On Fri, Nov 7, 2008 at 2:18 PM, mdh
>> >> <[EMAIL PROTECTED]> wrote:
>> >> > Howdy folks,
>> >> > I'm having a little trouble understanding
>> a
>> >> problem that the `host` command in RELENG_7_0
>> (very recent)
>> >> is having.
>> >> The '-6' on the command line for host(1)
>> forces an
>> >> IPv6 only
>> >> connection to your nameserver, not necessarily a
>> >> "" query for the
>> >> hostname in question. In this case, your
>> nameservers
>> >> listed in the
>> >> warnings are IPv4 nameservers that host(1) is
>> attempting to
>> >> connect to
>> >> using an ipv4 mapped ipv6 address (which by
>> default is
>> >> disabled in the
>> >> kernel) In other words, don't use host -6 for
>> this
>> >> scenario.
>> >
>> > Yet as I pointed out, the second nameserver in my
>> resolv.conf is ::1 - so shouldn't it work with that?
>> It's clearly trying to contact the first and third
>> nameservers listed. If the behavior I'm experiencing is
>> the proper behavior, then let me pose this question: when
>> would anyone conceivably want to use the -6 option, and why
>> does it exist? My intent was to force a query to hit the
>> nameserver on ::1 rather than 127.0.0.1.
>> >> >
>> >> > domain mydomain
>> >> > search mydomain
>> >> > nameserver 127.0.0.1
>> >> > nameserver ::1
>> >> > nameserver IP.IP.IP.8
>> >> >
>> >> > The DNS server running on localhost is
>> authoritative
>> >> for mydomain. I can ping it via localhost using
>> both v4 and
>> >> v6, and I can also ping the external v4 and v6
>> addresses
>> >> just fine remotely.
>> >> >
>> >> > As I said, I'm new to IPv6, but this
>> behavior
>> >> seems to be counterintuitive. Am I just doing it
>> wrong?
>> >> >
>> >>
>> >> For diagnosing your own nameservers, you are
>> better off
>> >> using the
>> >> dig(1) utility.
>> >>
>> >> Example:
>> >>
>> >> dig ipv6.google.com @::1
>> >>
>> >> This causes a dns query for an IPv6 address (aka
>> >> "" query) for the
>> >> hostname of "ipv6.google.com" using the
>> >> nameserver on the IPv6
>> >> localhost loopback address (::1), and will give a
>> very nice
>> >> verbose
>> >> output. man dig for more details.
>> >
>> > That is more useful, but still doesn't stifle my
>> desire to stomp a potential bug in the base system.
>>
>> Right after sending, I realized that I did not tell you all
>> of the answer
>>
>> host(1) will successfully query ::1 when named is setup to
>> listen on
>> ::1 in named.conf, and ::1 is listed in /etc/resolv.conf (I
>> just ran a
>> test on my box to be sure that it works this way with the
>> -6 switch)
>>
>> Example line from /etc/namedb/named.conf:
>>
>> listen-on-v6{ ::1; any; };
>>
>> And of course you need to restart named after the config
>> change(
>> /etc/rc.d/named restart)
>>
>> To make sure that it is listening on the IPv6 loopback
>> address:
>>
>> netstat -anW -f inet6
>>
>> I do not remember the minimum version of bind (aka named)
>> required for
>> IPv6 off the top of my head, but I am running 9.4.2-P2 on
>> my IPv6
>> machine.
>
> All of the conditions for success are true, however it fails. My DNS
Re: host -6 failure
On Sat, Nov 8, 2008 at 7:55 PM, mdh <[EMAIL PROTECTED]> wrote: > --- On Sat, 11/8/08, David Horn <[EMAIL PROTECTED]> wrote: >> From: David Horn <[EMAIL PROTECTED]> >> Subject: Re: host -6 failure >> To: [EMAIL PROTECTED] >> Cc: freebsd-questions@freebsd.org >> Date: Saturday, November 8, 2008, 7:25 PM >> On Fri, Nov 7, 2008 at 2:18 PM, mdh >> <[EMAIL PROTECTED]> wrote: >> > Howdy folks, >> > I'm having a little trouble understanding a >> problem that the `host` command in RELENG_7_0 (very recent) >> is having. This is by and large my first time working with >> IPv6, which I've been meaning to learn for some time. >> First off, I've got my zone file configured to return a >> record for x1.mydomain and named isn't complaining. >> However, when I run `host -6 x1.mydomain`, host returns the >> following output: >> > >> > ([EMAIL PROTECTED]) [/etc/namedb]: host -6 x1.mydomain >> > >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: >> internal_send: :::127.0.0.1#53: Invalid argument >> > >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: >> internal_send: :::IP.IP.IP.8#53: Invalid argument >> > >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: >> internal_send: :::127.0.0.1#53: Invalid argument >> > >> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: >> internal_send: :::IP.IP.IP.8#53: Invalid argument >> > ;; connection timed out; no servers could be reached >> >> The '-6' on the command line for host(1) forces an >> IPv6 only >> connection to your nameserver, not necessarily a >> "" query for the >> hostname in question. In this case, your nameservers >> listed in the >> warnings are IPv4 nameservers that host(1) is attempting to >> connect to >> using an ipv4 mapped ipv6 address (which by default is >> disabled in the >> kernel) In other words, don't use host -6 for this >> scenario. > > Yet as I pointed out, the second nameserver in my resolv.conf is ::1 - so > shouldn't it work with that? It's clearly trying to contact the first and > third nameservers listed. If the behavior I'm experiencing is the proper > behavior, then let me pose this question: when would anyone conceivably want > to use the -6 option, and why does it exist? My intent was to force a query > to hit the nameserver on ::1 rather than 127.0.0.1. > >> >> Most recent versions of the host(1) command will do both >> "A" (IPv4 >> host record), and "" (IPv6 host record) >> lookups for you >> automatically. For example: >> >> host www.kame.net >> www.kame.net has address 203.178.141.194 >> www.kame.net has IPv6 address >> 2001:200:0:8002:203:47ff:fea5:3085 >> >> > >> > IP.IP.IP.8 is my ISP's DNS server, and is a third >> option just in case the localhost DNS server crashes or goes >> batty while I'm out drinking or somesuch. Here's my >> resolv.conf, which shows ::1 listed as the second nameserver >> entry - however, it seems host -6 never even tries it. >> > >> > domain mydomain >> > search mydomain >> > nameserver 127.0.0.1 >> > nameserver ::1 >> > nameserver IP.IP.IP.8 >> > >> > The DNS server running on localhost is authoritative >> for mydomain. I can ping it via localhost using both v4 and >> v6, and I can also ping the external v4 and v6 addresses >> just fine remotely. >> > >> > As I said, I'm new to IPv6, but this behavior >> seems to be counterintuitive. Am I just doing it wrong? >> > >> >> For diagnosing your own nameservers, you are better off >> using the >> dig(1) utility. >> >> Example: >> >> dig ipv6.google.com @::1 >> >> This causes a dns query for an IPv6 address (aka >> "" query) for the >> hostname of "ipv6.google.com" using the >> nameserver on the IPv6 >> localhost loopback address (::1), and will give a very nice >> verbose >> output. man dig for more details. > > That is more useful, but still doesn't stifle my desire to stomp a potential > bug in the base system. Right after sending, I realized that I did not tell you all of the answer host(1) will successfully query ::1 when named is setup to listen on ::1 in named.conf, and :
Re: host -6 failure
On Fri, Nov 7, 2008 at 2:18 PM, mdh <[EMAIL PROTECTED]> wrote: > Howdy folks, > I'm having a little trouble understanding a problem that the `host` command > in RELENG_7_0 (very recent) is having. This is by and large my first time > working with IPv6, which I've been meaning to learn for some time. First > off, I've got my zone file configured to return a record for x1.mydomain > and named isn't complaining. However, when I run `host -6 x1.mydomain`, host > returns the following output: > > ([EMAIL PROTECTED]) [/etc/namedb]: host -6 x1.mydomain > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: > internal_send: :::127.0.0.1#53: Invalid argument > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: > internal_send: :::IP.IP.IP.8#53: Invalid argument > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: > internal_send: :::127.0.0.1#53: Invalid argument > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: > internal_send: :::IP.IP.IP.8#53: Invalid argument > ;; connection timed out; no servers could be reached The '-6' on the command line for host(1) forces an IPv6 only connection to your nameserver, not necessarily a "" query for the hostname in question. In this case, your nameservers listed in the warnings are IPv4 nameservers that host(1) is attempting to connect to using an ipv4 mapped ipv6 address (which by default is disabled in the kernel) In other words, don't use host -6 for this scenario. Most recent versions of the host(1) command will do both "A" (IPv4 host record), and "" (IPv6 host record) lookups for you automatically. For example: host www.kame.net www.kame.net has address 203.178.141.194 www.kame.net has IPv6 address 2001:200:0:8002:203:47ff:fea5:3085 > > IP.IP.IP.8 is my ISP's DNS server, and is a third option just in case the > localhost DNS server crashes or goes batty while I'm out drinking or > somesuch. Here's my resolv.conf, which shows ::1 listed as the second > nameserver entry - however, it seems host -6 never even tries it. > > domain mydomain > search mydomain > nameserver 127.0.0.1 > nameserver ::1 > nameserver IP.IP.IP.8 > > The DNS server running on localhost is authoritative for mydomain. I can > ping it via localhost using both v4 and v6, and I can also ping the external > v4 and v6 addresses just fine remotely. > > As I said, I'm new to IPv6, but this behavior seems to be counterintuitive. > Am I just doing it wrong? > For diagnosing your own nameservers, you are better off using the dig(1) utility. Example: dig ipv6.google.com @::1 This causes a dns query for an IPv6 address (aka "" query) for the hostname of "ipv6.google.com" using the nameserver on the IPv6 localhost loopback address (::1), and will give a very nice verbose output. man dig for more details. Good Luck. BTW, if you have not already setup an IPv6 tunnel to the internet, I highly recommend SixXS's (www.sixxs.net) free tunnels (and the sixxs-aiccu port), or you can look at Hurricane Electric (www.he.net), and some other tunnel brokers as well. -_Dave > Thanks, Matt > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipv6
On Sat, Sep 20, 2008 at 11:35 AM, beni <[EMAIL PROTECTED]> wrote: > Hi, > > I have a question about IPv6. > I installed /net/freenet6 and edited the /usr/local/etc/gw6c.conf file with > the login and password given by Go6.net. > I added freenet6_enable="YES", ipv6_enable="YES" and > ipv6_network_interfaces="vr0 tun0" to my /etc/rc.conf. > An ifconfig shows this : > bsdaddict# ifconfig vr0 > vr0: flags=8843 metric 0 mtu 1500 >options=2808 >ether 00:0c:76:c2:2c:b7 >inet6 fe80::20c:76ff:fec2:2cb7%vr0 prefixlen 64 scopeid 0x1 >inet 192.168.1.101 netmask 0xff00 broadcast 192.168.1.255 >media: Ethernet autoselect (100baseTX ) >status: active > bsdaddict# > So I think the installation of ipv6 is ok : surfing to > http://go6.net/4105/freenet.asp says "You are using IPv6 from ...". But in > X-chat, when connecting to Freenode p.ex., I get this : > > FreebsdBeni n=FreeBSD 213.219.143.49.adsl.dyn.edpnet.net :You are now logged > in. (id FreebsdBeni, username n=FreeBSD, hostname > 213.219.143.49.adsl.dyn.edpnet.net) Even if you have properly setup/configured a tunnel to provide IPv6, does not mean that IPv4 goes away. You are running in dual stack mode (both IPv4, and IPv6 active) You may want to read up a little bit on IPv6 details and background in the FreeBSD handbook http://www.freebsd.org/doc/en/books/handbook/network-ipv6.html and in the go6.net wiki (among lots of other good IPv6 articles. Google is your friend here.) http://wiki.go6.net/index.php?title=IPv6_transition_mechanisms Most applications that are IPv6 aware will default to using IPv6 if everything is setup properly. This includes giving an IPv6 capable DNS name to your IRC client. (ipv6.chat.us.freenode.net and ipv6.chat.eu.freenode.net are a few that are IPv6) I'm not much of an IRC user myself, but I see that several of the ports of xchat are IPv6 enabled. You did not specify what version of Xchat you are using, so I can't comment further there. Make sure you are using a version of xchat that supports IPv6, and that you are using the appropriate IPv6 freenode DNS name. You can also find a listing of IPv6 capable application ports over on http://www.freshports.org/ipv6/ > > And that is not a ipv6 address. So what am I missing here ? Is it my config or > is my isp converting my ipv6 back to ipv4 ? It is your config. An ISP can not really "automagically" change you from IPv6 to IPv4 when you have a tunnel active. You do not provide an ifconfig for your tunnel interface (tun0), so it is hard to tell what your configuration looks like. Can you ping6 the site in question ? (ie: ping6 ipv6.chat.us.freenode.net) > > Thanks for any hints on this. > -- > Beni. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0 No Sound: emu10k1
Thanks for the hint. snd_emu10kx instead of snd_emu10k1 (doh!) I knew it had to be something simple. Everything is working great now. --_Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0 No Sound: emu10k1
I'm hoping that someone can help me get my soundcard working properly with FreeBSD 7.0. I have tried all of the suggestions in the handbook, and am at a loss on next steps to diagnose. I am starting to think that I am missing something very simple. Hardware: SoundBlaster Audigy 2 ZS (PCI bus) installed in Dell Dimension 4100 (P3 1Ghz circa 2001, no internal sound card) Software: FreeBSD 7.0p2 (GENERIC kernel updated using freebsd-update) Driver: snd_emu10k1 (via loader.conf) I am not getting any error messages that indicate a problem. The driver is loading and /dev/sndstat shows proper output. The issue is that I get absolutely no sound out of my soundcard. I have tried using mpg123, and cat file >/dev/dsp without any output. The mixer levels look good (to me), and I am getting no failure messages. I have tested the speakers with another audio source (no issues), and am about the try swapping the soundcard into a new machine (running a different OS) to ensure that the card itself is not fried. Apologies for the long email, see detailed output below... Thanks in advance! --Dave == uname -a FreeBSD x-bsd.private.nullcore.com 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed Jun 18 07:33:20 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 === cat loader.conf snd_emu10k1_load="YES" === sysctl -a |grep hw.snd hw.snd.latency_profile: 1 hw.snd.latency: 5 hw.snd.report_soft_formats: 1 hw.snd.compat_linux_mmap: 0 hw.snd.feeder_buffersize: 16384 hw.snd.feeder_rate_round: 25 hw.snd.feeder_rate_max: 2016000 hw.snd.feeder_rate_min: 1 hw.snd.verbose: 4 hw.snd.maxautovchans: 16 hw.snd.default_unit: 0 hw.snd.version: 2007061600/i386 hw.snd.default_auto: 0 sysctl -a |grep pcm dev.pcm.0.%desc: Creative Audigy (EMU10K2) dev.pcm.0.%driver: pcm dev.pcm.0.%location: slot=9 function=0 dev.pcm.0.%pnpinfo: vendor=0x1102 device=0x0004 subvendor=0x1102 subdevice=0x2005 class=0x040100 dev.pcm.0.%parent: pci2 dev.pcm.0.eapd: 1 dev.pcm.0.play.vchans: 1 dev.pcm.0.play.vchanrate: 48000 dev.pcm.0.play.vchanformat: s16le dev.pcm.0.rec.vchans: 1 dev.pcm.0.rec.vchanrate: 48000 dev.pcm.0.rec.vchanformat: s16le dev.pcm.0.buffersize: 4096 = dmesg |grep pcm pcm0: port 0xdf00-0xdf3f irq 10 at device 9.0 on pci2 pcm0: pcm0: [ITHREAD] with hw.snd.verbose=4, dmesg shows the following after trying to play an mp3 file for several seconds: sndbuf_remalloc(): b=0xc2883b00 0 -> 4096 [4096] chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[4096/64/64] limit=4096 chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[4096/64/64] limit=4096 sndbuf_remalloc(): b=0xc2883b00 4096 [4096] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[2048/64/32] limit=0 sndbuf_remalloc(): b=0xc2883b00 4096 [2048] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=512 b[4096/128/2] bs[4096/128/32] limit=4096 pcm0: chn_trigger() pcm0:play:dsp0.p1: calling go=0x , prev=0x chn_resizebuf: PCMDIR_PLAY (hardware) timeout=512 b[4096/128/2] bs[4096/128/32] limit=0 sndbuf_remalloc(): b=0xc2883b00 4096 [4096] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[4096/64/64] limit=4096 chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[4096/64/64] limit=4096 sndbuf_remalloc(): b=0xc2883b00 4096 [4096] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[2048/64/32] limit=0 sndbuf_remalloc(): b=0xc2883b00 4096 [2048] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=512 b[4096/128/2] bs[4096/128/32] limit=4096 sndbuf_remalloc(): b=0xc2883b00 4096 -> 8192 [8192] chn_resizebuf: PCMDIR_PLAY (hardware) timeout=256 b[4096/256/2] bs[8192/256/32] limit=4096 sndbuf_remalloc(): b=0xc2883b00 8192 -> 16384 [16384] chn_resizebuf: PCMDIR_PLAY (hardware) timeout=128 b[4096/512/2] bs[16384/512/32] limit=4096 sndbuf_remalloc(): b=0xc2883b00 16384 -> 65536 [65536] chn_resizebuf: PCMDIR_PLAY (hardware) timeout=23 b[4096/2048/2] bs[65536/2048/32] limit=4096 pcm0: chn_trigger() pcm0:play:dsp0.p1: calling go=0x , prev=0x chn_resizebuf: PCMDIR_PLAY (hardware) timeout=23 b[4096/2048/2] bs[65536/2048/32] limit=0 sndbuf_remalloc(): b=0xc2883b00 65536 [65536] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[4096/64/64] limit=4096 chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[4096/64/64] limit=4096 sndbuf_remalloc(): b=0xc2883b00 65536 [4096] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=1024 b[4096/64/2] bs[2048/64/32] limit=0 sndbuf_remalloc(): b=0xc2883b00 65536 [2048] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=512 b[4096/128/2] bs[4096/128/32] limit=4096 sndbuf_remalloc(): b=0xc2883b00 65536 [4096] NOCHANGE chn_resizebuf: PCMDIR_PLAY (hardware) timeout=256 b[4096/256/2] bs[8192/256/32] limit=4096 sndbuf_remalloc(): b=0xc28
Re: cups-base upgrade and samba
I just upgraded my cups-base install to 1.3.3_1, and ran into similar issues at first. Try: "portaudit -F" to upgrade your audit database. I believe portaudit originally thought 1.3.3_1 fell into the "affected" versions, but looks to be the fixed version in the latest database. http://www.freshports.org/print/cups-base/ Good Luck. --_Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
