RV042 relay agent

Hello

Is it possible to configure RV042 as a DHCP relay agent? I use two of these routers with G2G configuration. In one place, I have W2k3 DHCP server and in another place, I want to use this server.

Thanks for the reply.

Karol

Hi Karol,

UnknownHero is correct. The RV042 is now managed by the Cisco Small Business support community.

You must create an account to post here.

Tags: Linksys Routers

Similar Questions

Get some VLAN voice to work on 5548P

Hello

I was wondering if there is a way to accomplish the following. I want the passage to the tag the traffic on its own based on the YES Table and pass it up to the Sonicwall (DHCP server/router) without going through the phone itself do the marking. Is this possible? Currently, the installation so I put manually the VLAN ID on the phone itself, but these phones can work anywhere there is a sense of internet connection if I manually add the tag VLAN, the phone will not work outside of the corporate network.

Thank you

If your phone supports LLDP-MED, you can install the switch with a VLAN voice. This wiki covers the implementation of the VLAN voice.

http://en.community.Dell.com/TechCenter/networking/w/wiki/configuring-Dell-PowerConnect-55xx-series-switch-voice-VLAN.aspx

Do not have to configure phones that you configure LLDP-MED. The VLAN ID information are passed with LLDP-MED configured on the VoIP phone using the LLDP-MED mechanism. By this method, the voice from the VoIP phone data are tagged with the VLAN ID exchanged and the usual traffic would go to the PVID.

Here is the link to the user guide. LLDP-MED configuration begins at page 540.

FTP://FTP.Dell.com/ Manuals /Cccomplis /powerconnect-5524_User%27s%20Guide_en-us.pdf

Once the phone is in the voice VLAN it can still receive an IP address by the DHCP server using the DHCP relay. The switch acts as a DHCP relay agent that listens for DHCP messages,

and passes between DHCP servers and clients, residing in IP or VLAN different subnets.

Relay DHCP and espionage begins on page 563 of the user guide.

I hope this helps.

DHCP Snooping

Scenerio:

As part of a modernization project of tech in a big campus and because of several problems caused by users (l) connect the routers on the network and causing DHCP issues, I'm looking to turn on DHCP snooping. During the tech switches access update will be updated first and then the kernel. The new access switches are 4510R + E/Sup7, running the latest IOS XE base license and just passing through. New carrots are 6509 Sup 720's configured as a cluster VSS, manage all routing for VIRTUAL local area networks and have the statements of support IP. The DHCP server which takes care of all the VLAN is a Windows 2008 server that is directly connected to the base.

I also read all the info I could find on DHCP snooping, but I'm still a little fuzzy on if it changes the way that the DHCP server handles requests.

Issues related to the:
- Because the access switches pass only, they only need monitoring DHCP enabled (in the world and on VIRTUAL local area networks) and their uplinks to the core set as being approved, right? In particular, they only declarations of support IP or Layer-3 interfaces for all of their VIRTUAL local networks, right?
- While I understand that DHCP snooping will be ineffective if it is not lit on the kernel, there is no reason I can't deploy it first to the access layer without touching the basic configurations to avoid large amounts of documents of change control, right? Then, when the kernel is put at level and DHCP snooping successfully activated that will work.
- I got that on the layer to access the switches uplink to the core are approved, but I'm not 100% on the question of whether the same interfaces are approved on the carrots. I don't think but want to be sure. Carrots of course trust the real interface on that server DHCP is plugged
- The most confusing part is all the stuff from the Option-82. As near as I can tell its option for the server to use the information from the Option-82. I think that if all I do is enable DHCP snooping on worldwide and on the right VIRTUAL LANs the DHCP relay between the core and the DHCP server will continue to work as it is today, is that correct?
Is there really this traps or in my case I really just need to turn it on in the world and by vlan, trust the uplinks on the access switches and the DHCP server on the kernel interface and call it a day?

Thank you

Nathan Spitzer

SR Network Communications analyst.

Lockheed Martin

Hello Nathan,.
```
Given that the access switches are only switching, they only need DHCP snooping turned on (both globally and on the VLANS) and their uplinks to the core set as trusted, right?
```
Fix.
```
In particular they dont need IP helper statements or layer-3 interfaces for all of their VLANS, right?
```
Fix. The statement of support ip address would only be necessary if switches performed routing inter - VLAN and the DHCP server is located in a VLAN different.
```
While I understand that DHCP snooping will only be marginally effective if it is not turned on on the core, there is no reason I cannot deploy it first at the access layer without touching the core configurations to avoid large amounts of change-control paperwork, right? Then when the core is upgraded and DHCP snooping properly enabled it will work. 
```
To my knowledge, the opposite is true. DHCP Snooping is a service of access protection layer - is it not in the core of the network. It has nothing to protect in the kernel once DHCP messages have beein properly disinfected at the edge of the network. For some inexplicable reason, many people think that the DHCP Snooping should be enabled on the network. The fact is that the DHCP Snooping protects against
- DHCP messages are sent to ineligible devices
- Ineligible devices posing as DHCP servers
From this it naturally follows that it is the limit of the network, or the layer of access, where such protection is the most effective. So in your case, I believe that the activation of the DHCP Snooping only on the access layer is actually what you want to do.
```
I got that on the access layer switches the uplinks to the core are trusted, but I am not 100% on whether the same interfaces are trusted on the cores. I dont think so but want to be sure. Of cource the cores do trust the actual interface the DHCP server is plugged in on
```
If you enable the DHCP Snooping on the basic features and uplink between the access switches and core would have to be configured as confidence both on the basic switches and access. Otherwise, the base ports would pass DHCP messages received from customers because the access layer switches running DHCP Snooping insert DHCP Option 82 in the DHCP messages sanitized and ports untrustred delete all DHCP messages including 82 of the present Option.

2960 Configuration Guide to

http://www.Cisco.com/en/us/docs/switches/LAN/catalyst2960/software/release/12.2_55_se/configuration/guide/swdhcp82.html#wp1078853

The switch removes a DHCP packet when one of these situations occurs:
- Comes from a packet to a DHCP server, for example a DHCPOFFER, DHCPACK, DHCPNAK or DHCPLEASEQUERY package, outside the network or firewall.
- A packet is received on an interface that is not reliable, and do not match the source MAC address and hardware address of the DHCP client.
The switch receives a message DHCPRELEASE or DHCPDECLINE with a MAC address in the DHCP snooping database binding, but the information in the database of linking interface does not correspond to the interface on which the message was received.
A DHCP relay agent sends a DHCP packet that includes a relay agent IP address which is not 0.0.0.0 or relay agent transmits a packet that includes information of option-82 to an untrusted port.

As I have indicated, however, I personally discourage running DHCP Snooping on the basic devices - I see no reason for this. Please correct if I am wrong!

The most confusing part is all the Option-82 stuff. As near as I can tell its optional for the server to use the Option-82 information. I believe that if all I do is turn DHCP snooping on globally and on the right VLANS the DHCP relaying between the core and the DHCP server will continue working just like it is today, is that correct?

LOL, my favorite on the DHCP Snooping things is the Option 82 interesting how much this topic brings confusion...

The Option 82 was created to provide DHCP relay agent the ability to identify itself and the customer who sent the original message from DHCP unmodified. The DHCP server can then use this information to perform certain policies of customer trust. The format of the Option 82 is not strictly specified, only its basic structure is fixed. You can read more on this and the whole reason to be in the RFC 3046. One of the key points to remember here, however, is that the DHCP server may or may not recognize the Option 82, but apart from that, to copy the value of the Option 82A received in the message to a DHCP client for all its replies sent to this client.

DHCP Snooping uses the Option 82 differently. He didn't expect and doesn't require that the DHCP Server includes the Option of 82 or manages a special way. The Option 82 is inserted by switches access performing DHCP Snooping and it contains two important parts:

The Circuit ID that identifies the port to which the client is connected (VLAN and the location of the physical port in a switch)
The remote ID that identifies the access switch to which the client is connected (by the MAC address of the switch)

See http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_55_se/configuration/guide/swdhcp82.html#wp1105589

Now, when an access switch performing DHCP Snooping receives a message from DHCP client on an untrusted port, this will happen:

The switch will insert the 82 Option in the message of the DHCP client. The Option 82 will identify the specific switch and the port to which the client is attached
The switch will forward the DHCP message according to its MAC address of destination (i.e. in a completely normal way)
The server receives the DHCP message containing the Option 82. It is not relevant for DHCP Snooping if the server takes into account the value of the Option 82. However, when the server replies, it will insert the original value of the Option of 82 to the answer.
Access switch will finally receive the DHCP response. Looking at the Option 82, he knows exactly in which port is the message transmitted to the customer - and only the customer - even if the answer was broadcast!

Note that the Option 82 contributes enormously to identify exactly the access switch and its port where the client is attached. If other switches with DHCP Snooping has received this DHCP message (in reason of the flood or address broadcast requested by the client), they would pass this message because they understand once glancing at the 82 Option that the customer is attached elsewhere. The 82 Option allowing to ensure DHCP communication between a particular client and the DHCP server doesn't leak not to other customers.

There is a hunt for witches, associated with the Option 82. A switch run DHCP Snooping inserts the Option 82 messages DHCP clients. However, each DHCP message contains a field named GIADDR where the IP address of the relay agent is registered, where the DHCP message was relayed. Clearly, when a DHCP message goes through a switch DHCP Snooping, it is not relayed (drawn from one VLAN and rerouted to another), so an access switch does not change the GIADDR that remains set to 0.0.0.0. However, at least the implementation of server DHCP Cisco IOS performs a validation on a test received DHCP messages and it drops DHCP messages containing the Option 82, but which the GIADDR field is set to 0.0.0.0 (i.e. unitialized). This can be seen in the output of the debug ip dhcp server packet :

Router# debug ip dhcp server packet

*Sep 9 01:59:40: DHCPD: inconsistent relay information.

*Sep 9 01:59:40: DHCPD: relay information option exists, but giaddr is zero

Under normal circumstances, such a mental health check makes sense - how is it that a DHCP message contains the Option 82 (i.e. the Relay Agent Information Option DHCP) when there is no DHCP relay identified in the GIADDR? However, with DHCP Snooping on the access layer switches, DHCP messages are normal and expected. Therefore, it is essential to disable this check of mental health on the Cisco box that is running the DHCP server configuration using global ip dhcp relay confidence all information or only is selected routed (i.e. L3) interfaces with command level interface ip dhcp relay reliable information.

To summarize:

The 82 Option is A Good Thing (TM) because it allows to deliver DHCP messages only to the client for which they are intended. Any suggestions to disable the insertion of the Option 82 on access DHCP Snooping Switches are useless 82 Option is inserted by DHCP Snooping Switches in DHCP messages by default - no additional configuration is necessary.
Through the easiest way - when you deploy DHCP Snooping, does not initially change anything about the Option 82. Make sure that your customers can receive their config IP via DHCP. If yes then there is nothing to resolve. If not, go further.
If you run a DHCP server on a Device IOS base (router, switch), you may need to use the command ip dhcp relay information confidence-everything (global config) or ip dhcp relay reliable information (level interface) to allow the DHCP messages with the Add Option 82 and unitialized field GIADDR to be accepted. These commands are required only on the device where the DHCP server is running, not on the access layer switches. You may want to first perform debugging as I suggested previously, and only if you see that packets are dropped, add these commands to the configuration.
I don't know if these commands should be added also to a DHCP relay function efficient switch - I can check that tomorrow in a laboratory.
If you are using another DHCP server you have to try experimentally whether happy with the DHCP messages with 82 Option present and unitialized GIADDR field

Sorry for the long answer... I hope that I do not bore you to death. We invite you to ask for more! I'll try to be more concise next time

Best regards

Peter

WLC - server DHCP (Override) and

Hi guys,.

A little confused. If I want my wireless clients to a DHCP address on my business DHCP servers, I need to click the Overrides button, for the WLC to act as a relay agent or the docs say that this happens by default?

Can someone pls confirm, because it is a little confusing. The files help mentioned below also?

Thx a lot indeed.

Ken

Server DHCP (Override)

----------------------

When the substitution is selected, you can enter the IP address of your DHCP server. It is a required field for some configurations of WLAN. There are three valid configurations:

-DHCP Server override on a valid DHCP and DHCP address assignment requested server IP address: requires that all WLAN clients obtain an IP address from the DHCP server.

-DHCP Server override on a valid DHCP and DHCP address unnecessary assignment server IP address: allows all clients WLAN get an IP address from the DHCP server or use a static IP address.

-DHCP Server OFF Overrides: guests WLAN using the DHCP setting in the Management Interface, not the static address of the Forces.

Hi Ken,

Your WLC default is DHCP relay, you do not need to override.

The WLAN configuration, put you in an interface. If you check this configuration of the interface, you will see that it points to a DHCP server. This is where your WLC relays to wireless clients.

If you wish to override this setting and to send your customers to a different DHCP server instead, you then click DHCP replace in the WIFI config and enter another IP DHCP address.

HTH

Jerome

DHCP with VPN

I work with an ASA 5505. I configured a connection IPsec remote access profile. This profile is set to give customers a virtual ip address via DHCP as shown in this example configuration:

http://www.Cisco.com/en/us/products/ps6120/products_configuration_example09186a0080a66bc6.shtml

When the DHCP request is sent from the ASA to the DHCP server, the hostname in the query is set to the name of the IPsec connection profile and a number. Is it possible to have the host name, set the host name of the client who initiated the connection?

The ASA takes by receiving a host name in a request for Config Mode IKE?

Thank you

Mark

Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for IPV4 address!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for IPV4 net mask!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for DNS server address!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for WINS server address!

    Aug 11 07:06:27 [IKEv1]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Received unsupported transaction mode attribute: 5

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Banner!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Save PW setting!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Default Domain Name!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Split Tunnel List!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Split DNS!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for PFS setting!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Client Browser Proxy Setting!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for backup ip-sec peer list!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Client Smartcard Removal Disconnect Setting!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for Application Version!

    Aug 11 07:06:27 [IKEv1]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Client Type: WinNT  Client Application Version: 5.0.05.0290

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for FWTYPE!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, MODE_CFG: Received request for DHCP hostname for DDNS is: PD1-STATIC-WXP!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Obtained IP addr (192.168.1.4) prior to initiating Mode Cfg (XAuth enabled)

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Sending subnet mask (255.255.255.0) to remote client

    Aug 11 07:06:27 [IKEv1]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Assigned private IP address 192.168.1.4 to remote user

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, constructing blank hash payload

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Send Client Browser Proxy Attributes!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Browser Proxy set to No-Modify. Browser Proxy data will NOT be included in the mode-cfg reply

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, Send Cisco Smartcard Removal Disconnect enable!!

    Aug 11 07:06:27 [IKEv1 DEBUG]: Group = IPSEC-Test, Username = cisco, IP = 20.20.20.1, constructing qm hash payload

    Aug 11 07:06:27 [IKEv1]: IP = 20.20.20.1, IKE_DECODE SENDING Message (msgid=fa774da7) with payloads : HDR + HASH (8) + ATTR (14) + NONE (0) total length : 206

Version above. The Tunnel-Group and the host name. Also make sure you have "Register this connection in DNS" setting checked under Advanced properties of WILL. It comes default Cisco VPN client. If StrongSwan has one GOES then it must follow the rules in the Windows API, this parameter expected to be here than if she one WILL, in the case where it is a sort of driver setup miniport (shim), she has no one will

Here is the package:

Frame 9 (590 bytes on wire, 590 bytes captured)

    Ethernet II, Src: Cisco_d7:74:dd (00:25:45:d7:74:dd), Dst: Vmware_ad:75:1b (00:50:56:ad:75:1b)

    Internet Protocol, Src: 11.12.12.5 (11.12.12.5), Dst: 11.12.12.25 (11.12.12.25)

    User Datagram Protocol, Src Port: bootps (67), Dst Port: bootps (67)

    Bootstrap Protocol

        Message type: Boot Request (1)

        Hardware type: Ethernet

        Hardware address length: 6

        Hops: 0

        Transaction ID: 0x011b5678

        Seconds elapsed: 7

        Bootp flags: 0x0000 (Unicast)

            0... .... .... .... = Broadcast flag: Unicast

            .000 0000 0000 0000 = Reserved flags: 0x0000

        Client IP address: 0.0.0.0 (0.0.0.0)

        Your (client) IP address: 0.0.0.0 (0.0.0.0)

        Next server IP address: 0.0.0.0 (0.0.0.0)

        Relay agent IP address: 11.12.12.5 (11.12.12.5)

        Client MAC address: Cisco_d7:74:dd (00:25:45:d7:74:dd)

        Client hardware address padding: 00000000000000000000

        Server host name not given

        Boot file name not given

        Magic cookie: (OK)

        Option: (t=53,l=1) DHCP Message Type = DHCP Discover

            Option: (53) DHCP Message Type

            Length: 1

            Value: 01

        Option: (t=57,l=2) Maximum DHCP Message Size = 1152

            Option: (57) Maximum DHCP Message Size

            Length: 2

            Value: 0480

        Option: (t=61,l=45) Client identifier

            Option: (61) Client identifier

            Length: 45

            Value: 00636973636F2D303032352E343564372E373464642D5044...

        Option: (t=12,l=15) Host Name = "PD1-STATIC-WXP"

            Option: (12) Host Name

            Length: 15

            Value: 5044312D5354415449432D57585000

        Option: (t=55,l=6) Parameter Request List

            Option: (55) Parameter Request List

            Length: 6

            Value: 01060F2C0321

            1 = Subnet Mask

            6 = Domain Name Server

            15 = Domain Name

            44 = NetBIOS over TCP/IP Name Server

            3 = Router

            33 = Static Route

        End Option

        Padding

The only thing that is new is the 'register this connection in DNS' thing you can find in the Advanced AV. properties

VMWare EFI Netboot problem

I tried for awhile now for netboot in a guest OS 10.8 and aired on a compatibility issue between my netboot (a Dell KACE K2000) server and VMWare Fusion Pro (this applies also to ESXi 5.5). For some reason, I jsutcan not get VM to netboot at all. There seems to be something to do with the VMWare EFI not broadcasting not quite the right information when it travels to netboot. Physical Macines will very well be netboot. In my efforts to solve the problem, I finally configure the virtual machine to make sure that the DHCP packet it sends are as close as possible to what sends a physical machine. Here are my results so far:
This first package comes from a WORKING PHYSICAL machine. This is the last packet sent before it receives an adequate response of the K2000 containing the name of boot file, the path root etc...
Time Source Destination Protocol Info length No.
196 18.139846000 10.4.40.180 255.255.255.255 DHCP DHCP inform 357 - Transaction ID 0 x 0
Supervise the 196: 357 bytes on wire (2856 bits), 357 (2856 bit) captured bytes on interface 0
Ethernet II, Src: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d), Dst: Broadcast (ff: ff: ff: ff: ff: ff)
Internet Protocol Version 4, Src: 10.4.40.180 (10.4.40.180), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
Message type: start request (1)
Type of equipment: Ethernet (0x01)
The hardware address length: 6
Hops: 0
Transaction ID: 0x00000000
Seconds: 0
BOOTP flags: 0 x 0000 (Unicast)
IP address of the client: 10.4.40.180 (10.4.40.180)
(Client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
The relay agent IP address: 0.0.0.0 (0.0.0.0)
MAC address of the client: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Customer address material fill: 00000000000000000000
Not given server host name
Not given boot file name
Magic cookie: DHCP
Option: (43) Vendor-Specific Information
Length: 19
Option: DHCP Message Type (53)
Length: 1
DHCP: Inform (8)
Option: list queries setting (55)
Length: 5
Parameter query list item: the subnet mask (1)
Parameter query list item: router (3)
Parameter query list item: boot file name (67)
List of parameter query element: the information specific to the provider (43)
Parameter query list item: class ID of seller (60)
Option: the DHCP Message size maximum (57)
Length: 2
Maximum DHCP Message size: 1500
Option: class ID of seller (60)
Length: 28
Class identifier of the provider: AAPLBSDPC/i386/MacBookPro8, 1
Option: identifier for Client (61)
Length: 7
Type of equipment: Ethernet (0x01)
MAC address of the client: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Option: end (255)
End option: 255
The response of the K2000:
Time Source Destination Protocol Info length No.
197 18.140539000 10.4.40.57 10.4.40.180 DHCP DHCP ACK - Transaction ID 618 0 x 0
Frame 197: 618 bytes on wire (4944 bits), 618 bytes captured (4944 bits) on the 0 interface
Ethernet II, Src: Vmware_b8:00:46 (00:50:56:b8:00:46), Dst: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Internet Protocol Version 4, Src: 10.4.40.57 (10.4.40.57), Dst: 10.4.40.180 (10.4.40.180)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
Message type: response of Boot (2)
Type of equipment: Ethernet (0x01)
The hardware address length: 6
Hops: 0
Transaction ID: 0x00000000
Seconds: 0
BOOTP flags: 0 x 0000 (Unicast)
IP address of the client: 10.4.40.180 (10.4.40.180)
(Client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 10.4.40.57 (10.4.40.57)
The relay agent IP address: 0.0.0.0 (0.0.0.0)
MAC address of the client: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Customer address material fill: 00000000000000000000
The server host name: 10.4.40.57
Name of boot file: netbootintel/i386/boot
Magic cookie: DHCP
Option: DHCP Message Type (53)
Length: 1
DHCP: ACK (5)
Option: class ID of seller (60)
Length: 9
Class identifier of the seller: AAPLBSDPC
Option: DHCP Server identifier (54)
Length: 4
The identifier for the DHCP server: 10.4.40.57 (10.4.40.57)
Option: (43) Vendor-Specific Information
Length: 12
Option: path for root (17)
Length: 72
Root Path: nfs:10.4.40.57:/kbox/datastore/current/tftpboot/netbootintel:netboot.dmg
Option: end (255)
End option: 255
Padding
As you can see, the K2000 responds with a boot file name and the Option 17.
Now for the virtual machine. You will notice that it reports the same model and MAC address as the physical machine, to rule out all wobbly filtering is done by the k2000:
Time Source Destination Protocol Info length No.
4455 198.409015000 10.4.40.180 255.255.255.255 DHCP DHCP inform 341 - ID of Transaction 0xf3d34dfa
Frame of 4455: 341 bytes on wire (2728 bits), 341 bytes captured (2728 bits) on the 0 interface
Ethernet II, Src: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d), Dst: Broadcast (ff: ff: ff: ff: ff: ff)
Internet Protocol Version 4, Src: 10.4.40.180 (10.4.40.180), Dst: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67)
Bootstrap Protocol
Message type: start request (1)
Type of equipment: Ethernet (0x01)
The hardware address length: 6
Hops: 0
Transaction ID: 0xf3d34dfa
Seconds: 4
BOOTP flags: 0 x 8000 (broadcast)
1... = broadcast flag: Broadcast
.000 0000 0000 0000 = reserved flags: 0x0000
IP address of the client: 10.4.40.180 (10.4.40.180)
(Client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 0.0.0.0 (0.0.0.0)
The relay agent IP address: 0.0.0.0 (0.0.0.0)
MAC address of the client: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Customer address material fill: 00000000000000000000
Not given server host name
Not given boot file name
Magic cookie: DHCP
Option: (43) Vendor-Specific Information
Length: 7
Option: DHCP Message Type (53)
Length: 1
DHCP: Inform (8)
Option: list queries setting (55)
Length: 5
Parameter query list item: the subnet mask (1)
Parameter query list item: router (3)
Parameter query list item: boot file name (67)
List of parameter query element: the information specific to the provider (43)
Parameter query list item: class ID of seller (60)
Option: class ID of seller (60)
Length: 28
Class identifier of the provider: AAPLBSDPC/i386/MacBookPro8, 1
Option: identifier for Client (61)
Length: 7
Type of equipment: Ethernet (0x01)
MAC address of the client: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Option: end (255)
End option: 255
Far as I can tell only 2 differences between these packages:
1 option 43 (provider specific information) is still that of length 7 coming from the virtual machine. Previous earlier packets in the netboot process are of length 7 physical machine, but you'll see that the package I listed length 19. It has a good amount more of information.
2. the physical machine Specifies the maximum size of 57 DHCP. I do not think that this issues as well, it is 1500 which corresponds to the MTU of the network.
Here's how the K2000 meets the virtual machine:
Time Source Destination Protocol Info length No.
4456 198.409714000 10.4.40.57 10.4.40.180 DHCP DHCP ACK - 0xf3d34dfa Transaction ID 618
Frame 4456: 618 bytes on wire (4944 bits), 618 bytes captured (4944 bits) on the 0 interface
Ethernet II, Src: Vmware_b8:00:46 (00:50:56:b8:00:46), Dst: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Internet Protocol Version 4, Src: 10.4.40.57 (10.4.40.57), Dst: 10.4.40.180 (10.4.40.180)
User Datagram Protocol, Src Port: bootps (67), Dst Port: bootpc (68)
Bootstrap Protocol
Message type: response of Boot (2)
Type of equipment: Ethernet (0x01)
The hardware address length: 6
Hops: 0
Transaction ID: 0xf3d34dfa
Seconds: 0
BOOTP flags: 0 x 8000 (broadcast)
1... = broadcast flag: Broadcast
.000 0000 0000 0000 = reserved flags: 0x0000
IP address of the client: 10.4.40.180 (10.4.40.180)
(Client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 10.4.40.57 (10.4.40.57)
The relay agent IP address: 0.0.0.0 (0.0.0.0)
MAC address of the client: Apple_03:2f:0 d (40: 6 c: 8f:03:2f:0 d)
Customer address material fill: 00000000000000000000
Not given server host name
Not given boot file name
Magic cookie: DHCP
Option: DHCP Message Type (53)
Length: 1
DHCP: ACK (5)
Option: class ID of seller (60)
Length: 9
Class identifier of the seller: AAPLBSDPC
Option: DHCP Server identifier (54)
Length: 4
The identifier for the DHCP server: 10.4.40.57 (10.4.40.57)
Option: (43) Vendor-Specific Information
Length: 47
Option: end (255)
End option: 255
Padding
He responds in the same way as for all DHCP, just because the last packet sends the VM before exhaling is identical to the previous. For some reason, he does not get past the stage of the netboot process LIST. I'm not 100% sure if the bug is really on the side of VMWare or the side of the K2000. Probably both honestly. Everything I have out the newspaper on the k2000 is "BSDP LIST 10.4.40.180:68 (MacBookPro8, 1/i386). The strange thing is, looking back in the newspapers I see the OCCASIONAL entry in the log indicating that virtual machine actually there for the SELECTION phase (BSDP SELECT in 10.4.40.196:622 (VMware7, 1/i386)). It's from before I changed the hardware ID to match a known correct machine. But it's random, few and far between. No real change in the virtual machine in these cases.
Some other relevant info on the environment: the k2000 once PXE and Netboot. We need to have both available on the same network, if DHCP options are implemented for PXE. I also confirmed that windows VM will be netboot very well. Maybe the EFI VMWare doesn't like the presence of both on the same network?

Ah, found the problem. At least, I think that I have. I would say that your NetBoot server behaves in a divergent way of Apple's NetBoot server, but we could also make our firmware a little more tolerant of the situation.

During (BSDP) NetBoot server discovery, BSDP protocol messages are packed in the field 'Vendor-Specific Option' in the format described in RFC 2132 (the same format DHCP options themselves are stored in the package). RFC 2132 sets a terminator from the list of DHCP options (in section 3.2), but BSDP itself define nor stipulate a list for options BSDP NetBoot Apple Server terminator does not issue a list terminator - expects customers use the length the DHCP field the length of the list of options of BSDP "Vendor-Specific Option", which makes sense. Your NetBoot server is such a terminator (0xff), which is sort of implicitly authorized (as it is in the RFC 2132) but Apple server is not and we do not expect.

Here is the offending BSDP ACK [LIST], with the dissected option DHCP data (I hope that the formatting out):

40 0000 6 c 8f 2f 03 0D 56 50 00 b8 00 46 08 00 45 00 @l... /... PV... ... F E.

5 0010 02 c 9 b 00 00 40 11 85 01 0 8F has 04 28 39 0 a 04. \... @... (9...

0020 28 b4 00 43 00 44 02 48 66 17 02 01 06 00 ed 85 (..) C.D.Hf...

0030 e9 c2 00 00 80 00 0 a 04 28 00 00 00 00 0 a 04 b4... (.......

0040 28 39 00 00 00 00 40 03 2f 6 c 8f 00 00 00 00 0D (9...@l... /...)

0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

00 a 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

c 00 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

00D 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

0110 00 00 00 00 00 00...

Magic number DHCP:

63 82 53 63 c.Sc

DHCP (ACK) Message type:

35 01 05 5...

Vendor class ID ("AAPLBSDPC"):

3 C 09 41<>

0120 41 50 42 53 44 50 43 APLBSDPC 4 C

The identifier for the DHCP (10.4.40.57):

36 0 a 04 04 28 39 6... (9

Provider-specific option (0x2b, 43): 2 b +.

Length of the vendor-specific Option (0x2f, 47) 2f /.

Option data specific to the provider (47 bytes, opaque at this level):

0130 01 01 01 04 02 80 00 07 04 81 00 06 09 1f 81 cc...

0140 00 cc 06 1A 4 b 32 30 30 30 20 4 65 74 42 6f 6f... K2000 NetBoo

0150 74 20 28 31 30 2nd 2nd 34 34 30 2 35 37 29 ff t (10.4.40.57).

DHCP option list Terminator: ff.

0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...

[...]

Pulling the 47 bytes of data in the Data Option Vendor-Specific field, we get:

Type of Message BSDP (LIST):

0130   01 01 01                                         ...

The BSDP (0x8000) server priority:

04 02 80 00                                ....

BSDP ID of default Boot Image (0x8100cc06)

07 04 81 00 cc 06...

BSDP list of boot images (length 0x1f, 31):

09 81 1F...

0140 00 cc 06 1A 4 b 32 30 30 30 20 4 65 74 42 6f 6f... K2000 NetBoo

0150 74 20 28 31 30 2nd 2nd 2nd 34 34 30 35 37 29 t (10.4.40.57)

THE WANDERING TERMINATOR:

ff .

This byte unique ff causes our BSDP analysis to cancel the package [LIST] ACK as invalid.

If the implementation of NetBoot Apple works on the same server, it must be tolerant to a terminator explicit here. I'll change our implementation to do the same. It may be useful to remind your NetBoot server provider as well, in case they wish to change their server to behave more like Apple.

Thanks for the report!

--

Darius

Post edited by: Darius Davis: corrected a "that" must have been a "does not" and made a few other details.

Hyperic HA does support load balancing?
Hello

We try to implement architecture Hyperic high availability based on JBoss HA and distributed cache EHCache. Our version is 3.2.3 EE.
The cluster configuration is quite simple with the HQ High Availability Guide.
Thanks for this guide and the esayness of the configuration of the feature!

My first question was, the agent, what server IP should I use? I put with node 1 and other agents with node 2
= > the synchronization between nodes works very well.

Therefore, I have some additional questions.

1 / can I have a single point of entry for agents with some load balancing and failover capability?
For example, if an agent is sending information with the Node1 and this node breaks down or the server is restarted for maintenance purposes, the agent information will be lost.

2 / same question for the application, can I have a single point of entry URL with some load balancing and failover capability?

Thanks for your help.

Nicolas.

Post edited by: njmn
HQ Enterprise HA for failover, but do not support for load balancing. You will need before your HQ multiple servers with a load (software/hardware) balancer which will relay agent to a live server. The load balancer must be staged all agents in a single node of 'master '. If this server is unavailable, another server will automatically become the master node and agents should be redirected to this node.

Charles

Virtual router workstation 7.1 does support DHCP/BOOTP

I have just set up two DHCP servers on my domain and I have four workstations running vmware workstation. Each workstation has 20 + windows XP customers running both. Each VM XP is currently using the internal router VMWares to assign addresses. Now that I have these brilliant new installed DHCP servers and running for my physical machines, I would use my virtual servers DHCP to distribute IP addresses to the XP machines that use virtual router of workstations.
So the virtual router workstations VMWare is consistent to RFC1542 DHCP/BOOTP relay agent capabilities
Thank you

Workstation 7.1 works like a virtual basic router.

No - your host operating system running a NAT service - it is something very different.

If this service doesn't support BOOTP - I think that this isn't - you can use real virtual router - maybe some Linux - VM.

Then you are free to add features to the router...

_________________________

VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

Agent query CVP/UCCE 10.5 Whisper - Whisper quick read failed

Hello Cisco community support,

We are currently experiencing problems with Agent Whisper, it's something we want to implement. At present when us dial in a script we headed over to the agent without a prompt whispers playing, we followed the official guide on the Cisco site and are currently receiving the following error message in the SVC call logs from the server during a call in the UCCE script (# were replaced when the IPS as stated due to concerns IS) :

87768869: #. ###. ##. #: 2 August 2016 09:05:11.360 + 0100: % CVP_10_5_SIP-3-SIP_ERROR_SNMP: CALLGUID = A97FB1F357BE11E6B478881DFCAC6500 LEGID = A97FB1F357BE11E6B478881DFCAC6500-14701251111571276 - [OUTGOING] failed to read quick Whisper. Check the media name and address. VXML log bridge can provide more details with "err deb voip appl" trace on. [id: 5010]

On the bridge, we have the following relevant commands configured:

Gateway Gateway/VXML penetration

Host mediaserver IP #. ###. ##. ###

mediaserver-backup host IP #. ###. ##. ###

!

Dial-peer voice voip 919191

CVP SIP ringtone description

ring service

session protocol sipv2

entering the number called 919191T

voice-class sip rel1xx disable

DTMF-relay rtp - nte

Codec g711ulaw

No vad

!

On the console of the CVP Ops we have configured the following:

CVP OPs Console

Ringtone 91919191

Local name Static Route IP address/host/Server Group name: VXML. #. co.uk

Send calls to the originator

Whisper 9191919100 announced

Local name Static Route IP address/host/Server Group name: VXML. #. co.uk

Send calls to the originator

Script of the ICM

Queue skills was also set to "activate target Requery.

The WAV file was spelled correctly, when we put the wav file to a device variable 9 and PM - 9 as the audio file plays fine meaning that the codec is certainly appropriately, as gateway plays the message the value of the post to run the Script. However, when we just run the Script of post PM value and Call.WhisperAnnounment the call just are routed through and without murmur is played.

Can anyone tell what else could be the cause this error message?

If you want something else, then please let me know.

Kind regards

Christopher Hawkins

OK, so if 'My term' does not work then you might want to try the "logging console command.

but I do not see what I wanted,

/en_gb/app/Whisper.wav - 80 - #. ###. ##. # cisco-IOS-C3900e/15.3 404 0 2 0

The 404 indicates that the file is not available at the location defined in media server.

The very basic test you can do is, open the browser on the machine where you can join the media server and type below URL.

http:///en_gb/app/whisper.wav

and if you see the 404 error, most probably the file is missing in app/en_gb/site, or maybe you're trying to find bad file.

one last thing, en_gb (trait underscore between fr and gb) will not be supported in a later version of the CVP.

It should be replaced by en-gb(en hyphen gb).

therefore ensure that the locale folder CVP could be defined as en - us, but you're trying to get en_US.

concerning

Colinet

Application of relay

Hello
Is there any application which can relay another application on Flash Media server?
For example, I have a 'live' application on the server. I want another application, "liverelay" that can relay essentially makes his appearance on the 'live' application
Is this possible? If yes how can I apply?
Looking forward to a response.
Thank you

Basically, you can hold in my code from anywhere above the code of the application 'live' - I don't think that it must enter in conflict - something like below

NetConnection.prototype.connectTimer;

NetConnection.prototype.url;

NetConnection.prototype.onStatus = function (info)

{

trace ("# nc:" + info.code + "' # '");

If (info.code == "NetConnection.Connect.Failed" |) info.code is "NetConnection.Connect.Closed")

{

If (this.connectTimer)

{

clearInterval (this.connectTimer);

this.connectTimer = null;

}

trace ("set up to reconnect timer for" + this.url);

this.connectTimer = setInterval (reconnection, 30000, this);

} else {}

If (info.code is "NetConnection.Connect.Success")

{

trace ("* connection to" + this.url + "successfully");

If {(this.connectTimer)

clearInterval (this.connectTimer);

}

}

}

}

Reconnect = function (nc)

{

If (NC.connectTimer)

{

clearInterval (nc.connectTimer);

nc.connectTimer = null;

}

NC. Connect (NC. (URL);

}

application.onAppStart = function()

{

NC = new NetConnection();

NC. URL = "rtmp://localhost/app_2";

NC. Connect (NC. (URL);

}

application.onPublish = function (client, stream)

{

trace ("# publish:" + stream.name + "#");

client.ns = new NetStream (nc);

client.ns.onStatus = function (info)

{

trace ("ns:" + info.code);

If (info.code is "NetStream.Publish.Start")

{

client.ns.Attach (Stream);

}

}

If (client.ns)

{

client.ns.Publish (Stream.Name);

}

Returns true;

}

application.onUnpublish = function (client, stream)

{

trace ("# end of publication:" + stream.name + "#");

client.ns.Attach (false);

client.ns.Publish (false);

}

/*

* application.onConnect:

* Implementation of the interface onConnect function (optional).

* It is called whenever a client connection request connection. Live webcam app uses this

* function to authenticate the connection field and allows only

for one request of the Subscriber.

*/

application.onConnect = function (p_client, p_autoSenseBW)

{

Check if pageUrl is an area that we know.

Check pageurl

An application for Flash Media Encoder is not verified for authentication

If ((p_client.agent.indexOf ("WEF") is-1) & (p_client.agent.indexOf ("GFFE") is-1))

{

Area of the HTML of authentication for the request file:

Do not call validate() when the query is localhost

or HTML authentication domains is disabled.

If ((p_client.ip! = "127.0.0.1") & application.) HTMLDomainsAuth

&& ! this.Validate (p_client.pageUrl, this.allowedHTMLDomains))

{

trace ("authentication for pageurl failed:" + p_client.pageUrl + ", rejecting the connection to" + p_client.ip);

Returns false;

}

Authentication of domain of the SWF file for the query:

Do not call validate() when the query is localhost

or SWF authentication domains is disabled.

If ((p_client.ip! = "127.0.0.1") & application.) SWFDomainsAuth

&& ! this.Validate (p_client.referrer, this.allowedSWFDomains))

{

trace ("authentication for sponsor failed:" + p_client.referrer + ", rejecting the connection to" + p_client.ip);

Returns false;

}

Logging

trace ("accepted a connection to IP address:" + p_client.ip)

+ ", sponsor:"+ p_client.referrer"

+ ", pageurl:" + p_client.pageUrl);

} else {}

Logging

trace ("Adobe Flash Media Encoder connected to" + p_client.ip);

}

By default, all clients are disabled to access raw audio and video and data bytes in a stream

using BitmapData.draw () and () SoundMixer.computeSpectrum., please see

Flow doccumentations for access to the data to know requirement version of flash player to support this restriction

Access permissions can be allowed for all uncomment the following statements

p_client.audioSampleAccess = ' / ';.

p_client.videoSampleAccess = ' / ';.

this.acceptConnection (p_client);

Client based on a component connection Flash 8 and 9 FLV Playback

requires the following code.

If (p_autoSenseBW)

p_client.checkBandwidth ();

on the other

p_client. Call ("onBWDone");

}

/*

* Client.prototype.getPageUrl

* Public API to return the URL of the HTML page.

*

*/

Client.prototype.getPageUrl = function() {}

Return this.pageUrl;

}

/*

* Client.prototype.getReferrer

* Public API to return the URL of the client SWF file field.

*

*/

Client.prototype.getReferrer = function() {}

Return this.referrer;

}

/*

* FCPublish:

* FME calls FCPublish with the name of the stream each time a stream of data

* is published. This notification can be used by the script action server-side

* to maintain a list of all streams or also to force FME to suspend their publication.

* To stop the publication, call "onFCPublish" with an information object with status

* code of the value of "NetStream.Publish.BadName".

*/

Client.prototype.FCPublish = function (streamname)

{

your configuration data flow and check if you want to allow this workflow to be published

If (true) / / do a validation here

{/ / This is optional.}

This.Call ("onFCPublish", null, {code: "NetStream.Publish.Start", description: streamname});

}

on the other

{

This.Call ("onFCPublish", null, {code: "NetStream.Publish.BadName", description: streamname});

}

}

/*

* FCUnpublish:

* FME notifies server script when a data stream is not published.

*/

Client.prototype.FCUnpublish = function (streamname)

{

make your own place

This.Call ("onFCUnpublish", null, {code: "NetStream.Unpublish.Success", description: streamname});

}

/*

* releaseStream:

* When the FME for FMS connection fall during an editing session, it will be

* try to republish the data stream when the connection is restored. In a certain

* times FMS will reject the new workflow server is always

* ignoring the fall of connection, sometimes it can take a few minutes.

* FME called 'releaseStream' method with the name of the stream, and this can be

* used for free by the force of the stream.

*/

Client.prototype.releaseStream = function (streamname)

{

s = Stream.get (streamname);

s.Play (false);

}

/*

* application.readValidDomains

* Function to read the file of authorized field

* Parameters:

* the file name:

* name of the file in the application directory

* which contains a domain name valid per line. This file can contain

* Comments followed by a ' # ' as the first character in this line.

* an entry without comment with a space is considered to be an error cases.

*

* Returns

* a table where each entry contains a domain name

* listed in the file.

*/

application.readValidDomains = function (fileName, domainsType)

{

var domainFile = new File (fileName);

var domainsArray = new Array();

var index = 0;

var lineCount = 0;

var tempLine;

domainFile.open ("text", "read");

Read the file line by line and fill in the domainsArray

with valid entries

While (domainFile.isOpen &! domainFile.eof ())

{

tempLine = domainFile.readln ();

lineCount ++;

If (! tempLine | tempLine.indexOf("#") == 0)

{

continue;

}

tempLine = tempLine.trim ();

If (tempLine.indexOf("")! = - 1)

{

trace ("' junk, entry field ignored." + fileName + ":"+(lineCount+1));)

}

on the other

{

domainsArray [index] = tempLine.toLowerCase ();

index ++;

If (tempLine == "*")

{

Switch (domainsType) {}

case 'HTMLDomains ':

trace ("found the wildcard character (*) entry: disable authentication for areas of HTML file" "");

request. HTMLDomainsAuth = false;

break;

case 'SWFDomains ':

trace ("found the wildcard character (*) entry: disable authentication for areas of SWF file" "");

This. SWFDomainsAuth = false;

break;

by default:

Do nothing

break;

}

}

}

} / / End while

Something is wrong! the file of areas must be accessible.

If (! domainFile.isOpen) {}

trace ("error: cannot open '" + name + "', rejecting all customers except localhost.");

}

on the other

{

domainFile.close ();

}

Return domainsArray;

}

/**

* String.prototype.trim:

* Function to cut the spaces at the end beginning of an input string.

* Returns:

* chain adorned without space leader & end.

*

*/

String.prototype.Trim = function () {}

Return this.replace(/^\s*/, "") .replace (/ \s*$ /, "");

}

===================================================

Try it and see if his work - if you are having problems LMK

Why E-mail stopped to relay my ISP?

I had my server running beautifully for serval months now. Last Friday, we noticed that some of the emails from our office did not reach their destination in a few minutes. Some would take hours and days. I could very well receive emails. We organize our company e-mail service in the House on a mac mini with OX 10.11.6 5.1.7 server. In case of problems today, I determined that the implementation of relay on the server is correct, but when I need local customers send the relay through our server it fails. If I uncheck this requirement, local customers can send very well.

The requirement of relay works well until last week. Without going through this may very well at the moment, but it seems counter-intuitive. Is there a problem with the installation of relay that needs work to update or rinsed out properly?

Now that I have turned off the outgoing 'Through ISP mail relay' switch I received a call from a person in Texas who does not work for us. He received an e-mail from his home account to our domain name.

It doesn't have an e-mail account in our system. How is this possible, and is this power flowing through our mail server?

macOS Sierra - calendar Agent Crash

I installed macOS Sierra on my MBP 8.3 (17 "end 2011) - 16 GB of RAM. 1 TB SSD.

After you have identified a problem with a Logitech mouse driver (and delete) I stopped for a few days to attend to other things.

Restart today, I had a few problems:

1. the backlight of the screen did not come until after I entered the word password (took a few reboots hard to understand what was going on. Once I entered the password, backlight restarted and has been authorized since, even after stop and restart. Weird!

2. the problem that won't go away, it's with the agent of the calendar. He has appeared as a couple of notifications - a single event, reminder of a task. I rejected the two of them, but they came back several times. The console log shows the following:

-Beginning of the inserted newspaper-

Process: CalendarAgent [312]

Path: gent /System/Library/PrivateFrameworks/CalendarAgent.framework/Executables/CalendarA

ID: CalendarAgent

Version: 8.0 (384)

Code type: X 86-64 (Native)

Parent process:? [1]

Manager: CalendarAgent [312]

User ID: 501

Date/time: 2016-09-27 16:02:35.685 + 1000

OS version: Mac OS X 10.12 (A 16, 323)

Report Version: 12

Anonymous UUID: 050C98F1-BA2C-E406-1823-28FB21ADFCF3

Time since started awake: 500 seconds

Integrity of system protection: enabled

Crashed thread: 0 dispatch queue: com.apple.main - wire

Exception type: EXC_CRASH (SIGABRT)

Exception codes: 0 x 0000000000000000, 0 x 0000000000000000

Note the exception: EXC_CORPSE_NOTIFY

Request for clarification:

Reason for termination due to an untrapped exception "NSInvalidArgumentException" app,: '-[CalManagedMigrationGroup isAutoScheduleSupported]: unrecognized selector sent to instance 0x7f87990fb920'

ending with an exception uncaught of print type

Abort() called

-End of the inserted newspaper-

There a lot more to it and a few dozen of them in today's newspaper.

Has anyone else had this?

Any thoughts on how to solve the problem?

I'm having a similar error - first Mail crashes with the error below and calendar hangs with a similar error. Details below. Everything was fine until I updated to Sierra (clean install, not upgrade).

Agent of photos using the battery

Hello

Recently 'Photos Agent' used a lot of energy, and I can not identify why. It will appear under 'apps using significant energy' and my fan go crazy mad and my computer feels as if it were about to melt. I checked all the settings to iCloud and Photos don't use iCloud at all - at least, do not (it's somehow, which is also starting to annoy me, because it was never implemented in the first place).

I do not see that it is iCloud and it does nothing between iPhoto and Photos because I deleted iPhoto, so he could be?

Very probably (given any details on your system), is looking for people - it is slow and is best done with the computer connected to the power supply

LN

I need to be in touch with an agent who speaks french. Please this is my imail address important * @ *.

I need to be in touch with an agent who speaks french. Please it's important my address imail - * @ *.

< personal information under the direction of the host >

There is no agent of Apple here. It's just a Forum user to only. Try the Apple Support here: official Apple Support

User Agent

I was wondering when I upgraded to 43.0 FF if 32 or 64 bits.

Someone explained in this thread: -.

https://support.Mozilla.org/en-us/questions/1099295

to check in the 'user agent' but not what the user agent or how to access it.

If someone can explain?

Additional: Ahh! I see that it is visible in my 'more system details' next to this post! But it is observable locally?

Then another question. I noticed that www.jpl.nasa.gov (Nasa site) will not display pictures since I upgraded to FF43.0. I have not blocked all sources of images and they appear perfectly before I updated...

Looks like it was a problem with cookies.

I have my cookies to the permissions set to "ask every time" and I reject cookies at most of the sites. Once I have re-enabled cookies for sites of nasa, they worked very well once more.

Seems strange, because they are all rendered perfectly before FF43 with cookies disabled for them...

RV042 relay agent

Similar Questions

Maybe you are looking for