Quick fill...
Mar. 28th, 2002 04:27 pmWell, there I was, just minding my own business, when my plate went from empty to near-overflow in no time flat. But I get ahead of myself.
This morning's telecon went well. The subject matter was not overly arcane, and the speakers were clearly audible. I did, however, become reacquainted with why I dislike doing two-hour telecons from my office: first, it's a pain to hold a receiver to one's ear for that period of time (I never did master the art of overly long conversations), and second, with one hand devoted to holding the receiver, that leaves one hand to write while holding the paper in place.
Yeah, I know... both "problems" are readily solved with a little ingenuity, or a little cash and even less ingenuity.
I tried to get confirmation from client M that they did, indeed have work for me, based on yesterday's conversation, but got no answer until later today. By that time, I'd already accepted work from client T and had been asked to do more work by client U. Eventually, M got back to me and now I have... a lot... of work due Monday, some more on Tuesday, and about 5 pages due mid-day tomorrow (and which I ought to get cracking on).
* * * I've been having trouble telneting and ftping into 'onegin'. A look at the firewall rules showed me why, and momentarily disconcerted me.
The rules that distracted me momentarily were the ones that allow udp access from some servers whose names were strange to me, until I realized that these were my DNS servers. Otherwise, the firewall rules basically block any and all incoming requests on the ports 0 through 1023 (which include telnet and ftp), so it really doesn't matter how I configure xinetd. Flushing the rules allows ftp and telnet sessions with no problems; restarting ipchains, however, gets me a slightly different set of rules, but the difference is stark, as the first rule says to accept all connections from anywhere to anywhere (kinda like not having any rules at all). So, it looks like I'm going to have to spend a little time refamiliarizing myself with ipchains and firewall rules, and soon.
Got to get back to work...
Cheers...
This morning's telecon went well. The subject matter was not overly arcane, and the speakers were clearly audible. I did, however, become reacquainted with why I dislike doing two-hour telecons from my office: first, it's a pain to hold a receiver to one's ear for that period of time (I never did master the art of overly long conversations), and second, with one hand devoted to holding the receiver, that leaves one hand to write while holding the paper in place.
Yeah, I know... both "problems" are readily solved with a little ingenuity, or a little cash and even less ingenuity.
I tried to get confirmation from client M that they did, indeed have work for me, based on yesterday's conversation, but got no answer until later today. By that time, I'd already accepted work from client T and had been asked to do more work by client U. Eventually, M got back to me and now I have... a lot... of work due Monday, some more on Tuesday, and about 5 pages due mid-day tomorrow (and which I ought to get cracking on).
The rules that distracted me momentarily were the ones that allow udp access from some servers whose names were strange to me, until I realized that these were my DNS servers. Otherwise, the firewall rules basically block any and all incoming requests on the ports 0 through 1023 (which include telnet and ftp), so it really doesn't matter how I configure xinetd. Flushing the rules allows ftp and telnet sessions with no problems; restarting ipchains, however, gets me a slightly different set of rules, but the difference is stark, as the first rule says to accept all connections from anywhere to anywhere (kinda like not having any rules at all). So, it looks like I'm going to have to spend a little time refamiliarizing myself with ipchains and firewall rules, and soon.
Got to get back to work...
Cheers...