Re: natd bug with pptp, hack fix, question
On Wed, Sep 27, 2000 at 12:34:36AM -0400, David G. Andersen wrote: > With natd+ipfw, I was setting up a front-end firewall for > a client. The firewall has several real IP addresses > (we'll call them 10.0.0.1 and 10.0.0.2) and two > MS PPTP servers behind it. > > > 10.0.0.1 > 10.0.0.2 > World- | firewall | - PPTP-1 192.168.1.1 > \ PPTP-2 192.168.1.2 > > I setup the natd.conf file in the way one would expect: > > redirect_proto gre 192.168.1.1 10.0.0.1 > redirect_port tcp 192.168.1.1:1723 10.0.0.1:1723 > > redirect_proto gre 192.168.1.2 10.0.0.2 > redirect_port tcp 192.168.1.2:1723 10.0.0.2:1723 > > [With or without the redirect_proto gre; with the > -current libalias, I would expect to perhaps not need it] > > Anyway, to make a long story short, it doesn't work. The > first PPTP server is reachable and happy, but the virtual > PPTP server on 10.0.0.2 is unreachable. When natd sees > the first GRE packet, it calls > > FindPptpIn(), which then checks: > > link = FindLinkIn(dst_addr, alias_addr, > NO_DEST_PORT, call_id, > LINK_PPTP, 1); > > This check fails, and it falls back to a call to > FindOriginalAddress(alias_addr); > > Two questions: > > a) I'm not sure about the location of the call to > AddLink for for this connection in the PPTP aliasing > code, so I couldn't determine the right way to set > things up. > > b) Shouldn't this also check to see if there's a default > GRE relay host for this alias address? > > One issue: > > I hacked my client's natd program in the interim to > AddLink inside FindPptpIn if it doesn't get a returned > link, and it works like a charm. However, it's definitely > the wrong thing to do and only a temporary solution. > The fact that it works, however, suggests that this > should be something relatively straightforward for someone > with a clue about how libalias works to fix. > > Anyone? I'm happy to fix it (though my client might > not like that. :-), but I'd love a bit of a hint about > the right way to address this within the libalias framework > before I blunder through making changes that won't be > accepted. > > Thanks! > > This is using the 4-stable natd and the libalias from -current. > >-Dave > > {I'm not on -hackers at the moment, so if you could CC: me on > a response, I'd appreciate it}. > Please try the attached patch. -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age Index: alias.c === RCS file: /home/ncvs/src/lib/libalias/alias.c,v retrieving revision 1.24 diff -u -p -r1.24 alias.c --- alias.c 2000/09/01 16:38:53 1.24 +++ alias.c 2000/09/27 08:13:23 @@ -711,13 +711,14 @@ GreAliasIn(struct ip *pip) { u_short call_id; struct alias_link *link; +static struct in_addr null_addr = {INADDR_NONE}; /* Return if proxy-only mode is enabled. */ if (packetAliasMode & PKT_ALIAS_PROXY_ONLY) return (PKT_ALIAS_OK); if (PptpGetCallID(pip, &call_id)) { - if ((link = FindPptpIn(pip->ip_src, pip->ip_dst, call_id)) != NULL) { + if ((link = FindPptpIn(pip->ip_src, pip->ip_dst, null_addr, call_id)) != NULL) +{ struct in_addr alias_address; struct in_addr original_address; Index: alias_db.c === RCS file: /home/ncvs/src/lib/libalias/alias_db.c,v retrieving revision 1.38 diff -u -p -r1.38 alias_db.c --- alias_db.c 2000/08/31 12:47:57 1.38 +++ alias_db.c 2000/09/27 08:13:24 @@ -1632,6 +1632,7 @@ FindUdpTcpOut(struct in_addr src_addr, struct alias_link * FindPptpIn(struct in_addr dst_addr, struct in_addr alias_addr, + struct in_addr src_addr, u_short call_id) { struct alias_link *link; @@ -1640,12 +1641,9 @@ FindPptpIn(struct in_addr dst_addr, NO_DEST_PORT, call_id, LINK_PPTP, 1); -if (link == NULL && !(packetAliasMode & PKT_ALIAS_DENY_INCOMING)) +if (link == NULL && src_addr.s_addr != INADDR_NONE) { -struct in_addr target_addr; - -target_addr = FindOriginalAddress(alias_addr); -link = AddLink(target_addr, dst_addr, alias_addr, +link = AddLink(src_addr, dst_addr, alias_addr, call_id, NO_DEST_PORT, call_id, LINK_PPTP); } Index: alias_local.h === RCS file: /home/ncvs/src/lib/libalias/alias_local.h,v retrieving revision 1.16 diff -u -p -r1.16 alias_local.h --- alias_local.h 2000/07/26 23:15:46
Intel Developer Update Magazine
Title: Intel September Issue Dear Intel Developer Update Subscriber, News from last months Intel® Developer Forum Conference continues to emerge. This months issue of IDU gives you a closer look. Intel® XScale Microarchitecture Serves Up Breakthrough I/O cover story Breakthrough I/O performance for networking applications becomes a reality with the announcement of the Intel® 80310 I/O processor chipset, the first product with Intel® XScale microarchitecture. http://developer.intel.com/update/contents/ac10001.htm Remote Access to Pre-Release IA-64 Systems -- Intel® Early Access Services offers software developers cost-free, maintenance-free, high-speed Internet access to fully functional, secure IA-64 systems. http://developer.intel.com/update/contents/sw10001.htm Accelerating Internet Expansion to Wireless Clients -- The Intel® Personal Internet Client Architecture separates hardware and software design environments so applications can be developed independently, eliminating serial development and speeding time-to-market. http://developer.intel.com/update/contents/ac10002.htm Deskpro IAPC Design Example -- Compaqs Deskpro EN series demonstrates a variety of ways OEMs can use S3 technology to differentiate their products from other platforms. http://developer.intel.com/update/contents/dt10001.htm Real-Time 1394b Data Transfer for Consumer Electronics - By choosing the right implementation of IEEE 1394b, manufacturers can achieve maximum throughput for the lowest cost and still provide significant product differentiation. http://developer.intel.com/update/contents/it10001.htm PXE Manageability Technology for EFI -- PXE (Preboot Execution Environment) provides standardized remote installation and manageability for enterprise network clients, and now its available for EFI (Extended Firmware Interface). http://developer.intel.com/update/contents/it10004.htm For details about ongoing developments, visit Intel Developer Update your monthly conference between the Conferences. Regards, The Editorial Staff Intel Developer Update Magazine == Know someone whod be interested in the information Intel Developer Update provides? Forward them this section. Anyone can receive a free subscription. Benefits include monthly email reminders, alerts on major news from Intel, and more. To subscribe, your colleague can link to our subscription form from here or go through the magazines home page at http://developer.intel.com/update. In the left navigation bar, they should click on Reader Services then click on "Subscribe Now." If you dont want to continue receiving Intel Developer Update mailings, send an email to [EMAIL PROTECTED] with "unsubscribe" as subject of the message. *For information regarding Intel Corporation's trademarks and acknowledgments please go to http://developer.intel.com/sites/developer/tradmarx.htm.
Re: putting FreeBSD in an extended partition
On Tue, 26 Sep 2000, Mike Smith wrote: > I am wondering whether there is a good reason for not putting FreeBSD in a > DOS extended partition. > >>> > >>> Good luck booting it. > >> > >> Do you mean as long as I can boot it, the kernel itself has no problem > >> with being putting into a DOS extended partition? > > > > Loader(8) can't grok it and the kernel can't mount it as root. > > Actually, that's not entirely true. > > The problem with booting is that you cannot mark an extended partition > entry as 'active' (without some nasty, nonstandard hacks). > > If that were possible, it would be trivial to improve the loader to deal > with that case. The kernel most certainly can mount an extended partition > as root, however. I know this is a minor subject. But Why Linux can be put in an extended partition while FreeBSD cannot? I can not find anywhere (e.g. kern/subr_diskslice.c) in the kernel that prevents this and I know LILO can boot FreeBSD. If it is the problem of booteasy, then we can use other boot loader. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: putting FreeBSD in an extended partition
Zhiui Zhang wrote: > On Tue, 26 Sep 2000, Mike Smith wrote: > > If that were possible, it would be trivial to improve the loader to deal > > with that case. The kernel most certainly can mount an extended partition > > as root, however. > > I know this is a minor subject. But Why Linux can be put in an extended > partition while FreeBSD cannot? I can not find anywhere (e.g. > kern/subr_diskslice.c) in the kernel that prevents this and I know LILO > can boot FreeBSD. If it is the problem of booteasy, then we can use other > boot loader. The standard bootblocks (ie. boot2) don't support this at present, nor do our tools like fdisk(8) and the equivalent part of sysinstall; so there's a reasonable amount of work needed to make booting from extended partitions a properly-supported feature. I'll most likely be adding this support in the next few months, though. It hasn't been a priority item as there's been little interest till recently. It should be fairly easy to hack boot2 to get this working in your particular case, if you have the time and inclination. -- Robert Nordier [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
system hangs with BUS Reset
I am debugging a program that does a lot of disk I/O and the system hangs briefly with the some repeated messages that looks like: (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x88 (da0:ahc0:0:0:0): BDR message in message buffer (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x89 (da0:ahc0:0:0:0): no longer in timeout, status= 34b ahc0: Issued Channel A Bus Reset. 2SCBs aborted. What should I do now? The following is my dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #0: Tue Sep 26 01:34:11 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SUNYFS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 134205440 (131060K bytes) avail memory = 126341120 (123380K bytes) Preloaded elf kernel "kernel" at 0xc0419000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR chip1: port 0xe800-0xe80f at device 4.3 on pci0 ahc0: port 0xd000-0xd0ff mem 0xe300-0xe3000fff irq 10 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs dc0: port 0xb800-0xb8ff mem 0xe280-0xe28000ff irq 11 at device 10.0 on pci0 dc0: Ethernet address: 00:a0:cc:e4:b7:14 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) WARNING: / was not properly dismounted Any help is appreciated. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: system hangs with BUS Reset
Hello, first off, you should ask in freebsd-questions or freebsd-scsi second this is a typical scsi problem. To solve: - check cables - check termination and if the problem still exists, check again. I speak from my own expierence, since I had this kind of problems one year, cos I didn't see that there were two jumpers on the disc to set the termination :-( Greetings Andreas On Wed, 27 Sep 2000, Zhiui Zhang wrote: > > I am debugging a program that does a lot of disk I/O and the system hangs > briefly with the some repeated messages that looks like: > > (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x88 > (da0:ahc0:0:0:0): BDR message in message buffer > (da0:ahc0:0:0:0): SCB 0x0 - Timed out in Data-in phase, SEQADDR==0x89 > (da0:ahc0:0:0:0): no longer in timeout, status= 34b > ahc0: Issued Channel A Bus Reset. 2SCBs aborted. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Anybody know the OS in the Maxtor MAXAttach products?
One of the comments on the side is: "Caching file system with Soft Update technology". Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. Just curious. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know the OS in the Maxtor MAXAttach products?
> > One of the comments on the side is: > > "Caching file system with Soft Update technology". > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. Last time I looked (a while back) they were using a patched-up FreeBSD 3.x variant. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know the OS in the Maxtor MAXAttach products?
> > > One of the comments on the side is: > > "Caching file system with Soft Update technology". > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. It is. This product is based on FreeBSD 3.2 if I'm not mistaken. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know the OS in the Maxtor MAXAttach products?
* Jordan Hubbard <[EMAIL PROTECTED]> [000927 16:12] wrote: > > > > > > One of the comments on the side is: > > > > "Caching file system with Soft Update technology". > > > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > It is. This product is based on FreeBSD 3.2 if I'm not mistaken. Several other companies are using FreeBSD for thier all-in-one fileserver appliances, afaik Quantum as well. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know the OS in the Maxtor MAXAttach products?
> > Several other companies are using FreeBSD for thier all-in-one > fileserver appliances, afaik Quantum as well. > Connexus/FasTraak (http://www.traakan.com) uses large chunks of various FreeBSD internals- namely the tcp stack. Their own NFS/SFS-journalling filesystem and driver model. FYI/FYA. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know the OS in the Maxtor MAXAttach products?
On Wednesday, 27 September 2000 at 15:31:47 -0700, Jaye Mathisen wrote: > One of the comments on the side is: > > "Caching file system with Soft Update technology". > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > Just curious. Maxtor have done a storage box with a modified FreeBSD, including Samba in the kernel. I don't know the name, but IIRC it's a small purple box with a couple of IDE boxes. I've heard that, for reasons that don't directly relate to FreeBSD, Maxtor isn't overly happy with the results, and that the next generation box probably won't run FreeBSD. There has even been talk that it'll be running Microsoft instead. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody know the OS in the Maxtor MAXAttach products?
* Greg Lehey <[EMAIL PROTECTED]> [000927 17:40] wrote: > On Wednesday, 27 September 2000 at 15:31:47 -0700, Jaye Mathisen wrote: > > One of the comments on the side is: > > > > "Caching file system with Soft Update technology". > > > > Sounds vaguely BSD'ish. Maybe even FreeBSD'ish. > > > > Just curious. > > Maxtor have done a storage box with a modified FreeBSD, including > Samba in the kernel. I don't know the name, but IIRC it's a small > purple box with a couple of IDE boxes. > > I've heard that, for reasons that don't directly relate to FreeBSD, > Maxtor isn't overly happy with the results, and that the next > generation box probably won't run FreeBSD. There has even been talk > that it'll be running Microsoft instead. That's upsetting, is there any reason they haven't tried to contact our developer base to resolve these issues, or is MicroSoft just twisting arms over there? -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
nfs v2
hi, with 4.1: there seems to be a problem with nfs2 mounts to non freebsd hosts: mainly, the special files - eg /dev/null - show up as something like 0 crw-r--r-- 1 root wheel0, 0x0022 Sep 28 09:29 /mnt/tmp/null it's ok if the exporting os is freebsd, but so far: netapp, procom, bsdi all show up to freebsd as 0, 0x0022! btw, the problem is not with ls, loo> date > /mnt/tmp/null /mnt/tmp/null: Device not configured. loo> needless to say, this is screwing up my diskless project. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message