search for: macaddr

Was in the process of upgrading a 7960 to SIP and in advertently applied a skinny image (P003G302.bin), now no matter what i put in OS79XX.TXT and OS7960.TXT it simply wont upgrade. The phone is pulling down OS79XX.TXT from my TFTP server but then goes on to repetedly ask for SEP<MACaddr>.cnf. Help!! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050525/74c1b48f/attachment.htm

...ipt __P((fsm *, char *)); /* Run an up/down script */ +static void bcp_script_done __P((void *)); + +/* + * Lengths of configuration options. + */ +#define CILEN_VOID 2 +#define CILEN_BRIDGELINEID 4 +#define CILEN_MACSUPPORT 3 +#define CILEN_TINYGRAM 3 +#define CILEN_LANID 3 +#define CILEN_MACADDR 8 +#define CILEN_SPANTREE 3 +#define CILEN_IEEE_802_TAGGED_FRAME 3 +#define CILEN_MGMT_INLINE 2 + +#define CODENAME(x) ((x) == CONFACK ? "ACK" : \ + (x) == CONFNAK ? "NAK" : "REJ") + +/* + * This state variable is used to ensure that we don't + * run...

I see my problem.? I mis-read what nmcli con mod eth0 mac "02:67:15:00:81:0B" does.? It sets HWADDR; which interface to link to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit.? I cannot find a way to set MACADDR.? I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses.? Uboot uses various...

...egister.rb @@ -393,13 +393,18 @@ class HostRegister < Qmf::ConsoleHandler # if we have a match, then update the database and remove # the received data to avoid creating a dupe later @logger.info "Searching for existing record for: #{detail.macaddr.upcase} in host #{host_qmf.hostname}" - if detail.macaddr.upcase == nic.mac + # if detail.interface ~ /eth.*\..*/ || detail.interface ~ /vnet.*/ + if detail.interface =~ /eth\d+\.\d+/ || detail.interface =~ /vnet\d+/ + @logger.info "Don't manage #{detail.interface...

I see my problem.? I mis-read what nmcli con mod eth0 mac "02:67:15:00:81:0B" does.? It sets HWADDR; which interface to link to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit.? I cannot find a way to set MACADDR.? I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses.? Uboot uses various...

Robert Moskowitz wrote: > I see my problem.? I mis-read what > > nmcli con mod eth0 mac "02:67:15:00:81:0B" > > does.? It sets HWADDR; which interface to link to, not MACADDR, what MAC > address you want for your interface. > > So I have read the nmcli pages and googled a bit.? I cannot find a way > to set MACADDR.? I suppose I can set HWADDR then use sed to change it to > MACADDR, but this seems a real hack. > Do it in the ifcfg-*, and in /etc/udev/ru...

Dear Sir, I was trying to install bridge as we are installing scps gateway in our testbed.This requires us to install the bridge. Our Linux version is 2.4.18 ~3 and we are using redhat 7.2 Please let me know which is the bridge I should install and how to configure it. Before configuring the bridge what I should check in my configuration. Thanks for your time, Sincerely Rama ===== I hear

...if(sock >= 0) + { + ifr.ifr_addr.sa_family = AF_INET; + strncpy(ifr.ifr_name, ifname.c_str(), IFNAMSIZ - 1); + + if(!ioctl(sock, SIOCGIFHWADDR, &ifr)) + { + char macaddr[256]; + + sprintf(macaddr, + "%.2X:%.2X:%.2X:%.2X:%.2X:%.2X", + (unsigned char )ifr.ifr_hwaddr.sa_data[0], + (unsigned char )ifr.ifr_hwaddr.sa_data[1], +...

...x af9de73..1a71b75 100644 --- a/net.c +++ b/net.c @@ -2103,7 +2103,7 @@ int net_client_init(Monitor *mon, const char *device, const char *p) } if (!strcmp(device, "nic")) { static const char * const nic_params[] = { - "vlan", "name", "macaddr", "model", NULL + "vlan", "name", "macaddr", "model", "vectors", NULL }; NICInfo *nd; uint8_t *macaddr; @@ -2138,6 +2138,22 @@ int net_client_init(Monitor *mon, const char *device, const char *p)...

...x af9de73..1a71b75 100644 --- a/net.c +++ b/net.c @@ -2103,7 +2103,7 @@ int net_client_init(Monitor *mon, const char *device, const char *p) } if (!strcmp(device, "nic")) { static const char * const nic_params[] = { - "vlan", "name", "macaddr", "model", NULL + "vlan", "name", "macaddr", "model", "vectors", NULL }; NICInfo *nd; uint8_t *macaddr; @@ -2138,6 +2138,22 @@ int net_client_init(Monitor *mon, const char *device, const char *p)...

...egister.rb @@ -393,14 +393,13 @@ class HostRegister < Qmf::ConsoleHandler # if we have a match, then update the database and remove # the received data to avoid creating a dupe later @logger.info "Searching for existing record for: #{detail.macaddr.upcase} in host #{host_qmf.hostname}" - # if detail.interface ~ /eth.*\..*/ || detail.interface ~ /vnet.*/ - if detail.interface =~ /eth\d+\.\d+/ || detail.interface =~ /vnet\d+/ - @logger.info "Don't manage #{detail.interface.inspect}" + if detail.interface_name =~ /eth\d...

In looking at the code I realized that the last of the HAL depenencies were removed with this patch. So, I'm pushing an updated patch that contains none of the HAL code in it.

...error "has different MAC address than expected, ignoring" when the network tries to startup. I am testing this out on the puppet learning VM. Does anyone see anything wrong with my code: init.pp -------------------------- define basehost ($ipaddress, $gateway, $hostname, $environ, $macaddress) { file { ''hosts'': path => ''/etc/hosts'', ensure => ''present'', owner => ''root'', group => ''root'', mode => ''644'', con...

...eem to recall somewhat talking about this at Puppet Camp last week….. Generally my signing strategy is always to generate new certs and private keys on the puppetmaster, and install them on the client machine as part of the initial install (hopefully automated). Can I generate a cert based on the macaddress of the new machine? I tried this, and puppetca --generate made the certs and key without complaining. Presumably I can install these on my client machine. If so, would I then run puppetd with a the --fqdn argument, and give the mac address there? And what would the name of this machine be in...

...fw AllowTrcrt fw net ACCEPT fw net icmp 11 ACCEPT net fw icmp 11 Yet traceroute requests are not honoured coming into this box:- Jan 10 11:37:00 nwww kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC=<macaddr> SRC=82.x.x.x DST=212.x.x.x LEN=38 TOS=0x00 PREC=0x00 TTL=1 ID=40996 PROTO=UDP SPT=40971 DPT=33459 LEN=18 Jan 10 11:37:05 nwww kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC=<macaddr> SRC=82.x.x.x DST=212.x.x.x LEN=38 TOS=0x00 PREC=0x00 TTL=1 ID=40997 PROTO=UDP SPT=40971 DPT=33460 LEN=18...

...previously but that was like 20 or so installs > ago. I don't know the files you need. > > For this installation: > > /etc/sysconfig/ifcfg-eth0 > > NAME="eth0" > BOOTPROTO=none > GATEWAY=192.168.1.1 > NM_CONTROLLED=no > HWADDR=44:37:E6:53:1E:E2 > MACADDR="" > IPV6INIT=no > DEVICE=eth0 > NETMASK=255.255.255.0 > MTU="" > BROADCAST=192.168.1.255 > IPADDR=192.168.1.110 > NETWORK=192.168.1.0 > ONBOOT=yes > TYPE=Ethernet > > /etc/sysconfig/ifcfg-eth1 > > GATEWAY=192.168.1.1 > NAME="&quo...

...un 15 07:25:51 2002 +++ ./pxelinux.asm Wed Aug 14 10:05:00 2002 @@ -17,6 +17,11 @@ ; version; incorporated herein by reference. ; ; **************************************************************************** +; modified by Hans-Werner Jouy (hans-werner.jouy at hamburglb.de) to use +; the macaddr aus configfilename, only try full maccaddr, then vendor part +; (first 3 byte), then defaultfilename: dirty hack, USE AT YOUR OWN RISK +; but free or better try to integrate into stable release +; **************************************************************************** %define IS_PXELINUX 1...

From: Amos Kong <akong at redhat.com> In virtio-net guest driver, currently we write MAC address to pci config space byte by byte, this means that we have an intermediate step where mac is wrong. This patch introduced a new control command to set MAC address, it's atomic. VIRTIO_NET_F_CTRL_MAC_ADDR is a new feature bit for compatibility. "mac" field will be set to read-only

From: Amos Kong <akong at redhat.com> In virtio-net guest driver, currently we write MAC address to pci config space byte by byte, this means that we have an intermediate step where mac is wrong. This patch introduced a new control command to set MAC address, it's atomic. VIRTIO_NET_F_CTRL_MAC_ADDR is a new feature bit for compatibility. "mac" field will be set to read-only

...f we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from "vif" instead. Also, the vbd doesn''t have to be a file anymore, but can be a physical disk partition. Signed-off-by: Yunfeng Zhao <yunfeng.zhao@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r 38c7c25b3cb9...