[9fans] connection via proxy
Hi guys, I've a problem with the internet connection,i don't know how to connect my fileserver via proxy server through the port 8080,somebody can help me??and explain to me the steps i hace to do.. thanks in advance to all of you... Armando.
Re: [9fans] connection via proxy
Not sure I understand, port 8080 is usually used to proxy http connections, plan9 uses several ports for its fileserver but HTTP is not one of them (well venti has a stats server but I only mention that to keep the pedants happy). what exactly are you trying to do? -Steve
Re: [9fans] plan9port lacks exportfs server
somehow it dawned on me that plan9port lacks an application to serve a local filesystem over 9P. Is this on purpose? Am I missing something fundamental that would allow for a moral equivalent of exportfs? I pull things in as they are needed. I have not needed to serve 9P. Adding u9fs sounds reasonable, but of course it is already in Unix-compilable form elsewhere. Russ
Re: [9fans] mounting stdin using 9pfuse
it appears that I'm missing something fundamental in how 9pfuse (the one written by Russ) works when it is given - as an address. The source looks like it should be simply using stdin for R/W instead of dialing out the connection first, but it doesn't really seem to work. Here's the simplest way of reproducing what I'm seeing: I don't know why your example doesn't work, but ramfs simply may not work with 9pfuse. I would try doing something a little more complicated, like dial tcp!sources.cs.bell-labs.com!9fs and then run 9pfuse - with that on standard input. 9fans is a fine list to ask about plan9port. Russ
[9fans] smtpd inserting nulls
i've been having a problem with nulls popping up in the middle of emails for some time. normally, this isn't something one would notice but imap4d makes nulls in email extra annoying by sending the client 4 reformattings of the same bogus message. i never did catch it red handed, but it finally be came obvious on (not exactly the first) inspection. the dot destuffing code didn't reduce the length of the line to account for the elided dot and thus added a null at the end of lines starting with a dot. (but only after the first 16k of the message.) fun times! because i was there, i also added protection against nulls in the actual data. there's a patch on sources. - erik
[9fans] DNS lookup problem
Hey guys, Recently I started serving dns from my cpu server, and I've just run into a problem connecting to gtalk which turns out to be caused by that. bitlbee queries _xmpp-client._tcp.gmail.com for srv records, and from linux I get: : nightingale ~; dig _xmpp-client._tcp.gmail.com srv @192.168.1.65 ;; Warning: Message parser reports malformed message packet. ; DiG 9.3.2-P2 _xmpp-client._tcp.gmail.com srv @192.168.1.65 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 40485 ;; flags: qr aa ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;_xmpp-client._tcp.gmail.com. IN SRV ;; Query time: 0 msec ;; SERVER: 192.168.1.65#53(192.168.1.65) ;; WHEN: Tue Oct 7 08:18:42 2008 ;; MSG SIZE rcvd: 372 I guess the malformed message packet is referring to the 4 authority/4 additional claim in the header followed by no actual records, but I don't really know the details of dns. It seems to work locally, though I'm not sure if it is using my router (I guess not, would expect it to use /net/dns): cpu% ndb/dnsquery _xmpp-client._tcp.gmail.com srv _xmpp-client._tcp.gmail.com srv 20 0 5222 talk1.l.google.com _xmpp-client._tcp.gmail.com srv 20 0 5222 talk2.l.google.com _xmpp-client._tcp.gmail.com srv 20 0 5222 talk3.l.google.com _xmpp-client._tcp.gmail.com srv 20 0 5222 talk4.l.google.com _xmpp-client._tcp.gmail.com srv 5 0 5222 talk.l.google.com -sqweek
Re: [9fans] plan9port lacks exportfs server
On Tue, Oct 7, 2008 at 12:24 AM, Russ Cox [EMAIL PROTECTED] wrote: Roman Shaposhnik wrote: somehow it dawned on me that plan9port lacks an application to serve a local filesystem over 9P. Is this on purpose? I pull things in as they are needed. I have not needed to serve 9P. This reminds me, I recently compiled aux/9pcon against p9p to test some connections (which was delightfully easy, only some minor rfork changes required). The result is at http://sqweek.dnsdojo.org/plan9/p9p-9pcon.c should anyone be interested. -sqweek
Re: [9fans] smtpd inserting nulls
On Mon, Oct 6, 2008 at 12:49 PM, erik quanstrom [EMAIL PROTECTED] wrote: i've been having a problem with nulls popping up in the middle of emails for some time. normally, this isn't something one would notice but imap4d makes nulls in email extra annoying by sending the client 4 reformattings of the same bogus message. i never did catch it red handed, but it finally be came obvious on (not exactly the first) inspection. the dot destuffing code didn't reduce the length of the line to account for the elided dot and thus added a null at the end of lines starting with a dot. (but only after the first 16k of the message.) fun times! because i was there, i also added protection against nulls in the actual data. there's a patch on sources. This is a great thing. I've been assuming that the rest of the world sent around bogus email, it never occured to me that the mta would be blowing it. Thanks for this, it's a big help ron
Re: [9fans] smtpd inserting nulls
On Mon Oct 6 20:47:42 EDT 2008, [EMAIL PROTECTED] wrote: This is a great thing. I've been assuming that the rest of the world sent around bogus email, it never occured to me that the mta would be blowing it. Thanks for this, it's a big help ron you're welcome! that bug had been driving me bats for about 15 months. (that'll be a lesson to you, boys and girls: never let 'em know you know anything about smtp. that goes double for imap.) btw, the nupas stuff is coming along. i have a couple users with ~2500 messages in their inboxes. now if i could just teach them where the delete button is. you may be interested in the nupas version of smtpd. i've added some spam control that's been pretty effective. the -E option demands a valid ehlo domain *or* authentication. this is good for imap users who can auth but feed us garbage ehlo strings. ☺ - erik
Re: [9fans] connection via proxy
You're after one of two things. 1) It mostly sounds like you want to send 9p requests to an existing server via an actual http proxy. If this is indeed what you're looking for, you're pretty much out of luck. No code or service exists to translate from 9p to/from http, which is what would be needed before you could do this. I suppose there's no theoretical reason such a mapping couldn't exist, but you would have to do the design and coding yourself. It would be a significant undertaking to do reasonably. 2) Instead, one could read your mail as saying you just need to use what you're describing as the http proxy port, 8080. In that case, you're okay: most servers which can listen on the network can accept an arbitrary port to listen on; see the 'listen' command in fossilcons(8), for example. For the rest, aux/trampoline in conjunction with listen(8) will do well. Sadly, I think you want option 1, which doesn't exist. Anthony
Re: [9fans] plan9port lacks exportfs server
Hi Russ! First of all -- thanks a lot for answering. On Mon, 2008-10-06 at 09:24 -0700, Russ Cox wrote: somehow it dawned on me that plan9port lacks an application to serve a local filesystem over 9P. Is this on purpose? Am I missing something fundamental that would allow for a moral equivalent of exportfs? I pull things in as they are needed. I have not needed to serve 9P. Adding u9fs sounds reasonable, but of course it is already in Unix-compilable form elsewhere. Of course, although the utility of plan9port as a one stop shop for everything Plan9 on UNIX platforms is quite significant. Hence the question -- would you be in favor of continue adding things as needed. And if so, what kind of of groundwork would you expect from the contributors? Thanks, Roman. P.S. I see that sqweek has the 9pcon and (not to overcommit myself ;-)) I also might be able to contribute things like u9fs and nfsserver.
Re: [9fans] mounting stdin using 9pfuse
On Mon, 2008-10-06 at 09:31 -0700, Russ Cox wrote: it appears that I'm missing something fundamental in how 9pfuse (the one written by Russ) works when it is given - as an address. The source looks like it should be simply using stdin for R/W instead of dialing out the connection first, but it doesn't really seem to work. Here's the simplest way of reproducing what I'm seeing: I don't know why your example doesn't work, but ramfs simply may not work with 9pfuse. Any particular reason for that? I'm asking simply because ramfs appears to be quite broken on my system. In fact, I can't make it work at all. Has it bitrotted? I would try doing something a little more complicated, like dial tcp!sources.cs.bell-labs.com!9fs and then run 9pfuse - with that on standard input. That, actually, seems to work fine. Although I'm about to give it more stress testing. Here's a question thought: by default 9pserve only listens on an AF_UNIX socket what would be the best way to connect it to the AF_INET one? Thanks, Roman.
[9fans] non working links - http://netlib.bell-labs.com
Hi all I am getting broken links on the netlib website. http://netlib.bell-labs.com/sys/doc/plumb.pdf The object /sys/doc/plumb.pdf does not exist on this server. ... fernan -- http://www.fernski.com
Re: [9fans] connection via proxy
Hello May be this is of your interest: http://www.r-36.net/htdialfs.tgz Other thing that could be of your interest is: http://sirviente.9grid.es/srv.rit the section about dealing with http proxy from a windws xp corporate workstation and a qemu plan9. hope this helps, gabi El 07/10/2008, a las 4:58, [EMAIL PROTECTED] escribió: You're after one of two things. 1) It mostly sounds like you want to send 9p requests to an existing server via an actual http proxy. If this is indeed what you're looking for, you're pretty much out of luck. No code or service exists to translate from 9p to/from http, which is what would be needed before you could do this. I suppose there's no theoretical reason such a mapping couldn't exist, but you would have to do the design and coding yourself. It would be a significant undertaking to do reasonably. 2) Instead, one could read your mail as saying you just need to use what you're describing as the http proxy port, 8080. In that case, you're okay: most servers which can listen on the network can accept an arbitrary port to listen on; see the 'listen' command in fossilcons(8), for example. For the rest, aux/trampoline in conjunction with listen(8) will do well. Sadly, I think you want option 1, which doesn't exist. Anthony
