IPs and stuff

2002 December 16
by darkness

Mixmaster is alive and well, and working. Checking out Freenet too. BTW, in the freenet.conf file, fproxy.bindAddress is now mainport.bindAddress IIRC. Not noted in their documentation as far as I could see, but I found it by searching around with Google.

Switched over most of the IPs in our office. To facilitate zone transfers between my internal and external views I had to assign an extra address to each name server, then use the transfer-source option in one of the views on each server. Then you modify the view without transfer-source to not match the IP you specified to transfer-source. Like this:

view "internal"
{
	match-client { ! 10.0.0.4; 10.0.0.0/8; 127.0.0.1; };

	...
};

view "external"
{
	transfer-source 10.0.0.3;
};

In the above example 10.0.0.3 was the additional IP added to the name server that was using the above configuration, and 10.0.0.4 was the IP added to the other name server.

When you’ve got more than two subnets on the same segment and you want ISC dhcpd to know about them/hand out IPs in them, you need to use the shared-network directive. Helpful hint.

I got my Cisco Aironet LMC-350 today. Oddly, I’m getting packet loss to my Orinoco RG-1000 which was sitting about five feet from the laptop. Not good? It worked fine with an LMC-340 I tested it with. I hope it’s just the lack of antenna… but the 340 didn’t have an antenna on it either. I’ll have to do some experiments. Maybe ad-hoc to another card will be OK. Maybe it’s the firmware, and some new security provisions that are fucking up with the Orinoco AP?

No Comments

Leave A Comment

Note: You can use basic XHTML in your comments. Your email address will never be published.

Subscribe to this comment feed via RSS