On Wed, 16 Mar 2005 [EMAIL PROTECTED] wrote:
On Tue, 15 Mar 2005 [EMAIL PROTECTED] wrote:
but didn't think this was doable ...Why not: ifconfig fxp0 inet 200.46.204.2/24 ifconfig fxp0 inet 200.46.208.2/24 alias ifconfig fxp0 inet 200.46.204.10/32 alias ifconfig fxp0 inet 200.46.204.5/32 alias ifconfig fxp0 inet 200.46.208.254/32 alias ifconfig fxp0 inet 200.46.208.251/32 alias ifconfig fxp0 inet 200.46.208.244/32 alias so on ? With the only fxp0 interfaceGreat ... I have a new server going down next week that I'll try out the ng_fec stuff with, and the above, then ... thanks ...
If addresses and not bandwidth is reason, no need for ng_fec.
'k, I don't think bandwidth is an issue ... just started to use mrtg on the switch, to see what is going on ... I might go with ng_fec anyway, so that both ports are used semi-balanced, since I do have them attached ...
Since the servers are remove, can I configure one interface as a fec device, assign its IPs over to it, then "add" the second device?
Also, where do you put your start up? SAme as a regular interface, just throw it into a startup.if_fec file or something like that?
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
