routed -q needs at least two working interfaces
Hello,
I have two machines connected to the same switch.
First machine is called router, has gateway_enable=YES
and shows the following interfaces
router# ifconfig
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE
ether 00:50:45:5d:9a:bc
inet 192.168.1.158 netmask 0xff00 broadcast 192.168.1.255
media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1)
status: active
bge1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE
ether 00:50:45:5d:9a:bd
inet 192.168.17.17 netmask 0xff00 broadcast 192.168.17.255
media: Ethernet autoselect (none)
status: no carrier
...
and the second machine called client:
client# ifconfig
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE
ether 00:50:45:5d:c6:ec
inet 192.168.1.157 netmask 0xff00 broadcast 192.168.1.255
media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1)
status: active
bge1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE
ether 00:50:45:5d:c6:ed
media: Ethernet autoselect (none)
status: no carrier
...
Now on the router I start the route daemon:
router# /sbin/routed -s -d -t
-- 10:43:21 --
Tracing actions started
Add interface bge0 192.168.1.158 --192.168.1.0 (mask 0xff00)
RCVBUF=61440
turn on RIP
Add interface bge1 192.168.17.17 --192.168.17.0 (mask 0xff00)
Add interface lo0 127.0.0.1 --127.0.0.1 (mask 0x)
LOOPBACK PASSIVE
Add127.0.0.1 (mask 0x)--127.0.0.1 metric=0 lo0 IF
Add192.168.17.0--192.168.17.17metric=0 bge1 IF
Add192.168.1.0 --192.168.1.158metric=0 bge0 IF
-- 10:43:21 --
ignore RTM_NEWMADDR for AF 173
ignore RTM_NEWMADDR for AF 173
ignore RTM_NEWMADDR without dst
ignore RTM_NEWMADDR without dst
-- 10:43:26 --
send all routes and inhibit dynamic updates for 4.884 sec
and on the client:
client# /sbin/routed -d -q -t
-- 10:45:36 --
Tracing actions started
Add interface bge0 192.168.1.157 --192.168.1.0 (mask 0xff00)
RCVBUF=61440
turn on RIP
Add interface lo0 127.0.0.1 --127.0.0.1 (mask 0x)
LOOPBACK PASSIVE
Add127.0.0.1 (mask 0x)--127.0.0.1 metric=0 lo0 IF
Add192.168.1.0 --192.168.1.157metric=0 bge0 IF
-- 10:45:36 --
ignore RTM_NEWMADDR for AF 172
-- 10:45:36 --
Add #1 192.168.1.0 --192.168.1.158metric=1 bge0 10:45:36
Add192.168.17.0--192.168.1.158metric=1 bge0 10:45:36
-- 10:45:37 --
turn on Router Discovery client using 192.168.1.158 via bge0
Add0.0.0.0 --192.168.1.158metric=15 bge0 RDISC
turn off RIP
Del192.168.17.0--192.168.1.158metric=1 bge0 10:45:36
As not expected the route to net 192.168.17.0 is deleted immediately.
Brining up the second interface on the client lets routed work as expected:
client# ifconfig bge1 192.168.18.18
client# ifconfig bge1 up
client# /sbin/routed -d -q -t
-- 10:51:12 --
Tracing actions started
Add interface bge0 192.168.1.157 --192.168.1.0 (mask 0xff00)
RCVBUF=61440
turn on RIP
Add interface bge1 192.168.18.18 --192.168.18.0 (mask 0xff00)
Add interface lo0 127.0.0.1 --127.0.0.1 (mask 0x)
LOOPBACK PASSIVE
Add127.0.0.1 (mask 0x)--127.0.0.1 metric=0 lo0 IF
Add192.168.18.0--192.168.18.18metric=0 bge1 IF
Add192.168.1.0 --192.168.1.157metric=0 bge0 IF
-- 10:51:12 --
ignore RTM_NEWMADDR for AF 172
ignore RTM_NEWMADDR without dst
-- 10:51:12 --
Add #1 192.168.1.0 --192.168.1.158metric=1 bge0 10:51:12
Add192.168.17.0--192.168.1.158metric=1 bge0 10:51:12
-- 10:51:13 --
turn on Router Discovery client using 192.168.1.158 via bge0
Add0.0.0.0 --192.168.1.158metric=15 bge0 RDISC
it seems to be impossible to get routed working on a machine with just
one network adapter.
I have testet this on FreeBSD 8.1 Stable.
I have seen the same problem on FreeBSD 7.0 and on FreeBSD 5.5
maybe it exists on FreeBSD 6 too.
the following patch solves the problem.
regards
Tobias Herre
--- /usr/src/sbin/routed/rdisc.orig2010-09-22 11:02:00.040741231 +
+++ /usr/src/sbin/routed/rdisc.c2010-09-22 11:02:10.671926200 +
@@ -557,7 +557,7 @@
}
/* turn RIP on or off */
-if (!rdisc_ok || rip_interfaces 1) {
+if (!rdisc_ok || rip_interfaces = 1) {
rip_on(0);
} else {
rip_off();
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
kern/150858: GEOM_LABEL is not compatible with newfs -r flag
Number: 150858
Category: kern
Synopsis: GEOM_LABEL is not compatible with newfs -r flag
Confidential: no
Severity: non-critical
Priority: medium
Responsible:freebsd-bugs
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Wed Sep 22 12:00:12 UTC 2010
Closed-Date:
Last-Modified:
Originator: Konstantin Kukushkin
Release:8.1-STABLE
Organization:
Rambler
Environment:
FreeBSD dash.local 8.1-STABLE FreeBSD 8.1-STABLE #0: Wed Sep 22 13:18:16 MSD
2010 r...@dash.local:/var/tmp/obj/usr/src/sys/EEE8 i386
Description:
For any provider, GEOM_LABEL strictly checks that ufs occupied all its
space. But filesystem can be smaller, in case if newfs(8) was run with
-r flag. So, GEOM_LABEL is not compatible with newfs -r flag.
When check is more permissive (as in attached patch) all work OK:
[pts/0] r...@dash:/usr/home/dark# uname -rp
8.1-STABLE i386
[pts/0] r...@dash:/usr/home/dark# ll /dev/ufsid/
total 0
crw-r- 1 root operator0, 93 22 ÓÅÎ 17:24 4992d90831a79611
[pts/0] r...@dash:/usr/home/dark# mdconfig -s 32m
md0
[pts/0] r...@dash:/usr/home/dark# newfs -r 4 -U /dev/md0
/dev/md0: 32.0MB (65532 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 8.00MB, 512 blks, 1024 inodes.
with soft updates
super-block backups (for fsck -b #) at:
160, 16544, 32928, 49312
[pts/0] r...@dash:/usr/home/dark# ll /dev/ufsid/
total 0
crw-r- 1 root operator0, 93 22 ÓÅÎ 17:24 4992d90831a79611
crw-r- 1 root operator0, 118 22 ÓÅÎ 13:38 4c99ce860db39b88
[pts/0] r...@dash:/usr/home/dark# glabel status
Name Status Components
ntfs/sys N/A ada0s1
msdosfs/SYS N/A ada0s2
msdosfs/BIOS N/A ada0s3
ntfs/BIG N/A ada1s2
ufsid/4992d90831a79611 N/A ada1s1a
ufsid/4c99ce860db39b88 N/A md0
How-To-Repeat:
radius# uname -rp
8.1-20100726-SNAP i386
radius# ll /dev/ufsid/
total 0
crw-r- 1 root operator0, 98 21 ÓÅÎ 22:01 4c98f1c148b0469b
crw-r- 1 root operator0, 99 21 ÓÅÎ 22:01 4c98f1c978a6bb52
radius# mdconfig -s 32m
md0
radius# newfs -r 4 -U /dev/md0
/dev/md0: 32.0MB (65532 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 8.00MB, 512 blks, 1024 inodes.
with soft updates
super-block backups (for fsck -b #) at:
160, 16544, 32928, 49312
radius# ll /dev/ufsid/
total 0
crw-r- 1 root operator0, 98 21 ÓÅÎ 22:01 4c98f1c148b0469b
crw-r- 1 root operator0, 99 21 ÓÅÎ 22:01 4c98f1c978a6bb52
radius# glabel status
Name Status Components
ufsid/4c98f1c148b0469b N/A ada2d
ufsid/4c98f1c978a6bb52 N/A ada3d
Fix:
Use attached patch.
Patch attached with submission follows:
--- /sys/geom/label/g_label_ufs.c.orig 2010-07-11 23:06:52.0 +0400
+++ /sys/geom/label/g_label_ufs.c 2010-09-22 12:21:23.0 +0400
@@ -83,10 +83,10 @@
continue;
/* Check for magic and make sure things are the right size */
if (fs-fs_magic == FS_UFS1_MAGIC fs-fs_fsize 0
- pp-mediasize / fs-fs_fsize == fs-fs_old_size) {
+ pp-mediasize / fs-fs_fsize = fs-fs_old_size) {
/* Valid UFS1. */
} else if (fs-fs_magic == FS_UFS2_MAGIC fs-fs_fsize 0
- pp-mediasize / fs-fs_fsize == fs-fs_size) {
+ pp-mediasize / fs-fs_fsize = fs-fs_size) {
/* Valid UFS2. */
} else {
g_free(fs);
Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: kern/150858: [geom] [geom_label] [patch] glabel(8) is not compatible with newfs -r flag
Old Synopsis: GEOM_LABEL is not compatible with newfs -r flag New Synopsis: [geom] [geom_label] [patch] glabel(8) is not compatible with newfs -r flag Responsible-Changed-From-To: freebsd-bugs-freebsd-geom Responsible-Changed-By: arundel Responsible-Changed-When: Wed Sep 22 12:14:52 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=150858 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: kern/150796: [panic] [suj] [ufs] [softupdates] Panic on portbuild
Old Synopsis: [panic] [suj] Panic on portbuild New Synopsis: [panic] [suj] [ufs] [softupdates] Panic on portbuild Responsible-Changed-From-To: freebsd-bugs-freebsd-fs Responsible-Changed-By: arundel Responsible-Changed-When: Wed Sep 22 12:24:16 UTC 2010 Responsible-Changed-Why: Assign to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=150796 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
kern/150859: [tmpfs] tmpfs on stable/8-amd64 panic
Number: 150859
Category: kern
Synopsis: [tmpfs] tmpfs on stable/8-amd64 panic
Confidential: no
Severity: serious
Priority: medium
Responsible:freebsd-bugs
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Wed Sep 22 13:00:13 UTC 2010
Closed-Date:
Last-Modified:
Originator: Dmitry Morozovsky
Release:FreeBSD [78]-STABLE {i386,amd64}
Organization:
Cronyx Plus LLC (RiNet ISP)
Environment:
System: FreeBSD 8-STABLE, 7-STABLE
Description:
tmpfs on active usage (ports tinderbox over it) panicked with the details below.
8.1-STABLE FreeBSD 8.1-STABLE #2 r212822M: Mon Sep 20 22:05:13 MSD 2010
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:248
#1 0x801a16ac in db_fncall (dummy1=Variable dummy1 is not available.
) at /usr/src/sys/ddb/db_command.c:548
#2 0x801a19e1 in db_command (last_cmdp=0x8070f080,
cmd_table=Variable cmd_table is not available.
) at /usr/src/sys/ddb/db_command.c:445
#3 0x801a1c30 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:498
#4 0x801a3c79 in db_trap (type=Variable type is not available.
) at /usr/src/sys/ddb/db_main.c:229
#5 0x802e055e in kdb_trap (type=3, code=0, tf=0xff81ddf53f60) at
/usr/src/sys/kern/subr_kdb.c:535
#6 0x804febe6 in trap (frame=0xff81ddf53f60) at
/usr/src/sys/amd64/amd64/trap.c:562
#7 0x804e33b4 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:224
#8 0x802e06fd in kdb_enter (why=0x8055c85c panic, msg=0xa
Address 0xa out of bounds) at cpufunc.h:63
#9 0x802af43b in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:573
#10 0x80c24f5e in tmpfs_alloc_vp (mp=0xff000a23,
node=0xff001f8fa7e0, lkflag=525312, vpp=0xff81ddf542f0)
at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_subr.c:383
#11 0x80c23572 in tmpfs_lookup (v=Variable v is not available.
) at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_vnops.c:95
#12 0x8032c4e0 in vfs_cache_lookup (ap=Variable ap is not available.
) at vnode_if.h:80
#13 0x8052a6b0 in VOP_LOOKUP_APV (vop=0x80c26260,
a=0xff81ddf542d0) at vnode_if.c:123
#14 0x8024df8f in null_lookup (ap=0xff81ddf543d0) at vnode_if.h:54
#15 0x8052a6b0 in VOP_LOOKUP_APV (vop=0x806b4de0,
a=0xff81ddf543d0) at vnode_if.c:123
#16 0x803337a2 in lookup (ndp=0xff81ddf54850) at vnode_if.h:54
#17 0x803348aa in namei (ndp=0xff81ddf54850) at
/usr/src/sys/kern/vfs_lookup.c:269
#18 0x8034cb6c in vn_open_cred (ndp=0xff81ddf54850,
flagp=0xff81ddf54958, cmode=0, vn_open_flags=Variable vn_open_flags is
not available.
) at /usr/src/sys/kern/vfs_vnops.c:188
#19 0x8032f25f in vop_stdvptocnp (ap=Variable ap is not available.
) at /usr/src/sys/kern/vfs_default.c:761
#20 0x8024e615 in null_vptocnp (ap=0xff81ddf54a20) at
/usr/src/sys/fs/nullfs/null_vnops.c:780
#21 0x8032b4c8 in vn_vptocnp_locked (vp=0xff81ddf54ab0,
cred=0xff02161cb700, buf=0xff01d476d900 , buflen=0xff81ddf54aac)
at vnode_if.h:1544
#22 0x8032b72d in vn_fullpath1 (td=0xff00a46897c0,
vp=0xff01024c7588, rdir=0xff000a06f938, buf=0xff01d476d900 ,
retbuf=0xff81ddf54b20, buflen=255)
at /usr/src/sys/kern/vfs_cache.c:1175
#23 0x8032b98e in kern___getcwd (td=0xff00a46897c0, buf=0x800c06208
Address 0x800c06208 out of bounds, bufseg=UIO_USERSPACE, buflen=256)
at /usr/src/sys/kern/vfs_cache.c:940
#24 0x804fe76f in syscall (frame=0xff81ddf54c80) at
/usr/src/sys/amd64/amd64/trap.c:945
#25 0x804e3692 in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:377
#26 0x000800936e3c in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) up 10
#10 0x80c24f5e in tmpfs_alloc_vp (mp=0xff000a23,
node=0xff001f8fa7e0, lkflag=525312, vpp=0xff81ddf542f0)
at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_subr.c:383
383 panic(tmpfs_alloc_vp: type %p %d, node,
(int)node-tn_type);
(kgdb) l
378 if (node-tn_dir.tn_parent == node)
379 vp-v_vflag |= VV_ROOT;
380 break;
381
382 default:
383 panic(tmpfs_alloc_vp: type %p %d, node,
(int)node-tn_type);
384 }
385
386 vnode_pager_setsize(vp, node-tn_size);
387 error = insmntque(vp, mp);
How-To-Repeat:
configure ports tinderbox (ports-mgmt/tinderbox)
mount -t mptfs tmpfs /path/to/tinderbox/build
/usr/local/tb/scripts/tc rinderbuild -nullfs -b your-build-name
Fix:
Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To
Re: bin/140972: sysintall(8): 8.0-RELEASE-i386-memstick Fixit broken - No USB devices found!
The following reply was made to PR bin/140972; it has been noted by GNATS. From: Mij m...@bitchx.it To: bug-follo...@freebsd.org, 4548b...@razorfever.net Cc: Subject: Re: bin/140972: sysintall(8): 8.0-RELEASE-i386-memstick Fixit broken - No USB devices found! Date: Wed, 22 Sep 2010 15:42:42 +0200 A tip for ZFS users: - like some other users, the Re-scan devices trick didn't help for me - I insisted on this problem just because Fixit kicked just fine on the virgin system, and stopped working (same image) after it was installed - a clue in my case was the appearance of a stray Open_Disk( in the first curses screen (Country Selection) of sysinstall - the USB drive was actually detected as da0 Based on this, if you interrupt loader, enter its CLI, and pre-load the ZFS modules, the Open_Disk( string will disappear and you'll get back Fixit: OK load /boot/kernel/opensolaris.ko OK load /boot/kernel/zfs.ko OK boot I could not figure out why sysinstall is confused by the presence of the ZFS drive (which is ad6, or ada0 if ahci would be loaded). ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: kern/150859: [tmpfs] tmpfs on stable/8-amd64 panic
The following reply was made to PR kern/150859; it has been noted by GNATS. From: Jaakko Heinonen j...@freebsd.org To: Dmitry Morozovsky ma...@freebsd.org Cc: bug-follo...@freebsd.org, delp...@freebsd.org Subject: Re: kern/150859: [tmpfs] tmpfs on stable/8-amd64 panic Date: Wed, 22 Sep 2010 19:39:25 +0300 On 2010-09-22, Dmitry Morozovsky wrote: at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_subr.c:383 #11 0x80c23572 in tmpfs_lookup (v=Variable v is not available. ) at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_vnops.c:95 383 panic(tmpfs_alloc_vp: type %p %d, node, (int)node-tn_type); This seems to be a duplicate of kern/122038. r197953 hasn't been MFCd to stable/8. -- Jaakko ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: kern/150859: [tmpfs] tmpfs on stable/8-amd64 panic
Synopsis: [tmpfs] tmpfs on stable/8-amd64 panic State-Changed-From-To: open-closed State-Changed-By: arundel State-Changed-When: Wed Sep 22 17:31:04 UTC 2010 State-Changed-Why: Duplicate of #122038. You might want to contact delphij and ask if he could MFC r197953 to stable/8 (and maybe also stable/7). http://www.freebsd.org/cgi/query-pr.cgi?pr=150859 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: kern/89522: 6.0-RELEASE will not boot on some Compaqs with mouse connected
The following reply was made to PR kern/89522; it has been noted by GNATS. From: Pete French petefre...@ticketswitch.com To: bug-follo...@freebsd.org, petefre...@ticketswitch.com Cc: Subject: Re: kern/89522: 6.0-RELEASE will not boot on some Compaqs with mouse connected Date: Wed, 22 Sep 2010 20:48:40 +0100 [last reply came out blank for some reason] I no longer have the hardware concerned, so am unable to test later versions of BSD for this bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: bin/106049: commit references a PR
The following reply was made to PR bin/106049; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: bin/106049: commit references a PR
Date: Wed, 22 Sep 2010 20:28:06 + (UTC)
Author: marius
Date: Wed Sep 22 20:27:59 2010
New Revision: 213027
URL: http://svn.freebsd.org/changeset/base/213027
Log:
MFC: r173852
Add the -W options, which acts the same as -w but will generate
unique names based on the submitted filename, a strftime(3) format
string and a two digit sequence number.
By default the strftime(3) format string is %Y%m%d (MMDD), but
this can be changed by the -F option.
PR: bin/106049 (based on patch in that PR)
Approved by: grog@ (mentor)
Modified:
stable/7/libexec/tftpd/Makefile
stable/7/libexec/tftpd/tftpd.8
stable/7/libexec/tftpd/tftpd.c
Directory Properties:
stable/7/libexec/tftpd/ (props changed)
Modified: stable/7/libexec/tftpd/Makefile
==
--- stable/7/libexec/tftpd/MakefileWed Sep 22 20:17:34 2010
(r213026)
+++ stable/7/libexec/tftpd/MakefileWed Sep 22 20:27:59 2010
(r213027)
@@ -5,6 +5,7 @@ PROG= tftpd
SRCS= tftpd.c tftpsubs.c
DPADD=${LIBUTIL}
LDADD=-lutil
+WFORMAT=0
MAN= tftpd.8
CFLAGS+=-I${.CURDIR}/../../usr.bin/tftp
.PATH:${.CURDIR}/../../usr.bin/tftp
Modified: stable/7/libexec/tftpd/tftpd.8
==
--- stable/7/libexec/tftpd/tftpd.8 Wed Sep 22 20:17:34 2010
(r213026)
+++ stable/7/libexec/tftpd/tftpd.8 Wed Sep 22 20:27:59 2010
(r213027)
@@ -40,7 +40,8 @@
.Nd Internet Trivial File Transfer Protocol server
.Sh SYNOPSIS
.Nm tftpd
-.Op Fl cClnw
+.Op Fl cClnwW
+.Op Fl F Ar strftime-format
.Op Fl s Ar directory
.Op Fl u Ar user
.Op Fl U Ar umask
@@ -142,6 +143,13 @@ except it falls back to
specified via
.Fl s
if a directory does not exist for the client's IP.
+.It Fl F
+Use this
+.Xr strftime 3
+compatible format string for the creation of the suffix if
+.Fl W
+is specified.
+By default the string %Y%m%d is used.
.It Fl l
Log all requests using
.Xr syslog 3
@@ -184,6 +192,17 @@ Allow write requests to create new files
By default
.Nm
requires that the file specified in a write request exist.
+Note that this only works in directories writable by the user
+specified with
+.Fl u
+option
+.It Fl W
+As
+.Fl w
+but append a MMDD.nn sequence number to the end of the filename.
+Note that the string MMDD can be changed the
+.Fl F
+option.
.El
.Sh SEE ALSO
.Xr tftp 1 ,
@@ -212,10 +231,17 @@ the
.Fl u
option was introduced in
.Fx 4.2 ,
-and the
+the
.Fl c
option was introduced in
-.Fx 4.3 .
+.Fx 4.3 ,
+and the
+.Fl F
+and
+.Fl W
+options were introduced in
+.Fx 7 .
+.Pp
.Sh BUGS
Files larger than 33488896 octets (65535 blocks) cannot be transferred
without client and server supporting blocksize negotiation (RFC1783).
Modified: stable/7/libexec/tftpd/tftpd.c
==
--- stable/7/libexec/tftpd/tftpd.c Wed Sep 22 20:17:34 2010
(r213026)
+++ stable/7/libexec/tftpd/tftpd.c Wed Sep 22 20:27:59 2010
(r213027)
@@ -110,6 +110,8 @@ static int suppress_naks;
static intlogging;
static intipchroot;
static intcreate_new = 0;
+static char *newfile_format = %Y%m%d;
+static intincrease_name = 0;
static mode_t mask = S_IWGRP|S_IWOTH;
static const char *errtomsg(int);
@@ -134,7 +136,7 @@ main(int argc, char *argv[])
tzset();/* syslog in localtime */
openlog(tftpd, LOG_PID | LOG_NDELAY, LOG_FTP);
- while ((ch = getopt(argc, argv, cClns:u:U:w)) != -1) {
+ while ((ch = getopt(argc, argv, cCF:lns:u:U:wW)) != -1) {
switch (ch) {
case 'c':
ipchroot = 1;
@@ -142,6 +144,9 @@ main(int argc, char *argv[])
case 'C':
ipchroot = 2;
break;
+ case 'F':
+ newfile_format = optarg;
+ break;
case 'l':
logging = 1;
break;
@@ -160,6 +165,10 @@ main(int argc, char *argv[])
case 'w':
create_new = 1;
break;
+ case 'W':
+ create_new = 1;
+ increase_name = 1;
+ break;
default:
syslog(LOG_WARNING, ignoring unknown option -%c, ch);
}
@@ -513,6 +522,57 @@ option_fail:
FILE *file;
/*
+ * Find the next value for MMDD.nn when the file to be
Re: kern/136386: [bluetooth] [headers] [request] Can the following bluez macros be added to bluetooth.h
Old Synopsis: [headers] [request] Can the following bluez macros be added to bluetooth.h New Synopsis: [bluetooth] [headers] [request] Can the following bluez macros be added to bluetooth.h Responsible-Changed-From-To: freebsd-bugs-freebsd-bluetooth Responsible-Changed-By: arundel Responsible-Changed-When: Wed Sep 22 23:06:44 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=136386 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: kern/150798: [ipfw] ipfw2 fwd rule matches packets but does not do the job in fact.
Old Synopsis: ipfw2 fwd rule matches packets but does not do the job in fact. New Synopsis: [ipfw] ipfw2 fwd rule matches packets but does not do the job in fact. Responsible-Changed-From-To: freebsd-bugs-freebsd-ipfw Responsible-Changed-By: linimon Responsible-Changed-When: Thu Sep 23 05:17:52 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=150798 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
