Summary of my experiences for the Archives: - ES2B configures the aliased address just fine in the extended scripts using eth0_ALIAS0=64.21.224.241. - ifconfig doesn't show alias'd address, but "ip addr" does show it - The extended scripts do not open any ports or protocols for the alias address automatically so you won't be able to ping it or pass any traffic unless you explicitly open the ports using the network.conf, such as EXTERN_UDP_PORT0="12.11.155.254/32 500 64.21.224.241"
So in the end, everything was working as it should, it just took me a little while to figure out what was REALLY happening. Thanks for all the help Charles! - Todd > -----Original Message----- > From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 24, 2001 11:57 AM > To: Todd Pearsall; Linux Router Project > Subject: Re: [Leaf-user] Eigerstein2Beta IP Alias > > > > Charles, you were right on with ifconfig not showing the alias > addresses, > > but ip addr does. > > > > ip addr results > > 7: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > > link/ether 00:40:33:37:21 brd ff:ff:ff:ff:ff:ff > > inet 64.21.224.240/26 brd 64.21.224.255 scope global eth0 > > inet 64.21.224.241/26 brd 64.21.224.255 scope global > secondary eth0:1 > > > > Do I need to play with any firewall rules to be able to ping the new > > address? I'm using ES2B so it's kernel 2.2.16. There isn't an > ip_alias.o > > modules included. > > You may need to allow ICMP packets through the firewall for your secondary > IP(s) to get them to ping...I don't remember if this is enabled > by default, > but I don't think so. > > > Should I move to the dachstein normal-ipsec kernel? > > Probably a good idea. > > Charles Steinkuehler > http://lrp.steinkuehler.net > http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) > > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
