Hi Vivek: You might want to contact a Linux expert to see if there is a way to get the interface name configured the way you want.
I took a look at the man page for "ifconfig" and it gives me the impression that it is typically called at boot time to configure the various interfaces used by Linux. It wouldn't surprise me if the boot code turns out to read a configuration file that contains all of the interface information and then calls "ifconfig" to get things set up correctly. If so, you might be able to edit this file to change the interface names to things that are more to your liking. (Of course, I could be totally wrong about this, too ...) Regards, Al -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 14, 2007 3:03 AM To: Stephens, Allan; [EMAIL PROTECTED] Cc: [email protected] Subject: RE: [tipc-discussion] Error message "unable to enable bearer" onLinux TIPC Hi Al, Thanks for the response. Ifconfig displays the interface name as eth0 indeed and I am a able to enable a bearer with that interface name only. In VxWorks we are able to configure the interface name via bootargs but this does not work for a embedded Linux board. Regards, -Vivek -----Original Message----- From: Stephens, Allan [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 8:42 PM To: Vivek Alexander (WT01 - Embedded & Product Engineering); [EMAIL PROTECTED] Cc: [email protected] Subject: RE: [tipc-discussion] Error message "unable to enable bearer" onLinux TIPC Hi Vivek: TIPC should be able to utilize the Ethernet interfaces listed via "ifconfig". Most Linux systems seem to be configured by default with interface names like "eth0" and "eth1", but I think other names could also be used (like "fei0" and "motsecc0"); you may have to do some non-standard configuration of your Linux system to allow this though ... If "ifconfig" lists an interface name that TIPC can't attach to, be sure to let us know; that sort of behavior would appear to be a bug. Regards, Al -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, August 10, 2007 4:33 AM To: [EMAIL PROTECTED] Cc: [email protected] Subject: Re: [tipc-discussion] Error message "unable to enable bearer" onLinux TIPC Hey Randy, Thanks for the reply. I tried eth0 and it worked. But probably it does not have anything to do with the name length cos fei0 also does not work. Looks like Linux does not understand any other interface names other than eth. Cheers, -Vivek PS:I'm working on Linux kernel version 2.6.21 and TIPC 1.7.3. -----Original Message----- From: Randy Macleod [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 9:44 AM To: Vivek Alexander (WT01 - Embedded & Product Engineering) Subject: Re: [tipc-discussion] Error message "unable to enable bearer" on Linux TIPC > [EMAIL PROTECTED]:/usr/sbin> tipc-config -a=1.1.2 -be=eth:mottsec0 unable > to enable bearer [EMAIL PROTECTED]:/usr/sbin> tipc-config -addr node > address: <1.1.2> [EMAIL PROTECTED]:/usr/sbin> tipc-config -b > Bearers: > No active bearers > > Any ideas what may be going wrong. Just guessing but perhaps the mottsec0 device name is too long. Can you change the name to 4 characters like eth0. The code is here: http://lxr.linux.no/source/net/tipc/bearer.c#L473 What version of tipc/linux are you using? Check the output of # dmesg. -- // Randy ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
